__group__ ticket summary component milestone type created _changetime _description _reporter DrewAPicture 1866 "Add a basic ""suggest an edit"" workflow to the handbooks plugin" Handbooks enhancement 2016-07-29T15:22:51Z 2020-05-04T16:53:17Z "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 [https://wordpress.org/plugins/post-forking/ 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." DrewAPicture Otto42 2699 Add a new role to the forums: plugin/theme support Support Forums enhancement 2017-04-07T14:55:18Z 2023-05-25T14:48:55Z " Plugin and theme authors currently have the power to mark threads as resolved within their own support forum, which is great. '''Problem description''' However, some of the larger plugin/theme shops have a support team to help out on their own support forums. I think it would be useful to be able to recognize those people in the support forums, like we’re able to recognize authors. '''Proposal''' So what I would like to propose is adding a new role: Plugin/Theme Support. Everyone with this role should have rights to mark topics within their own support forum as resolved, and should not be affected by posting speed limitations for their own support forum. This role should also show in the forums as ‘Support’, similar to author. The reason why I propose a new role, instead of adding the capability to the contributor role is because, in my opinion, they serve a different purpose. Let me explain. A contributor is someone who helped your open source project forward. This can be by providing feedback, writing code, creating images, doing marketing or being a friend of the project, for example. Someone working on support does contribute his/her (paid) time to your project and is in that way a contributor. However, I think there are more than enough valid use cases where you don’t want someone who contributed code (for example) once to be able to close support request on behalf of the author. That’s why I think having a separate support role would be viable. It would show the community that this person is vetted and answering on behalf of the plugin/theme author. '''Related ticket''' This proposal is related to ticket #2598. '''Managing support role''' Of course, it should be possible for plugin authors to manage the list of support people. I see two reasonable ways to do so, which should be mutually exclusive. One way is by adding the usernames to the `readme.txt` file, the same way contributors are currently added. The other way would be to add users the same way committers are currently added, on the Advanced View of the plugin. '''Showing support staff''' To be transparent about this, we’d probably also need a place to list people in the support role. This could be the Advanced View page, or even the plugin page itself. " TacoVerdo Otto42 4825 Add Enterprise content to wordpress.org General Q1 enhancement 2019-11-05T18:14:42Z 2020-11-18T19:08:48Z "The Enterprise Growth council has been working on content geared toward enterprise decision-makers as a companion to the content the Growth Council created in 2018. This is essentially a microsite that will live at wordpress.org/enterprise. All the content and designs required for this is here: https://drive.google.com/open?id=1lRpTt88b5bcdbiClPNZwmVP6w1q1QGFJ and here: https://docs.google.com/spreadsheets/d/1uPa6m2hVb4Oz-qOvTEDn2FUC1-uBRVoDvohc7YNmYRY/edit#gid=0 Any additional coordination with the council can take place in #council-ops [https://wordpress.slack.com/archives/C9GG77GRJ]" chanthaboune Otto42 4123 Proposal to improve the main navigation menu accessibility General defect (bug) 2019-01-29T18:14:14Z 2023-06-13T06:25:20Z "Several [https://www.w3.org/TR/wai-aria-practices-1.1/#html5-sectioning-elements HTML5 sectioning elements] automatically create [https://www.w3.org/TR/wai-aria-1.1/#landmark_roles 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 `