Title: developer-hub – Make WordPress.org --- # Tag Archives: developer-hub [ ](https://profiles.wordpress.org/ndiego/) [Nick Diego](https://profiles.wordpress.org/ndiego/) 7:33 pm _on_ December 15, 2023 Tags: developer-hub, [website-redesign ( 13 )](https://make.wordpress.org/meta/tag/website-redesign/) # 󠀁[Developer Resources gets a refresh](https://make.wordpress.org/meta/2023/12/15/developer-resources-gets-a-refresh/)󠁿 After many months of hard work, the redesign for the [Developer Resources](https://developer.wordpress.org/) section of WordPress.orgWordPress.org The 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/](https://wordpress.org/) was launched yesterday. The goal was to provide an aesthetic refresh, update the site to a blockBlock 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. theme, and provide a consistent layout throughout the site. Congratulations to everyone who was involved in this effort. You can view the [announcement post](https://wp.me/p2QFvb-7L6) for a more detailed overview of this project. All development took place in the [wporg-developer](https://github.com/WordPress/wporg-developer) 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/) repository, and the design was done in [Figma](https://www.figma.com/file/2WxlJFzMJvqPfZL1EkAOVp/Developer-Resources?type=design&node-id=2934-6071&mode=design&t=q607b55vFlXIUjuB-0). Here’s a look at the new [homepage](https://developer.wordpress.org/) followed by a [sample page](https://developer.wordpress.org/block-editor/getting-started/devenv/get-started-with-create-block/) from the Block Editor Handbook. [[ _The redesigned homepage versus the previous site._ [[ _A redesigned single page layout versus the previous site._ ## Design is content This redesign focused on updating the theme structure, fonts, spacing, colors, etc. It did not touch any content in the various handbooks that comprise Developer Resources. Yet, the content is why we all visit this section of WordPress.org.  Therefore, now that Developer Resources is updated, this is the perfect time to audit and improve the content throughout. Updating documentation, especially quick fixes like formatting and grammar, is one of the best ways new (or returning) contributors can help support the WordPress project.  If you are interested in contributing to documentation, please check out the resources below.  * [Documentation Team](https://make.wordpress.org/docs/) * [Documentation Issue Tracker](https://github.com/WordPress/Documentation-Issue-Tracker) * [Gutenberg GitHub repository](https://github.com/WordPress/gutenberg/blob/trunk/CONTRIBUTING.md)( Block Editor Handbook) * [Theme Handbook Overhaul tracking ticket](https://github.com/WordPress/Documentation-Issue-Tracker/issues/816) As with all changes to WordPress.org, this redesign is just a single iteration, with many more to come in the future. So, if you find an issue or have suggestions for larger functional changes, feel free to open an issue on [GitHub](https://github.com/WordPress/wporg-developer/issues). You will also see several issues already on deck for the [next iteration](https://github.com/WordPress/wporg-developer/milestone/4). Finally, make sure to join the [#website-redesign](https://wordpress.slack.com/archives/C04U953K77A) SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel if you are interested in additional updates coming to WordPress.org and want to contribute. Thanks! _Props to @greenshady for reviewing this post and providing feedback._ +make.wordpress.org/docs/ +make.wordpress.org/themes/+make.wordpress.org/plugins/ +make.wordpress.org/design/+make.wordpress.org/marketing/+make.wordpress.org/accessibility/ [#website-redesign](https://make.wordpress.org/meta/tag/website-redesign/) [#developer-hub](https://make.wordpress.org/meta/tag/developer-hub/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2023%2F12%2F15%2Fdeveloper-resources-gets-a-refresh%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/ndiego/) [Nick Diego](https://profiles.wordpress.org/ndiego/) 9:24 pm _on_ November 22, 2023 Tags: developer-hub, [website-redesign ( 13 )](https://make.wordpress.org/meta/tag/website-redesign/) # 󠀁[Redesigning Developer Resources and a call for testing](https://make.wordpress.org/meta/2023/11/22/redesigning-developer-resources-and-a-call-for-testing/)󠁿 Over the past few months, contributors have been working on a new design for the [Developer Resources](https://developer.wordpress.org/) section of WordPress.orgWordPress. org The 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/](https://wordpress.org/), which includes the official Code Reference, BlockBlock 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. Editor Handbook, Theme Handbook, and much more.  This project aims to refresh the aesthetics of the Developer Resources section, convert the site to a block theme, and improve the overall developer experience. While this redesign includes few functional changes and virtually no content changes, the size of the site makes this project one of the largest we have tackled so far. All development work is taking place in the [wporg-developer](https://github.com/WordPress/wporg-developer) 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/) repository, and you can view the staging site here: [developer.wordpress.org/redesign-test](https://developer.wordpress.org/redesign-test/)_._ ## Design The Developer Resources redesign follows the new WordPress.org aesthetic that debuted with the [Showcase redesign](https://make.wordpress.org/meta/2023/10/11/revitalizing-the-wordpress-showcase/) last month. Given that this is developer documentation, the design takes a slightly more minimalistic and content-first approach. You can view the comprehensive design, as well as all previous iterations, in [Figma](https://www.figma.com/file/2WxlJFzMJvqPfZL1EkAOVp/Developer-Resources?type=design&node-id=2934-6071&mode=design&t=q607b55vFlXIUjuB-0). Below is the redesigned [homepage](https://developer.wordpress.org/redesign-test). [[ _The redesigned homepage versus the current site._ The internal page design takes inspiration from other popular documentation sites, such as [React](https://react.dev/learn/reacting-to-input-with-state) and [MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript). Visitors are presented with the familiar layout of a chapter list on the left, content in the middle, and a table of contents on the right. Here’s a [sample page](https://developer.wordpress.org/redesign-test/block-editor/getting-started/devenv/get-started-with-create-block/) from the Block Editor Handbook. [[ _A redesigned single page layout versus the current site._ ## Development While the new design is the most apparent change, Developer Resources will soon be powered by blocks. Specifically, it’s a [custom child theme](https://github.com/WordPress/wporg-developer) that sits atop the WordPress.org [parent block theme](https://github.com/WordPress/wporg-parent-2021). Much like the newly redesigned [Showcase](https://wordpress.org/showcase/) site, this structure allows us to take advantage of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. functionality like Group and Query blocks as well as custom blocks explicitly built for WordPress. org. As we continue to migrate sections of the WordPress.org network to block themes, each subsequent project will become easier and build off prior work. For example, we completed the standardization of layout and spacing variables as part of the Showcase redesign last month.  ## Content The content and existing content management processes for all internal sections of Developer Resources will not change as part of the redesign work. The one minor exception is the homepage, as can be seen in the screenshot above. The content for the new homepage was based on the [existing site](https://developer.wordpress.org/) but now uses a “card” layout. This new design is highly adaptable, and additional cards can be added easily. The one new addition is a listing of the latest [Developer Blog](https://developer.wordpress.org/news/) posts.  [[ _The Developer Blog posts list on the homepage_ In the last year, the Blog has become a valuable community-driven resource for content that complements the official developer documentation. Surfacing the latest posts on the homepage will increase its visibility. The Developer Blog is also [being redesigned](https://github.com/WordPress/wporg-developer-blog/issues/46#) to match the new look of Developer Resources. The goal is for developers to navigate fluidly between blog articles and official developer documentation without feeling like they are visiting two completely different sites.  ## How you can help First, thank you to everyone who has contributed so far to this new Developer Resources redesign, whether in [Figma](https://www.figma.com/file/2WxlJFzMJvqPfZL1EkAOVp/Developer-Resources?type=design&mode=design&t=9Mc4BF6KIm0z0Ts2-0), [GitHub](https://github.com/WordPress/wporg-developer/issues), or the [#website-redesign](https://wordpress.slack.com/archives/C04U953K77A) channel in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). However, we need additional help.  Given the scope of this section, more testing is needed as we look toward launching the new design in early December. While functionality might have moved around, there should be parity between the current site and the staging site.  Here are the major sections of Developer Relations. Each link will take you to the relevant section in the staging site. * [Block Editor Handbook](https://developer.wordpress.org/redesign-test/block-editor/) * [Themes Handbook](https://developer.wordpress.org/redesign-test/themes/) * [Plugins Handbook](https://developer.wordpress.org/redesign-test/plugins/) * [Common APIs](https://developer.wordpress.org/redesign-test/apis/) * [Advanced Administration](https://developer.wordpress.org/redesign-test/advanced-administration/) * [Code Reference](https://developer.wordpress.org/redesign-test/reference/) * [REST API](https://developer.wordpress.org/redesign-test/rest-api/) * [WP-CLI Commands](https://developer.wordpress.org/redesign-test/cli/commands) * [Coding Standards](https://developer.wordpress.org/redesign-test/coding-standards/) If you would like to propose a change or report an issue, please do so in the [wporg-developer](https://github.com/WordPress/wporg-developer/issues) GitHub repository. Please ensure your issue has not already been reported before opening a new one. **The goal is to wrap up all testing and quality assurance by the end of next week (12/1). ** As with all changes to WordPress.org, this redesign is just a single iteration, with many more to come in the future. So, if you have suggestions for larger functional changes, feel free to propose those as well.  Also, make sure to join the [#website-redesign](https://wordpress.slack.com/archives/C04U953K77A) Slack channel if you are interested in additional updates coming to WordPress.org and want to contribute. Thanks! _Props to @laurlittle, @markoserb, and [@adamwood](https://profiles.wordpress.org/adamwood/) for reviewing this post and providing feedback._ +make.wordpress.org/docs/ +make.wordpress.org/themes/+make.wordpress.org/plugins/ +make.wordpress.org/design/+make.wordpress.org/marketing/ [#website-redesign](https://make.wordpress.org/meta/tag/website-redesign/) [#developer-hub](https://make.wordpress.org/meta/tag/developer-hub/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2023%2F11%2F22%2Fredesigning-developer-resources-and-a-call-for-testing%2F%23respond&locale=en_US)