Areas to contribute

As a team, we contribute by supporting design across the entire project. Listed here are just some of the ways you can contribute currently.

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. focuses Core focuses

Currently, the focus is on GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. phase two, but we also are involved in several components within core:

  • Editor: to help go along to weekly meetings:
    18:00 CEST on Wednesday and join #core-editor.

Top ↑

Calls for design Calls for design

We have a list of current designs needed here and the Team TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the team uses for example: board here.

Top ↑

Core TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. design feedback Core Trac design feedback

We have two keywords in trac which we as a team can help with: ‘UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it.-feedback’ and ‘UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.-feedback’. What is trac? Trac is where bugs are reported and enhancement requests are made for WordPress.

Ideally, to do this, you will have a working local testing environment, however some tickets you will not need that for. Here is how a typical workflow would look for feedback in trac:

  1. Visit the report here.
  2. Ideally, work the oldest ticket first, you can click on the ‘modify’ column to sort.
  3. Click a ticket number or summary to view it.
  4. Read the entire ticket to know the full picture. If there is something to test then do that.
  5. Add your response as feedback, or make a mock-up and if required you can even make a patch. This is a great way to find tickets to get involved in.
  6. If you feel this ticket has enough feedback or needs no more (often it is good to get a few opinions), you can go a step further and mark as having feedback. This removes it from the report. Be aware you don’t have to do this step, most tickets need a lot of feedback.
  7. To flag as having had feedback, click the word ‘manual’ by the keyword:
  8. Once you click ‘modify’ you can the add the word ‘has’ to the feedback tag:
  9. Click ‘submit changes’ and now the ticket will not show in the feedback report.
  10. If you find a ticket you think needs action or discussion; bring it to the design team weekly meeting. You can also drop it on the channel at any time, but the meeting will get a faster response. Each meeting usually has a post on asking for topics, so if you can’t make the meeting, you can add a comment there.
  11. To learn about the terms used in trac and core, check out the Glossary.

Note: Please note that mentioning the tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. ticket on SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at will change its date. This means that it will move in the triage list. So if you do so, please make sure to update the ticket if possible.

Top ↑

Meta Trac design feedback Meta Trac design feedback

In addition to Core Trac, we have a second Trac for issues related to the website and associated projects, Meta Trac. You won’t need a local testing environment to work on most Meta tickets. Visit the “Needs Designer” report to get started.

Last updated: