This post summarizes the latest Default Theme meeting (agenda, slack transcript).
Status update
Most presets are now part of the theme, and work is being done on the different templates and patterns. The repository now has priority labels to indicate the urgency of specific issues and pull requests.
Over 20 contributors have participated so far, and over 60 open issues are in the GitHub 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/ repository. Many are related to block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. patterns, and the ones with the “Need Dev” label are ready to be worked on.
https://github.com/WordPress/twentytwentyfive/issues
A decision was made not to use domains or brands in graphic elements or patterns. More about that discussion and decision here. There were also conversations on how to improve the process of getting the images from the Figma file to add them to the theme, which resulted in hosting the images in a public directory.
Priorities
With the different presets already in the theme, contributors are ready to start working on the different theme styles. Next, the alternative templates for photo blog (versus network, site), complex blog and personal blog.
At the same time, work needs to be completed on block patterns to be used in the creation of other layouts, such as landing pages.
Open floor
@joen mentioned that there’s a good list of Gutenberg-related issues to the theme development, created by @poena, and that he’d be willing to help expedite those.
@beafialho asked how to proceed with implementing templates, when parts are still being discussed or there are independent issues to work on. The conclusion was that as long as there’s communication on why there are things that are not being fully implemented according to the design, and there are links to the other issues we can move forward to expedite things.
@beafialho also asked about creating GitHub issues vs. opening PRs directly when she finds issues with the implementation. The idea is that if the issues found are quick to fix, a PR could be the best way to expedite things. If the issues found are related to bigger changes, then creating GitHub issues would be the best way to proceed. As it can open up the game for contributors to work on those, and it’ll keep track of the progress and what happened.
Thanks to @poena for reviewing the summary.
#bundled-theme, #core-themes, #summary, #twenty-twenty-five
