WordPress.org

Making WordPress.org

Opened 2 years ago

Last modified 6 months ago

#1201 new enhancement

Lock default header navigation items

Reported by: samuelsidler Owned by:
Milestone: Priority: normal
Component: International Sites (Rosetta) Keywords:
Cc:

Description

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.

Change History (16)

This ticket was mentioned in Slack in #meta-i18n by sam. View the logs.


2 years ago

#2 @ramiy
2 years ago

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

This ticket was mentioned in Slack in #polyglots by petya. View the logs.


2 years ago

#4 @dd32
2 years ago

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' );

This ticket was mentioned in Slack in #polyglots by dd32. View the logs.


2 years ago

This ticket was mentioned in Slack in #meta-i18n by sam. View the logs.


2 years ago

#7 @samuelsidler
2 years ago

  • Summary changed from Fix default header navigation items to Lock default header navigation items

This ticket was mentioned in Slack in #meta-i18n by dd32. View the logs.


2 years ago

#9 in reply to: ↑ description ; follow-ups: @SergeyBiryukov
2 years ago

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.

#10 in reply to: ↑ 9 @SergeyBiryukov
2 years ago

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.

#11 in reply to: ↑ 9 ; follow-up: @samuelsidler
2 years ago

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.

#12 in reply to: ↑ 11 @SergeyBiryukov
2 years ago

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.

This ticket was mentioned in Slack in #meta-i18n by dd32. View the logs.


2 years ago

This ticket was mentioned in Slack in #meta by ocean90. View the logs.


23 months ago

This ticket was mentioned in Slack in #polyglots by sergey. View the logs.


6 months ago

Note: See TracTickets for help on using tickets.