We've talked about this quite a bit in the context of DevHub where User Contributed Notes are occasionally used as a feedback mechanism. Basically, we need a way for docs consumers to report problems or suggest edits of published documentation on .org.

The initial proposal would be to build or use something akin to ​Post Forking on the front-end of handbooks and eventually other places like DevHub or HelpHub.

Personally I don't think an MVP has to be a complete solution, it mostly needs to cover the rift drawn between moving away from the Codex where any user could edit anything to the now largely closed systems on .org.

I think starting with the handbooks would be the way to go.

Several ​HTML5 sectioning elements automatically create ​ARIA landmark regions.

Landmark regions are exposed to assistive technologies and allow users to quickly find information in a page. Ideally, all content in a web page should be wrapped within landmark regions. For now, I'd like to propose to focus on the navigation menu.

In this specific case it's important to know that <nav> elements are mapped to an ARIA role=navigation. Therefore, <nav> elements are perceived by screen readers and users can jump to them using dedicated keyboard shortcuts.

In the wp.org network, some sections don't use <nav> elements at all. For example, the home page (screenshot from Safari and VoiceOver):

Other sections do use navigation landmarks but not for the main menu. For example, the Themes section has two of them:

Same in the Plugin section sub-pages:

For clarity, these are respectively:

• a <nav> element with a role="navigation": it was common practice to repeat the role even if redundant, to support old browsers assistive technologies
• a <div> element with a role="navigation", which is equivalent to a <nav>

Besides technical details, the most important navigation (the main one) doesn't use a navigation landmark. Wrapping the main menu in a <nav> element would be a good, simple, improvement.

Note: when in a page there are multiple landmarks of the same type, it's important to use an aria-label to help users to distinguish them. This is also what WordPress core and the bundled themes do.

Suggested:

• wrap the existing main menu markup in a <nav aria-label="Main menu">
• where present, add to the secondary navigation an aria-label="Secondary menu" (or any better wording)
• the toolbar already uses an aria-label="Toolbar", no need for any change

Optionally:

• modernize the markup: remove role="navigation" and just use a <nav> element

Note about the wording: When screen readers encounter a <nav> element or a role="navigation", they already announce "navigation": it's recommended to not use this word in the aria-label because it would be announced twice.

In light of the June 18 outage where plugin updates aren't being properly synced, @otto42 pointed out it would be useful if the wp-admin page for a plugin had a button or such to 'force' an update. This would obviate the need for grabbing someone with systems access every time a plugin got stuck for whatever reason, and in cases like this would let us ensure security fixes were properly handled in a timely manner.

Replace the contents of ​https://ps.w.org/robots.txt with:

User-agent: * Disallow: /

Plugin pages, like ​https://wordpress.org/plugins/autoptimize/, often contain FAQ content.

When this is the case, we should output FAQ schema markup, with an aim to encourage Google to show FAQ questions+answers in the search results (therefore achieving extra visibility and clickthrough-rates).

Approach

• Add an additional node to the existing schema markup on plugin pages, for "@type": "FAQPage".

• Add a mainEntity property to house the questions.
  • Loop through each question/answer, and construct a Question node with an acceptedAnswer property.

Example output

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What does the plugin do to help speed up my site?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "It concatenates all scripts and styles, minifies and compresses them, adds expires headers, caches them, and moves styles to the page head, and scripts (optionally) to the footer. It also minifies the HTML code itself, making your page really lightweight."
    }
  }, {
    "@type": "Question",
    "name": "But I’m on HTTP/2, so I don’t need Autoptimize?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "HTTP/2 is a great step forward for sure, reducing the impact of multiple requests from the same server significantly by using the same connection to perform several concurrent requests. That being said, <a href="http://engineering.khanacademy.org/posts/js-packaging-http2.htm">concatenation of CSS/ JS can still make a lot of sense</a>, as described in <a href="https://css-tricks.com/http2-real-world-performance-test-analysis/">this css-tricks.com article</a> and this <a href="http://calendar.perfplanet.com/2015/packaging-for-performance/">blogpost from one of the Ebay engineers</a>. The conclusion; configure, test, reconfigure, retest, tweak and look what works best in your context. Maybe it’s just HTTP/2, maybe it’s HTTP/2 + aggregation and minification, maybe it’s HTTP/2 + minification (which AO can do as well, simply untick the “aggregate JS-files” and/ or “aggregate CSS-files” options). And Autoptimize can do a lot more then “just” optimizing your JS &amp; CSS off course 😉"
    }
  }, {
    "@type": "Question",
    "name": "Will this work with my blog?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Although Autoptimize comes without any warranties, it will in general work flawlessly if you configure it correctly. See “Troubleshooting” below for info on how to configure in case of problems."
    }
  },
  {...}
  ]
}

Sanitization concerns

All HTML tags should be stripped from fields, with the exception of the text property of an acceptedAnswer, which should:

• Accept <a>, <strong> and <em> tags.
• Disallow/remove any values/properties/attributes of these tags (other than the href attribute on <a> tags).
• Remove invalid markup (e.g., an <a> without a closing </a>).

• Change the <title> content to: {{Full Name}} ({{Username}}) - WordPress user profile | WordPress.org. E.g., Joost de Valk (joostdevalk) - WordPress user profile | WordPress.org.

• Add and populate a meta description tag with the (sanitized) content of the Bio field, up to 160 characters (cutting off gracefully with an ellipses character).

• Add and populate open graph tags as follows:

<meta property="og:type" content="profile" />
<meta property="og:title" content="{{Full Name}} - WordPress user profile" />
<meta property="og:description" content="{{Meta description}}" />
<meta property="og:url" content="{{URL}}" />
<meta property="og:site_name" content="WordPress" />
<meta property="og:image" content="{{Gravatar Large Image}}" />
<meta property="profile:username" content="{{Username}}" />

The following code should be adapted and added to profile templates (values from ​https://profiles.wordpress.org/jonoaldersonwp/ used for reference).

<script type="application/ld+json">
{
    "@context":"https://schema.org",
    "@graph":[
        {
            "@type":"Organization",
            "@id":"https://wordpress.org/#organization",
            "url":"https://wordpress.org/",
            "name":"WordPress",
            "logo":{
                "@type":"ImageObject",
                "@id":"https://wordpress.org/#logo",
                "url":"https://s.w.org/style/images/about/WordPress-logotype-wmark.png"
            },
            "sameAs":[
                "https://www.facebook.com/WordPress/",
                "https://twitter.com/WordPress",
                "https://en.wikipedia.org/wiki/WordPress"
            ]
        },
        {
            "@type":"WebSite",
            "@id":"https://wordpress.org/#website",
            "url":"https://wordpress.org/",
            "name":"WordPress.org",
            "publisher":{
                "@id":"https://wordpress.org/#organization"
            }
        },
        {
            "@type":"ProfilePage",
            "@id":"https://profiles.wordpress.org/jonoaldersonwp/#webpage",
            "url":"https://profiles.wordpress.org/jonoaldersonwp/",
            "inLanguage":"en",
            "name":"{{Page title}}",
            "description":"{{Meta description}}",
            "isPartOf":{
                "@id":"https://wordpress.org/#website"
            }
        },
          {
            "@type":"Person",
            "@id":"https://profiles.wordpress.org/jonoaldersonwp/#profile",
            "name":"Jono Alderson",
            "image":"https://secure.gravatar.com/avatar/beed0f5ca54ae221655b9f30a1f6fe66?s=200&#038;d=mm&#038;r=g",
            "jobTitle":"Special Ops",
            "worksFor": {
             "@type":"Organization",
             "name":"Yoast"
            },
            "sameAs": [
                "https://www.facebook.com/jonathan.alderson",
                "https://www.linkedin.com/in/jonoalderson/",
                "https://twitter.com/jonoalderson"
            ],
            "mainEntityOfPage": { "@id" : "https://profiles.wordpress.org/jonoaldersonwp/#webpage" }
        }
    ]
}
</script>

NOTE: Optional nodes (like worksFor) should only be included when the relevant profile fields are populated.

NOTE: https://meta.trac.wordpress.org/ticket/4277 changes the title and description contents; values here should also change and use the new values specified in #4277.

NOTE: https://meta.trac.wordpress.org/ticket/4278 is required to retrieve/set social profiles in the sameAs array.

NOTE: If name is not set, fall back to username.

On Core and Plugins Trac, UTF-8 text is displayed correctly: ​https://core.trac.wordpress.org/browser/tags/4.4.2/tests/phpunit/tests/pomo/po.php#L115 ​https://plugins.trac.wordpress.org/browser/edit-parent-comment-id/tags/0.3/edit-parent-comment-id-ru_RU.po#L24

On Themes Trac that's not the case, looks like ISO-8859-1 is the default encoding there: ​https://themes.trac.wordpress.org/browser/zalive/1.3.4/languages/ru_RU.po#L20

The description for ​Theme Check plugin appears to be parsed incorrectly (see the screenshot).

The first code sample lacks the code formatting. In the readme.txt both samples are formatted the same way:

Examples:
`define( 'TC_PRE', 'Theme Review:[[br]]
- Themes should be reviewed using "define(\'WP_DEBUG\', true);" in wp-config.php[[br]]
- Themes should be reviewed using the test data from the Theme Checklists (TC)
-----
' );`

`define( 'TC_POST', 'Feel free to make use of the contact details below if you have any questions,
comments, or feedback:[[br]]
[[br]]
* Leave a comment on this ticket[[br]]
* Send an email to the Theme Review email list[[br]]
* Use the #wordpress-themes IRC channel on Freenode.' );`

My plugin has a short description longer than 150 characters in the readme.txt (due to the ampersand being turned into it's HTML entity taking it over the limit).

However, the API request for 'plugin_information' returns different results for the short_description at different times of the day.

curl --location -g --request GET 'https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request[slug]=wp-user-manager&request[fields]=short_description'

It can return:

The most customizable profiles & community builder WordPress plugin with front-end login, registration, profile customization and content restrict … Which is 150 chars if you don't count ' …'

But then a later call to the API returns:

The most customizable profiles & community builder WordPress plugin with front-end login, registration, profile customization…

It feels like some double trimming is happening somewhere along the line.

We need an admin-only tool that will allow us to mass-email plugins.

One exists but currently can only be run by a server admin, which limits usability.

1) Provide a list of plugins

2) Provide an email subject and body with basic substitutions

3) The tool would then email everyone with commit access and listed owner the message

Substitutions needed:

%USER_EMAIL% %USER_DISPLAY_NAME% %PLUGIN_URL%

With Helpscout you can pre-fill everything BUT the body: ​https://docs.helpscout.com/article/119-pre-fill

So it doesn't look like we can use that for our bulk-mail tool.

If it's secure and has the capability to be given a usable UX, whatever tool is used on the back-end should be fine.

Limiting the number of plugins mailed at a time is also fine. Handling more than 50 of those at a stretch is usually pretty annoying anyway :)

The privacy policy listed on your main privacy policy page (​https://wordpress.org/about/privacy/) appears to be missing the words "will not" in the first paragraph under the section titled "Use of Personal Information".

I believe the sentence should be "We will not use the information you provide to register for an account, attend our events, receive newsletters, use certain other services, or participate in the WordPress open source project in any other way."

It would be helpful if the forums logged who marked a post resolved (or unresovled) as well as closed etc.

From a moderator perspective, this would help track down plugin developers (for example) who automate resolving tickets. It would also mean we'd know who to ping if someone closed a post without a comment.

Example:

• Marked Resolved by Mika 11 Jan 2017, 22:00
• Marked unresolved by Otto 11 Jan 2017, 22:30

or

• Closed by Jan 13 Feb 2017, 11:30
• Opened by Marius 14 Feb 2017, 00:13

While we were building the new bbPress theme we discovered that the WordPress theme live on ​https://wordpress.org/news/ would've been the best starting point. We now had to hack together stuff from various places.

Wouldn't it make sense to open-source that theme used at /news/ as well?

The following legacy pages should be deleted, and 301'd to a sensible location. May also need removing from nav, if this isn't automatic. Likely going to need to do a few passes of these for ones I miss in the initial sweep... Might also be some duplicates.

'Welcome' flavours (should 301 to site root): ​https://fuc.wordpress.org/txt-welcome/ ​https://frp.wordpress.org/txt-welcome/ ​https://kab.wordpress.org/txt-welcome/ ​https://tg.wordpress.org/txt-welcome/ ​https://li.wordpress.org/txt-welcome/ ​https://nl.wordpress.org/txt-welcome/ ​https://tt.wordpress.org/txt-welcome/ ​https://la.wordpress.org/txt-welcome/ ​https://la.wordpress.org/txt-welcome/ ​https://si.wordpress.org/txt-welcome/ ​https://am.wordpress.org/txt-welcome/ ​https://es-cr.wordpress.org/txt-welcome/ ​https://lin.wordpress.org/txt-welcome/ ​https://sq.wordpress.org/txt-welcome/ ​https://es-ar.wordpress.org/txt-welcome/ ​https://oci.wordpress.org/txt-welcome/ ​https://br.wordpress.org/txt-welcome/ ​https://de-ch.wordpress.org/txt-welcome/ ​https://cn.wordpress.org/txt-welcome/ ​https://nb.wordpress.org/txt-welcome/ ​https://bre.wordpress.org/txt-welcome/ ​https://gd.wordpress.org/txt-welcome/ ​https://el.wordpress.org/txt-welcome/ ​https://hr.wordpress.org/txt-welcome/ ​https://cs.wordpress.org/txt-welcome/ ​https://es-mx.wordpress.org/txt-welcome/ ​https://is.wordpress.org/txt-welcome/ ​https://bg.wordpress.org/txt-welcome/ ​https://it.wordpress.org/txt-welcome/ ​https://it.wordpress.org/txt-welcome/logowordcamp/ ​https://lv.wordpress.org/txt-welcome/ ​https://bn.wordpress.org/txt-welcome/ ​https://ms.wordpress.org/txt-welcome/ ​https://fy.wordpress.org/txt-welcome/ ​https://uz.wordpress.org/txt-welcome/ ​https://ug.wordpress.org/txt-welcome/ ​https://as.wordpress.org/txt-welcome/ ​https://mr.wordpress.org/txt-welcome/ ​https://ky.wordpress.org/txt-welcome/ ​https://dv.wordpress.org/txt-welcome/

'Install' flavours (should 301 to the local 'download' page if it exists, and the root if not): ​https://rhg.wordpress.org/txt-install/ ​https://en-gb.wordpress.org/txt-install/ ​https://ku.wordpress.org/txt-install-2/ ​https://fr.wordpress.org/txt-install/ ​https://da.wordpress.org/txt-install/ ​https://li.wordpress.org/txt-install/ ​https://el.wordpress.org/txt-install/ ​https://eu.wordpress.org/txt-install/ ​https://srd.wordpress.org/txt-install/ ​https://so.wordpress.org/txt-install/ ​https://so.wordpress.org/txt-install/ ​https://kab.wordpress.org/txt-install/ ​https://tw.wordpress.org/txt-install/ ​https://fi.wordpress.org/txt-install/ ​https://haz.wordpress.org/txt-install/ ​https://de-ch.wordpress.org/txt-install/ ​https://os.wordpress.org/txt-install/ ​https://es-ar.wordpress.org/txt-install/ ​https://mr.wordpress.org/txt-install/ ​https://es-mx.wordpress.org/txt-install/ ​https://es-co.wordpress.org/txt-install/ ​https://gl.wordpress.org/txt-install/ ​https://nn.wordpress.org/txt-install/ ​https://jv.wordpress.org/txt-install/ ​https://mk.wordpress.org/txt-install/ ​https://fy.wordpress.org/txt-install/ ​https://id.wordpress.org/txt-install/ ​https://ido.wordpress.org/txt-install/ ​https://ms.wordpress.org/txt-install/ ​https://sw.wordpress.org/txt-install/ ​https://ca.wordpress.org/txt-install/ ​https://kn.wordpress.org/txt-install/ ​https://azb.wordpress.org/txt-install/ ​https://sq.wordpress.org/txt-install/ ​https://tl.wordpress.org/txt-install/ ​https://zh-hk.wordpress.org/txt-install/ ​https://es-cr.wordpress.org/txt-install/ ​https://pl.wordpress.org/txt-install/ ​https://ko.wordpress.org/txt-install/ ​https://oci.wordpress.org/txt-install/ ​https://ky.wordpress.org/txt-install/ ​https://fa-af.wordpress.org/txt-install/ ​https://th.wordpress.org/txt-install/ ​https://bn.wordpress.org/txt-install/ ​https://as.wordpress.org/txt-install/ ​https://pan.wordpress.org/txt-install/ ​https://az-tr.wordpress.org/txt-install/ ​https://lin.wordpress.org/txt-install/ ​https://vi.wordpress.org/txt-install/ ​https://fr-be.wordpress.org/txt-install/ ​https://ka.wordpress.org/txt-install/ ​https://xho.wordpress.org/txt-install/ ​https://hu.wordpress.org/txt-install/ ​https://fr-ca.wordpress.org/txt-install/ ​https://is.wordpress.org/txt-install/ ​https://dzo.wordpress.org/txt-install/ ​https://sv.wordpress.org/txt-install/ ​https://ko.wordpress.org/txt-install/ ​https://sr.wordpress.org/txt-install/ ​https://co.wordpress.org/txt-install/ ​https://bre.wordpress.org/txt-install/ ​https://hr.wordpress.org/txt-install/ ​https://hr.wordpress.org/txt-install/clean-install/ ​https://hr.wordpress.org/txt-install/upgrade/ ​https://gu.wordpress.org/txt-install/ ​https://km.wordpress.org/txt-install/ ​https://ar.wordpress.org/txt-install/ ​https://fa.wordpress.org/txt-install/ ​https://it.wordpress.org/txt-install/ ​https://su.wordpress.org/txt-install/ ​https://tuk.wordpress.org/txt-install/ ​https://sa.wordpress.org/txt-install/ ​https://bs.wordpress.org/txt-install/ ​https://kir.wordpress.org/txt-install/ ​https://yor.wordpress.org/txt-install/ ​https://br.wordpress.org/txt-install/ ​https://nb.wordpress.org/txt-install/ ​https://tt.wordpress.org/txt-install/ ​https://ta.wordpress.org/txt-install/ ​https://uk.wordpress.org/txt-install/ ​https://snd.wordpress.org/txt-install/ ​https://arq.wordpress.org/txt-install/ ​https://tg.wordpress.org/txt-install/ ​https://twd.wordpress.org/txt-install/ ​https://eo.wordpress.org/txt-install/ ​https://ur.wordpress.org/txt-install/ ​https://hr.wordpress.org/txt-install/clean-install/ ​https://ug.wordpress.org/txt-install/ ​https://bcc.wordpress.org/txt-install/ ​https://khk.wordpress.org/txt-install/ ​https://ory.wordpress.org/txt-install/

'Themes' themes ​https://ml.wordpress.org/Themes/

'Sample page' variants ​https://snd.wordpress.org/sample-page/ ​https://tzm.wordpress.org/sample-page/ ​https://rup.wordpress.org/sample-page/ ​https://az-tr.wordpress.org/sample-page/ ​https://os.wordpress.org/sample-page/ ​https://lin.wordpress.org/sample-page/ ​https://twd.wordpress.org/sample-page/ ​https://fur.wordpress.org/sample-page/ ​https://sa.wordpress.org/sample-page/ ​https://pan.wordpress.org/sample-page/ ​https://la.wordpress.org/sample-page/ ​https://as.wordpress.org/sample-page/ ​https://bre.wordpress.org/sample-page/ ​https://fuc.wordpress.org/sample-page/ ​https://tt.wordpress.org/sample-page/ ​https://azb.wordpress.org/sample-page/

'Releases' variants ​https://cs.wordpress.org/releases/

'Contact' variants ​https://es-pr.wordpress.org/contact/ ​https://ur.wordpress.org/contact/ ​https://kal.wordpress.org/contact/ ​https://eu.wordpress.org/argitaraketak/ ​https://dzo.wordpress.org/contact/ ​https://scn.wordpress.org/contact/ ​https://ps.wordpress.org/contact/ ​https://es-mx.wordpress.org/contact/ ​https://km.wordpress.org/contact/ ​https://tah.wordpress.org/contact/ ​https://ta.wordpress.org/contact/ ​https://snd.wordpress.org/contact/ ​https://kir.wordpress.org/contact/ ​https://sna.wordpress.org/contact/ ​https://dv.wordpress.org/contact/ ​https://rhg.wordpress.org/contact/ ​https://mlt.wordpress.org/kuntatt/ ​https://frp.wordpress.org/contact/ ​https://yor.wordpress.org/contact/ ​https://arq.wordpress.org/contact/ ​https://sa.wordpress.org/contact/ ​https://oci.wordpress.org/contact/ ​https://ido.wordpress.org/contact/ ​https://lo.wordpress.org/contact/ ​https://rup.wordpress.org/contact/ ​https://la.wordpress.org/contact/ ​https://fao.wordpress.org/contact/ ​https://kn.wordpress.org/contact/ ​https://me.wordpress.org/contact/ ​https://os.wordpress.org/contact/ ​https://li.wordpress.org/contact/ ​https://twd.wordpress.org/contact/ ​https://es-ar.wordpress.org/contact/ ​https://as.wordpress.org/contact/ ​https://ltz.wordpress.org/contact/ ​https://pan.wordpress.org/contact/ ​https://mya.wordpress.org/contact/ ​https://en-gb.wordpress.org/contact/ ​https://ory.wordpress.org/contact/ ​https://az.wordpress.org/contact/ ​https://tg.wordpress.org/contact/ ​https://te.wordpress.org/contact/ ​https://mri.wordpress.org/contact/ ​https://khk.wordpress.org/contact/ ​https://kin.wordpress.org/contact/ ​https://tuk.wordpress.org/contact/ ​https://az-tr.wordpress.org/contact/ ​https://mk.wordpress.org/contact/ ​https://ast.wordpress.org/contact/ ​https://gu.wordpress.org/contact/ ​https://bre.wordpress.org/contact/ ​https://am.wordpress.org/contact/ ​https://mg.wordpress.org/contact/ ​https://mr.wordpress.org/contact/ ​https://lin.wordpress.org/contact/ ​https://hat.wordpress.org/contact/ ​https://ary.wordpress.org/contact/ ​https://co.wordpress.org/contact/

The per_page argument for the Plugins API query_plugins action seems to return the wrong number of results in some cases.

So, if you limit the per_page to 20, you only get 19 items back event though that there are more than 20 results available.

We are hitting this issue with the WP-CLI plugin search command, which shows the exact count of elements returned. See ​https://github.com/wp-cli/extension-command/issues/156 for the related issue.

Copied over from ​#wp12696:

Replying to apeatling:

It would be awesome if you could pass an ordering parameter to plugins_api() that would allow you to return a list of filtered plugins in a specific order.

I'd love to be able to use the API to return a list of the most popular / newest / recently updated plugins on the repo that contain the tag "buddypress".

Something like this would be awesome:

$plugins = plugins_api( 'query_plugins', array( 'tag' => 'buddypress', 'page' => 1, 'order' => 'popular' );

Even better, also allow search filtering:

$plugins = plugins_api( 'query_plugins', array( 'tag' => 'buddypress', 'search' => 'album', 'page' => 1, 'order' => 'popular' );

I'd be happy to implement this if I can get access to the API source on WordPress.org.

Reply from Otto:

This wouldn't be terribly difficult to add to the API, but it's pointless until core supports doing it there and is able to request the ordering. So, moving to the plugins component.

Now that the arguments for plugins_api() have been documented, paired with the fact that there are existing filters in plugins_api() for modifying arguments, I think there's now a more compelling case for implementing an 'orderby' (or similar) argument in the dotorg API.

Adding the ​https://core.trac.wordpress.org/browser/trunk/.editorconfig file to the root of the meta repo should help avoid basic coding standards issues when contributing to the meta team.

Using the same .editorconfig from core should not cause any issues with the current meta projects.

​https://editorconfig.org/

Quite often we're sharing code snippets to help our users when providing support. I would love to see the support forums support syntax highlighting. In it's current implementation it's not incredibly helpful to the end user.

Here's an example: ​https://wordpress.org/support/topic/reorder-posts-in-collection?replies=4