Design contribution process

As WordPress added more open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. projects to its ecosystem and redesigned the News section, it seems a good opportunity to treat the design dimension more broadly and improve the contribution process based on the current practices.

Documentation concerns

When I started working on Openverse redesign, I struggled with finding up-to-date documentation regarding the contribution process. The procedure was slightly unclear as the design handbook suggests making a post in the Design blog and Figma had many projects, making it challenging to navigate through and where to start from.

The redesign task did not have specific tickets, and that is why my first move was to follow the most recent projects in Figma and duplicate their structures. I created a design library file mirroring the structure of the WordPress one and bringing into Openverse some 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. https://wordpress.org/gutenberg/ design features that I considered experience’s backbones.

On the other hand, I recently discovered Gutenberg’s Design Contributions document and it is excellent explaining how to start contributing, describing the design principles, and linking the issues that need design. One place gathering Gutenberg’s design dimension. Unfortunately, it is not part of the existing handbook.

New design needs

Along with Openverse, the Photo Directory and News redesign projects made me think of the opportunity we have to expand the design contribution process and update the documentation to ease the onboarding of new contributors.

We currently have solid practices like the bi-weekly meetings, iteration posts, and the recent design share posts made by Channing. So this is not about starting from scratch but tapping into visible accomplishments.

What I have in mind ranges in the following, without any specific order or priority.

Update the Design handbook documentation: Review the existing content and fix the broken links. Add step-by-step sections to start using Figma, like the duplicate files guide. Expand the meaning of designing WordPress as it tends to refer to be CMS-only.
One structure for all Design Libraries: Update the Openverse Design Library’s file structure to mirror the WordPress one. Same for new upcoming libraries.
One contribution process on GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/: Duplicate the Gutenberg design contribution document into repos where design proposals are shared to match the label logic.

The list above is very task-specific and can evolve quickly into a list of changes, but I still miss some bridge between project priorities and design tasks. Some contributors might hesitate to participate due to priorities unclarity and get lost among the many places where design happens.

I hope you like this idea, and please, feel free to suggest changes and add things that I am missing.

Tammie Lister 2:38 pm on March 13, 2022
It’s often a misconception that a handbook or documentation is ‘done’. It never is. The design team materials were always intended to be a living document and reflect the current form of the design team – whatever that took.

To give some context, you might not be aware of @fcoveram ; it’s not always been just coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. either; it’s included WordCamps, metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. and other teams. Our fabulous designers have a long history of contributing to BuddyPress, bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. and projects that come under our excellent collective ecosystem, so seeing that grow in reflection of the handbook makes sense.

We have had several initiatives around the process, and I think it’s essential that whatever is done is transparent and works for those that work full time and those that only have a few hours to drop in. Each should have a time for proposal and feedback, not just be added. I am not saying that would happen, just vocalising what many want.

There seem to be a few threads you are talking about aside from your numbered list: 
- Surfacing lost evergreen content is crucial for new contributors and those looking to add more.
- We are adding new projects to the ecosystem.
- Unifying processes: this includes the library structure contribution process.
I propose tackling one by one and starting with the content surfacing, working out the journeys and IA needed; what is broken should be fixed. From there, you can quickly know what might be hiding. You might not even have found yourself yet and move into the process.

One note of caution I will raise. The design process likely might vary depending on the repo. There absolutely should be a unifying where possible (labels label is a strong example, and the flow from needs design feedback onto production). However, some variations will happen because of projects.

As someone that has worked across many areas, I’d be happy to help here if you want a view. Let me know where you are looking for contributions, as this post isn’t too clear.
Estela Rueda 2:44 pm on March 14, 2022

You have good ideas and as Tammie said, the handbook is a living document that should be edited as needed. A lot of what is there we wrote when 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. https://wordpress.org/gutenberg/ was barely Gutenberg, so much has changed. As we all know, in design there is no such thing as one-size-fits-all. Each project has its own processes and new contributors bring new ideas.
Looking forward to see what next steps you take and I’ll be happy to help where I can.
Francisco 7:10 pm on March 14, 2022

It’s often a misconception that a handbook or documentation is ‘done’. It never is.

You are very right about that @karmatosed.

I liked how you chunked my points and completely missed the projects you mentioned by my lack of awareness and diving into Openverse primarily. I also agree with @estelaris on the one-size-fits-all misconception and keeping the process flexible as much as it keeps contributions alive. My main concern was the onboarding stage and the risks of losing new contributors due to its lack of clarity.

Regarding the next steps, I would love your help Tammie and Estela to include the projects noted, update outdated content, and fix the broken links. In parallel, I can start editing the Openverse repo by mirroring the 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. https://wordpress.org/gutenberg/ guide and linking the design handbook in Openverse to steer one design documentation. The file structure in Design Libraries is an endless task that I already started, but it would be great to add some screenshots in the handbook.

Comments are closed.

The Design Team provides design for the WordPress project.

More information

Design contribution process

Documentation concerns

New design needs

The Design Team provides design for the WordPress project.

More information

Documentation concerns

New design needs

Share this: