Lock default header navigation items

[samuelsidler]

The headers on Rosetta sites are flexible right now, in that they can be rearranged in whatever way an Editor wants. Flexibility is good, but we should also try for consistency with the rest of WordPress.org. As a result, I think we should "fix" the default items to the header and allow Editors to rearrange everything after those items.

Thus, we should fix these items, in order:

• Home (instead of "Showcase")
• Themes
• Plugins
• Forums (if applicable, instead of "Support")
• Get Involved (if applicable, link to P2 – note that no locales use this right now)
• Blog
• Download (in lieu of the download button)
• Custom menu with everything else

If we do this, we'll need to do the following:

• Add the following items as strings to the Rosetta project.
• Alert translation editors that this will change, and pick a day (to avoid duplicate items)
• Ship it!‡

‡ Coding may be required.

[ramiy]

he_IL forums have differnt headers. And they are not in use by the general public, only by spammers.

[dd32]

The strings will be imported into translate.wordpress.org in the near future.

For reference, the implementation I've done with (which is in a private repo currently) is this:

/* translators: This is the menu title used on the localised WordPress homepage menu. */
_x( 'Home',         'Menu title', 'rosetta' );

/* translators: This is the menu title used on the localised WordPress homepage menu. */
_x( 'Themes',       'Menu title', 'rosetta' );

/* translators: This is the menu title used on the localised WordPress homepage menu. */
_x( 'Plugins',      'Menu title', 'rosetta' );

/* translators: This is the menu title used on the localised WordPress homepage menu. */
_x( 'Forums',       'Menu title', 'rosetta' );

/* translators: This is the menu title used on the localised WordPress homepage menu. */
_x( 'Get Involved', 'Menu title', 'rosetta' );

/* translators: This is the menu title used on the localised WordPress homepage menu. */
_x( 'Blog',         'Menu title', 'rosetta' );

/* translators: This is the menu title used on the localised WordPress homepage menu. */
_x( 'Download',     'Menu title', 'rosetta' );

[SergeyBiryukov]

Replying to samuelsidler:

Flexibility is good, but we should also try for consistency with the rest of WordPress.org. As a result, I think we should "fix" the default items to the header and allow Editors to rearrange everything after those items.

Thus, we should fix these items, in order:
...

• Forums (if applicable, instead of "Support")

If the goal is consistency with ​https://wordpress.org/, why not a combined Forums/Documentation submenu under "Support"? With a fallback to just "Forums" for locales that don't have localized documentation.

[SergeyBiryukov]

Replying to SergeyBiryukov:

If the goal is consistency with ​https://wordpress.org/, why not a combined Forums/Documentation submenu under "Support"? With a fallback to just "Forums" for locales that don't have localized documentation.

Or perhaps linking to English documentation (for the sake of consistent menus) would be better in that case.

[samuelsidler]

Replying to SergeyBiryukov:

If the goal is consistency with ​https://wordpress.org/, why not a combined Forums/Documentation submenu under "Support"? With a fallback to just "Forums" for locales that don't have localized documentation.

Because there's no way to know if a given locale has a page for documentation. What would that be based on? Slug? Page name? It'd be guesswork at best right now.

Eventually, support docs (in English) will be on wordpress.org/support/ (via helphub), which we'll bring over to Rosetta sites in some form so support/help docs can live there. When that happens, we'd rename the tab from "Forums," of course.

For the time being, I think it's fine to let Rosetta sites link to their documentation at the end of the fixed tabs.

[SergeyBiryukov]

Replying to samuelsidler:

Because there's no way to know if a given locale has a page for documentation. What would that be based on? Slug? Page name? It'd be guesswork at best right now.

There's a list on ​https://codex.wordpress.org/Codex:Multilingual#Codex_in_other_Languages that might help.

[SergeyBiryukov]

Related: #2898

[SergeyBiryukov]

With the ​new About pages on Rosetta sites added in #3046, would be great to have a consistent placement for them:

• Between "Get Involved" and "Blog", as on the main site.
• With "About" title rather than "Democratize Publishing"

Currently, they are added to the end of the menu as "Democratize Publishing": ​https://test.wordpress.org/about/.

[azhiyadev]

Hiya

We will be launching Learn WordPress shortly and "Learn" has been added onto the main navigation menu on wordpress.org ​https://wordpress.org (next to Showcase). How do we get it on Trac and localised sites - ideally in the same position as wordpress.org?

Where you currently have Support, Developers and Get Involved on the footer of Trac sites, can we have please have "Learn WordPress" displayed at the bottom of this?

[dd32]

Just noting that this ticket was never fully implemented, but that some code was deployed for it.
It's active on ​https://en-au.wordpress.org/ (Home -> About is forced, Learn -> Team is set via the wp-admin menu - see above image), but was never rolled out to all sites.

How do we get it on Trac and localised sites - ideally in the same position as wordpress.org?

Trac was added in [10519].

Adding Learn (English-only resource) to localised sites main menu doesn't offer a great experience, so I'm hesitant to force it upon localised teams, especially in such a prominent location. Continuing discussion on ​https://github.com/WordPress/learn/ on how best to bring it to a localised audience would be best.

[azhiyadev]

Thank you @dd32 I'll pick up the rest of the discussion via GitHub.

[dd32]

With some recent (and upcoming) changes in the WordPress.org headers, it's made sense to finalise this.

All rosetta sites now have certain menu items forcefully prefixed, and some duplicate ones were removed.