435555 - Implement new SUMO theme

Status: VERIFIED FIXED

(support.mozilla.org :: General, defect)

Description

[David Tenser [:djst]]

This is a tracker bug for the overall theme update for SUMO.

Comment 1

[Ryan Doherty (:rdoherty)]

Can I get access to bug 435237? Thanks!

Comment 2

[Ryan Doherty (:rdoherty)]

Assigning to myself before Brian takes over.

Comment 3

[Jason Barnabe (np)]

Some info on how the site's set up that may be helpful:

The site as set up has 7 different themes stored in templates/styles. The ones in use:

-mozfh - http://support.mozilla.com/forum
-mozfr - http://support.mozilla.com/tiki-view_forum.php?forumId=1 (non-front page forum stuff)
-mozih - In product home page (?)
-mozip - http://support.mozilla.com/en-US/kb/Options_window (KB articles linked to from Firefox itself)
-mozkb - http://support.mozilla.com/kb/Profiles (non-in-product KB articles)
-mozlc - http://support.mozilla.com/kb/Live+Chat
-mozms - http://support.mozilla.com/en-US/kb/Creating+articles and other administrative articles (possibly including the home page)

The themes consist of stylesheets named after the theme (directly inside the templates directory) and Smarty templates (inside a directory named after the theme). Where there is no template file defined, the default one (directly inside the templates directory) is used. We never change any of the tpl files directly in templates; we make a copy of the one we want to change and make it part of a theme. Many/most of the non-default ones are symlinked to another default one so reduce duplication. Some of the stylesheets @import other ones to reduce duplication as well. tiki.tpl is the main template file.

Comment 4

[Brian Krausz]

Note: mockups show "Enter Keyword" preentered in the search field, but main MoCo redesign on staging does not.  I'll follow the mockup for now, but should this be filed as a bug in the MoCo redesgin?

Comment 5

[David Tenser [:djst]]

(In reply to comment #4)
> Note: mockups show "Enter Keyword" preentered in the search field, but main
> MoCo redesign on staging does not.  I'll follow the mockup for now, but should
> this be filed as a bug in the MoCo redesgin?
> 

John, can you answer this question?

Comment 6

[David Tenser [:djst]]

General info about new production files:

Moz_SUMO_Home_01.psd - the new start page template (http://support.mozilla.com/)

Moz_SUMO_Inproduct_01.psd - the Firefox 3 product help landing page (what you see when hitting F1 in Firefox). Note the simplified top nav -- that should be used while in ?stylemode=inproduct. All URIs from Fx3 are using this parameter. Ask Nelson for the details about that mode.

Moz_SUMO_Article_01.psd - the knowledge base article template. E.g. http://support.mozilla.com/en-US/kb/Firefox+is+already+running+but+is+not+responding

Moz_SUMO_contribute2.psd - the contributor article template, e.g. articles meant for contributors, not end-users.

Moz_SUMO_generic.psd - here's a more generic template that uses the wiki page title as the white, large heading, and no Actions box visible. It would typically be used for pages like Support Firefox Day, etc. 

Moz_SUMO_ForumsHome_01.psd - the Support Forum start page (http://support.mozilla.com/forum). Note that the main area is slightly wider than on the regular start page. This is because the two lists contain much longer strings and is by design.

Moz_SUMO_Forumsbrowse_01.psd - the forum browse template. See http://support.mozilla.com/tiki-view_forum.php?locale=en-US&forumId=1 for an example of how it looks like today to see what it replaces.

Moz_SUMO_Forumspost_01.psd - the forum post view template. See http://support.mozilla.com/tiki-view_forum_thread.php?locale=en-US&comments_parentId=58254&forumId=1  for an example of how it looks like today to see what it replaces.

Moz_SUMO_LiveChat_01.psd - the Live Chat start page (http://support.mozilla.com/chat). The file shows the foxkeh while the chat is closed. Note that the text "We're Closed" needs to be part of the image because the Live Chat software doesn't support updated status of both text and images (afaik).

Comment 7

[John Slater]

(In reply to comment #4)
> Note: mockups show "Enter Keyword" preentered in the search field, but main
> MoCo redesign on staging does not.  I'll follow the mockup for now, but should
> this be filed as a bug in the MoCo redesgin?
Great question. I actually would prefer to have the search field stay blank when SUMO is implemented (no "Enter Keyword" in other words). No need to file a Mozilla.com bug for now.

Thanks! 

Comment 8

[Brian Krausz]

The mockup shows that in articles (Moz_SUMO_Article_01.psd), the first h2 (Firefox did not shut down normally) should not have the horizontal rule above it, but the rest of the h2's should.  Since this is within the wikitext, I cannot change the HTML, only the CSS, and there is no way to implement this in CSS (the first-child pseudo-element only matches if the h2 is the first actual element).  I can either take out all the horizontal rules or leave one in between the TOC and the first h2.  Please advise :).

Comment 9

[Brian Krausz]

Status update:

For those with VPN access: http://bk-sumo.khan.mozilla.org/en-US/kb/Firefox+is+already+running+but+is+not+responding

Tested on Firefox and Safari, waiting for a VMWare license to test on IE.

Standard and KB articles should be done, the main content of the homepage needs to be updated in the wiki, will figure out how to submit the revised tikiwiki code later.

Also, will there be icons for logged-in actions such as Souce, Monitor this page, and History, or should those just be iconless?

--Brian

Comment 10

[David Tenser [:djst]]

(In reply to comment #8)
> The mockup shows that in articles (Moz_SUMO_Article_01.psd), the first h2
> (Firefox did not shut down normally) should not have the horizontal rule above
> it, but the rest of the h2's should.  Since this is within the wikitext, I
> cannot change the HTML, only the CSS, and there is no way to implement this in
> CSS (the first-child pseudo-element only matches if the h2 is the first actual
> element).  I can either take out all the horizontal rules or leave one in
> between the TOC and the first h2.  Please advise :).
> 

Let's keep the rules for all h2's. We can possibly change the wiki generated output to create a separate class for the first h2, but for now let's use a rule on all h2s.

Comment 11

[Brian Krausz]

We're done here...yay!