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!
Today we deployedDeployLaunching code from a local development environment to the production web server, so that it's available to visitors. some changes to DevHub. These changes focused on making the code references easier to use, understand and navigate. You can read more about the changes in @tellyworth’s post Exploration: improving DevHub.
If you find any issues or have any feedback/suggestions on how we can further improve the code reference you can file a meta ticket or check out the GitHub repository.
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 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 by 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:
I\u2019m with Xavi, I love everything, but the ToC\u2026 I have some doubts deleting it\u2026 but also yes, it needs some changes and improvements.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/meta\/2022\/07\/01\/exploration-improving-devhub\/#comment-9331","unixtime":1656745665,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2022%2F07%2F01%2Fexploration-improving-devhub%2F%23comment-9331&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"
I like the changes mostly, except I agree that the TOC is quite useful on longer pages such as WP_Query. I also think the parameters need to have the bullets to help with scanning, as indentation is often not obvious enough.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/meta\/2022\/07\/01\/exploration-improving-devhub\/#comment-9334","unixtime":1657052444,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2022%2F07%2F01%2Fexploration-improving-devhub%2F%23comment-9334&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"
I am all for option 3! There is too much focus on backwards compatibility and tradition in WP right now. The entire ecosystem is in need of a lot of drastic changes!<\/p>\n","permalink":"https:\/\/make.wordpress.org\/meta\/2022\/07\/01\/exploration-improving-devhub\/#comment-9335","unixtime":1657113945,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2022%2F07%2F01%2Fexploration-improving-devhub%2F%23comment-9335&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"
Those changes look great. Only the removal of the TOC (especially on complex functions\/classes like wp_query) and the indentations for the parameters I\u2018m not a huge fan of.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/meta\/2022\/07\/01\/exploration-improving-devhub\/#comment-9336","unixtime":1657136977,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2022%2F07%2F01%2Fexploration-improving-devhub%2F%23comment-9336&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"
Yeah +1 for the above comments.- Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"
<\/button>- Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1657145078","hasChildren":false,"userLogin":"audrasjb","userNicename":"audrasjb"},{"type":"comment","id":"9338","postID":"20037","postTitleRaw":"Exploration: improving DevHub","cssClasses":"comment byuser comment-author-apeatling even depth-2","parentID":"9333","contentRaw":"I'm working on this in a branch: https:\/\/github.com\/WordPress\/wporg-developer\/tree\/try\/block-theme","contentFiltered":"
\nI agree with all of these changes, but we should not remove the table of content. It\u2019s a great help for everyone (like in the above WP_Query example) and removing it would a big loss in terms of accessibilityAccessibility<\/span> Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both \u201cdirect access\u201d (i.e. unassisted) and \u201cindirect access\u201d meaning compatibility with a person\u2019s assistive technology (for example, computer screen readers). (https:\/\/en.wikipedia.org\/wiki\/Accessibility)<\/span><\/span><\/span>\/usability.
\nMaybe we could display it depending on the length of the content?<\/p>\n","permalink":"https:\/\/make.wordpress.org\/meta\/2022\/07\/01\/exploration-improving-devhub\/#comment-9337","unixtime":1657145077,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2022%2F07%2F01%2Fexploration-improving-devhub%2F%23comment-9337&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":3,"commentDropdownActions":"","commentFooterActions":"
I\u2019m working on this in a branch: Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"<\/button>- Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1657234267","hasChildren":false,"userLogin":"apeatling","userNicename":"apeatling"},{"type":"comment","id":"9339","postID":"20037","postTitleRaw":"Exploration: improving DevHub","cssClasses":"comment byuser comment-author-apeatling odd alt thread-even depth-1","parentID":"0","contentRaw":"Big +1 to number 3 as all the changes are improvements in my opinion.","contentFiltered":"
- Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"
<\/button>- Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1657234421","hasChildren":false,"userLogin":"apeatling","userNicename":"apeatling"},{"type":"comment","id":"9340","postID":"20037","postTitleRaw":"Exploration: improving DevHub","cssClasses":"comment byuser comment-author-adamwood even thread-odd thread-alt depth-1","parentID":"0","contentRaw":"An alternative to removing the ToC entirely which we tried was fixing it to the right of the content on wide screens, and having it inline on medium and below. I've reopened a PR which describes this in more detail. Please take a look and let us know if that could be a solution. I certainly think it's an improvement on the current behaviour.\n\nhttps:\/\/github.com\/WordPress\/wporg-developer\/pull\/126","contentFiltered":"
Big +1 to number 3 as all the changes are improvements in my opinion.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/meta\/2022\/07\/01\/exploration-improving-devhub\/#comment-9339","unixtime":1657234421,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2022%2F07%2F01%2Fexploration-improving-devhub%2F%23comment-9339&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"
An alternative to removing the ToC entirely which we tried was fixing it to the right of the content on wide screens, and having it inline on medium and below. I\u2019ve reopened a PR which describes this in more detail. Please take a look and let us know if that could be a solution. I certainly think it\u2019s an improvement on the current behaviour.<\/p>\n
Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"<\/button>- Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1657247362","hasChildren":false,"userLogin":"adamwood","userNicename":"adamwood"},{"type":"comment","id":"9423","postID":"20037","postTitleRaw":"Exploration: improving DevHub","cssClasses":"comment byuser comment-author-dufresnesteven odd alt thread-even depth-1","parentID":"0","contentRaw":"I have logged an issue tracking feedback related to parameters and their indentation:\n\nhttps:\/\/github.com\/WordPress\/wporg-developer\/issues\/129","contentFiltered":"
I have logged an issue tracking feedback related to parameters and their indentation:<\/p>\n
Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"<\/button>- Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1661487268","hasChildren":false,"userLogin":"dufresnesteven","userNicename":"dufresnesteven"},{"type":"comment","id":"9427","postID":"20037","postTitleRaw":"Exploration: improving DevHub","cssClasses":"comment byuser comment-author-milana_cap even thread-odd thread-alt depth-1","parentID":"0","contentRaw":"As many have already noted, I love all the changes except for ToC. It's not just how people are use to use it. Take a look at pages such as WP_Query. Without ToC It's almost impossible to use it. I don't have a good solution but am more than happy to help in anyway I can.","contentFiltered":"
- Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"
<\/button>- Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1661932243","hasChildren":false,"userLogin":"milana_cap","userNicename":"milana_cap"},{"type":"comment","id":"9428","postID":"20037","postTitleRaw":"Exploration: improving DevHub","cssClasses":"comment byuser comment-author-samanthaxmunoz odd alt depth-2","parentID":"9427","contentRaw":"Agreed - perhaps a collapsable \/ expandable TOC might be an option?\n\nThe current placement isn't ideal, but it would be helpful to maintain that functionality for people who use it.","contentFiltered":"
- Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"
<\/button>- Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1661942480","hasChildren":false,"userLogin":"samanthaxmunoz","userNicename":"samanthaxmunoz"},{"type":"comment","id":"9429","postID":"20037","postTitleRaw":"Exploration: improving DevHub","cssClasses":"comment byuser comment-author-themiked even thread-even depth-1","parentID":"0","contentRaw":"As others have said, don't hide the toc. It's very useful and not only for complicated pages like https:\/\/developer.wordpress.org\/reference\/classes\/wp_query\/","contentFiltered":"
- s
- search
- c
- compose new post
- r
- reply
- e
- edit
- t
- go to top
- j
- go to the next post or comment
- k
- go to the previous post or comment
- o
- toggle comment visibility
- esc
- cancel edit post or comment
As many have already noted, I love all the changes except for ToC. It\u2019s not just how people are use to use it. Take a look at pages such as WP_Query. Without ToC It\u2019s almost impossible to use it. I don\u2019t have a good solution but am more than happy to help in anyway I can.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/meta\/2022\/07\/01\/exploration-improving-devhub\/#comment-9427","unixtime":1661932243,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2022%2F07%2F01%2Fexploration-improving-devhub%2F%23comment-9427&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"
Agreed \u2013 perhaps a collapsable \/ expandable TOC might be an option?<\/p>\n
The current placement isn\u2019t ideal, but it would be helpful to maintain that functionality for people who use it.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/meta\/2022\/07\/01\/exploration-improving-devhub\/#comment-9428","unixtime":1661942480,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2022%2F07%2F01%2Fexploration-improving-devhub%2F%23comment-9428&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"
As others have said, don\u2019t hide the toc. It\u2019s very useful and not only for complicated pages like Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"<\/button>- Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1661961886","hasChildren":false,"userLogin":"theMikeD","userNicename":"themiked"},{"type":"comment","id":"9430","postID":"20037","postTitleRaw":"Exploration: improving DevHub","cssClasses":"comment byuser comment-author-themiked odd alt thread-odd thread-alt depth-1","parentID":"0","contentRaw":"Item 7 is a very bad UX mistake. The purpose of this page is to assist developers, so don't hide stuff. If you hide this, why stop there? why not hide everything? Why only this one? What problem is this solving?","contentFiltered":"
Item 7 is a very bad UXUX<\/span> UX is an acronym for User Experience - the way the user uses the UI. Think \u2018what they are doing\u2019 and less about how they do it.<\/span><\/span><\/span> mistake. The purpose of this page is to assist developers, so don\u2019t hide stuff. If you hide this, why stop there? why not hide everything? Why only this one? What problem is this solving?<\/p>\n","permalink":"https:\/\/make.wordpress.org\/meta\/2022\/07\/01\/exploration-improving-devhub\/#comment-9430","unixtime":1661962033,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2022%2F07%2F01%2Fexploration-improving-devhub%2F%23comment-9430&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"- Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"
<\/button>- Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1661962033","hasChildren":false,"userLogin":"theMikeD","userNicename":"themiked"},{"type":"comment","id":"9435","postID":"20037","postTitleRaw":"Exploration: improving DevHub","cssClasses":"comment byuser comment-author-dufresnesteven even thread-even depth-1","parentID":"0","contentRaw":"Noting that the Table of Contents was restored in:\n\nhttps:\/\/github.com\/WordPress\/wporg-developer\/pull\/126","contentFiltered":"
Noting that the Table of Contents was restored in:<\/p>\n
Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"<\/button>- Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1662356941","hasChildren":false,"userLogin":"dufresnesteven","userNicename":"dufresnesteven"},{"type":"comment","id":"9436","postID":"20037","postTitleRaw":"Exploration: improving DevHub","cssClasses":"comment byuser comment-author-devnel odd alt depth-2","parentID":"9430","contentRaw":"I would agree if this was content that already existed on the page. In this case, this is displaying helpful content that exists on other<\/em> pages that may add additional context. Since this isn't necessarily needed by everyone. I think, hiding this info that wasn't there before, provides a useful differentiation for content that is referenced from somewhere else.","contentFiltered":"
I would agree if this was content that already existed on the page. In this case, this is displaying helpful content that exists on other<\/em> pages that may add additional context. Since this isn\u2019t necessarily needed by everyone. I think, hiding this info that wasn\u2019t there before, provides a useful differentiation for content that is referenced from somewhere else.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/meta\/2022\/07\/01\/exploration-improving-devhub\/#comment-9436","unixtime":1662361803,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2022%2F07%2F01%2Fexploration-improving-devhub%2F%23comment-9436&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"- Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"
<\/button>- Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1662361803","hasChildren":false,"userLogin":"devnel","userNicename":"devnel"},{"type":"comment","id":"9438","postID":"20037","postTitleRaw":"Exploration: improving DevHub","cssClasses":"comment byuser comment-author-kingkool68 even thread-odd thread-alt depth-1","parentID":"0","contentRaw":"
Site resources