[wp-meta] [Making WordPress.org] #3046: WordPress.org/about page outdated

[Making WordPress.org]

#3046: WordPress.org/about page outdated
------------------------------------------+-----------------------
 Reporter:  melchoyce                     |       Owner:  dd32
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-----------------------
Changes (by dd32):

 * owner:  obenland => dd32


Comment:

 Replying to [comment:85 tellyworth]:
 > * Make sure navigation works for extra child pages on Rosetta sites
 After reviewing the situation of how the existing navigation happens, and
 what about pages exist in the Rosetta network at present, I think I'm
 going to suggest that this isn't a launch blocker nor something we need to
 support.

 Locales in general only appear to have a translation of the about page,
 one which is often outdated. There's two locales which do have extra
 content, both of which are also out of date (when I checked them).

 There's been some examples of pages which would work placed under /about/,
 such as translation contributors, and I do think that's a good use-case of
 putting something under About. '''However''', I think that'd be best
 implemented for all locales and put into the main /about/ page hierarchy
 globally rather than on a per-locale basis.
 A new ticket for those pages would be appreciated.

 Locales will still be able to add a page into the `/about/` hierarchy,
 they'll just have to link to it from somewhere else. I'd highly suggest
 against it though as it may break things down the line when we add a
 conflicting slug page globally (which will take precedence over the
 locales custom page)

 > * Decide on how to handle translated slugs, and implement
 Slug translation isn't something we've solved on WordPress.org yet for
 rosetta sites (see: /plugins/ and /themes/) and I don't see this as a
 release blocker either.
 I've spun this out into #3507 as it's going to require a bit more work and
 will be best handled as it's own mini-project.

 > * Write a script to add pages to Rosetta sites
 > * Decide how to keep new pages in sync, and implement
 I've been testing a script for this, and have promising results. I expect
 re-running the script to populate rosetta sites will also let us populate
 them with changes. The pages will be owned by `wordpressdotorg` so not
 modifiable by locales which makes syncing changes easier.
 Unfortunately we also need to create these pages on new-rosetta-site-
 creation so we'll need to define it in two places - unless we set Rosetta
 to just duplicate any pages on `wordpress.org/` (Which is what I think
 I'll do).

 > * Find a way to add links to About page into main Rosetta navigation
 This tends to fall back to #1201 where forcing certain items into the nav
 is going to be better in the long-run for consistency
 This isn't a release blocker, and can be dealt with post-launch. The about
 pages will be linked to from the footers (See #3315)

 ----

 As Obenland is now taking some time off, I'll be finishing up the
 remaining tasks here.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3046#comment:98>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org