Title: docs – Make WordPress.org --- # Tag Archives: docs [ ](https://profiles.wordpress.org/dufresnesteven/) [Steve Dufresne](https://profiles.wordpress.org/dufresnesteven/) 5:47 am _on_ September 5, 2022 Tags: [devhub ( 4 )](https://make.wordpress.org/meta/tag/devhub/), docs    # 󠀁[Improving DevHub Code References](https://make.wordpress.org/meta/2022/09/05/improving-devhub-code-references/)󠁿 Today we deployedDeploy Launching 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](https://profiles.wordpress.org/tellyworth/)’ s post [Exploration: improving DevHub](https://make.wordpress.org/meta/2022/07/01/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](https://meta.trac.wordpress.org/newticket) or check out the [GitHub repository](https://github.com/WordPress/wporg-developer). Thanks! cc +make.wordpress.org/docs/ +make.wordpress.org/core/ [#docs](https://make.wordpress.org/meta/tag/docs/) [#devhub](https://make.wordpress.org/meta/tag/devhub/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2022%2F09%2F05%2Fimproving-devhub-code-references%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/tellyworth/) [Tellyworth](https://profiles.wordpress.org/tellyworth/) 5:38 am _on_ July 1, 2022 Tags: [devhub ( 4 )](https://make.wordpress.org/meta/tag/devhub/), docs    # 󠀁[Exploration: improving DevHub](https://make.wordpress.org/meta/2022/07/01/exploration-improving-devhub/)󠁿 Recently some of us on the 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. team did some experimenting with hypothetical changes to the [WordPress Developer Docs](https://developer.wordpress.org/), especially the [function reference](https://developer.wordpress.org/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](https://github.com/WordPress/wporg-developer/). 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](https://href.li/?https://github.com/WordPress/wporg-developer) with a fork of the necessary code, including the Handbook pluginPlugin A 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/](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](https://href.li/?https://github.com/WordPress/wporg-developer/pull/74) from 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 by the repository owner. [https://github.com/](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()](https://href.li/?https://developer.wordpress.org/reference/functions/get_posts/). I’ve highlighted some of the more visible things we changed: [[ Before [[ After And below the fold on a function like [wp_authenticate()](https://href.li/?https://developer.wordpress.org/reference/functions/wp_authenticate/): [[ Before [[ After [Continue reading →](https://make.wordpress.org/meta/2022/07/01/exploration-improving-devhub/#more-20037) [#devhub](https://make.wordpress.org/meta/tag/devhub/), [#docs](https://make.wordpress.org/meta/tag/docs/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2022%2F07%2F01%2Fexploration-improving-devhub%2F%23respond&locale=en_US)