Welcome to the MetaMetaMeta 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. Team!
The Meta team is responsible for maintaining and managing WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ websites. Our work is mostly done on the meta trac. If you see a bug, file a ticket!
Recently some of us on the MetaMetaMeta 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. team did some experimenting with hypothetical changes to the WordPress Developer Docs, especially the function reference. As developers and frequent users of the docs, we’re aware of its shortcomings and potential for improvement. In order not to risk breaking anything and give ourselves freedom to make significant changes, we forked the codebase into an experimental repo.
The changes we came up with turned out to be quite solid and sensible, and I think most of them are good enough for production. Since they were made as unilateral experiments, we’d like to hear feedback from the +make.wordpress.org/docs/ team and community in general as to what should happen next. You’ll find an outline of some of the most notable changes below.
A local development environment
We started by setting up a fresh repository with a fork of the necessary code, including the Handbook pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, phpdoc-parser, and the current theme. The repo contains a complete local Docker environment, so you can run a copy on your local machine to develop and test changes. The local environment imports function reference content by parsing phpdocs just like in production; and it also imports some handbook content from GitHubGitHubGitHub is a website that offers online implementation of git repositories that can 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/. It doesn’t import all handbook content, but there’s enough for testing purposes.
Visible changes
Here’s a typical function reference page you’ve probably seen before: get_posts(). I’ve highlighted some of the more visible things we changed:
Apart from Editor modifications to make the BlockBlockBlock 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. Editor accessible on the front page, it was built almost entirely with GutenbergGutenbergThe 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/ 🥳.
I invite you to read more about the project in Redesign of the Gutenberg Page, and if you have any feedback, find any issues, or want to get involved, head over to the theme repository.
Over the course of the last year, community members from the metaMetaMeta 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. team and the theme review team have been working together, testing new ways to make theme reviews quicker and easier without compromising the quality of themes in the directory. We improved existing tools, added new tools, opened up direct SVNSVNApache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. commits, and audited theme review rules. As a result, the average time for themes to be reviewed has decreased:
Period
Avg Days to Review
Change
2020 January
129
2021 January
60
53% Decrease
2022 January
5
90% Decrease
Note: Changes in theme upload numbers are not really statistically relevant.
What’s next?
Improving developer experience and simplifying the theme review process is an ongoing process and requires active participation from theme authors and contributors. If you are interested in contributing, follow the theme blog, join the slack chat or participate in the appropriate code repository (listed below).
Also, in order to make better, data-driven decisions, we have created a theme review stats page that will help us track how long it’s taking for theme reviews to complete and some other related theme information.
I want to thank @poena@kafleg and all the members of the Theme Review team who participated!
To get a quick overview across all teams, WordCamp CentralWordCamp CentralWebsite for all WordCamp activities globally. https://central.wordcamp.org includes a list of upcoming and past camp with links to each., WPTV, HelpHub, DevHub, and more, it would help to have a single location to show what activity is happening.
Ideally, this should live natively on WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ in a visible location. Make WordPress Team Updates could be a good home, as well as Project Updates, as this encompasses the entire WordPress project. or creating a unique site could work as well.
Using a pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to import the RSS would make quick work of deployingDeployLaunching code from a local development environment to the production web server, so that it's available to visitors. this idea.
In preparation for the work, I have moved the original WordPress.org Gutenberg theme into its own repository, matching the structure of the WordPress News Theme. This will help open up development since contributors won’t need to set up the full metaMetaMeta 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. environment to contribute. Check out the repository.
Stories
I also went through the latest designs and pulled out some high-level feature sets, framed them as user stories, and added them as issues in the GitHub repository.
I have also added some tasks to those user stories, although there is still more work to be done there.
What’s next?
I have started experimenting with the theme to gain insight into the project and have implemented a few things. Before I go any further, I would like to invite anyone interested to provide feedback or participate by creating, commenting, or assigning themselves to an issue in the GitHub repository.
In last week’s MetaMetaMeta 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. meeting, we discussed the idea of more directly involving community teams in the Meta components most relevant to them.
In particular, we’d like to explore the idea of each Meta component having a liason or maintainer appointed by the relevant team. Someone from the Support team assigned to the Support Forum component, for example, and a Polyglots teamPolyglots TeamPolyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. member on both Translate Site and Rosetta.
Those liasons would be expected to help triage tickets, set priorities, and identify the issues that are most important to the team. They would not be expected to fix the issues themselves.
I’d like to invite all teams to offer their feedback and suggestions on the idea. If any teams have contributors who would like to volunteer to try it out in practice, I don’t see any reason we can’t start a trial more or less immediately.
Last year we launched the Block Pattern Directory, a curated selection of beautiful and useful block patterns hosted on WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ and usable directly from the post editor in any WordPress site.
Soon we plan to open the Pattern Directory to submissions from the public. The Pattern Creator page will allow designers and content creators to build, edit, and submit their best blockBlockBlock 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 to the directory. Approved patterns will be added to the directory, where they will be instantly available to the authors of millions of WordPress sites.
The Pattern Creator is expected to launch next week. In the meantime, we’d like to invite designers, theme developers, and anyone else who loves creating block patterns, to help test the submission process and start submitting and publishing patterns early. If creating and sharing block patterns with the whole world sounds like something you’d love to do, you can get started now.
Themes: if you’d like to see the moderation and approval process we can arrange that. cc +make.wordpress.org/themes/
The Pattern Directory is open sourceOpen SourceOpen 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.. You can participate in its development in the pattern-directory GitHub repository. Suggestions and feedback are welcome on GitHubGitHubGitHub is a website that offers online implementation of git repositories that can 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/ or in comments on this post. Please report any issues you find by filling out a bug report.
