Developer Resources gets a refresh

After many months of hard work, the redesign for the Developer Resources 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/ 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 for a more detailed overview of this project. All development took place in the 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 be the repository owner. https://github.com/ repository, and the design was done in Figma.

Here’s a look at the new homepage followed by a sample page 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. 

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. You will also see several issues already on deck for the next iteration

Finally, make sure to join the #website-redesign SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at 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 #developer-hub

Meeting Agenda for December 13, 2023

👋🏻 Intro/Welcome

🆕 News

Our next meeting falls between holidays for many attendees and often the last week of the calendar year is not the most active for contributors. Should we postpone the meeting 1 week, or skip it and resume on January 10 (11th for some regions)?

This week’s meeting will be held at 21UTC on Wednesday, December 13.

👋🏻 Intro/Welcome

🆕 News

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. news

Cross-team news

Other news

Open Floor

X-post: Update on Matrix Migration: Pausing the Transition

X-comment from +make.wordpress.org/project: Comment on Update on Matrix Migration: Pausing the Transition

Plugin Previews are now available for opt-in

Following up on the last post:

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/ or can be cost-based plugin from a third-party committers can now enable the Preview button for public users on their plugins.

In order for previews to be enabled, a plugin committer must do two things:

  1. Commit a valid blueprint.json file to a subdirectory of the plugin’s assets folder, named assets/blueprints/blueprint.json. Examples of a suitable blueprint file can be found in the previous post.
  2. On the Advanced View tab, use the button to enable previews publicly. It looks like this:

Screenshot 2023-12-08 at 5.03.51 pm

As before, plugin committers can test blueprints with the Preview button without enabling it publicly.

Problems with the toggle button or other parts of the process can be reported on Meta Trac ticket #7251.

X-post: Embracing Matrix for Enhanced Communication

X-comment from +make.wordpress.org/project: Comment on Embracing Matrix for Enhanced Communication

Meeting Agenda for November 29, 2023

This week’s meeting will be held at 21UTC on Wednesday, November 29, 2023, and @courane01 will be hosting.

👋🏻 Intro/Welcome

🆕 News

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. news

Still Open

Cross-team news

    Other news

    Open Floor

    Open Discussion

    Create Tours for Make P2s

    For GlotPress and thus translate.wordpress.org, Polyglots contributors @spiraltee and @amieiro, with the help of @piermario and @lidialab (thank you!), created a tour that is a bit different than tours that you’d usually encounter. Often, tours pop in your face when you visit a website for the first time. This tour indicates its starting point using a glowing dot. You can just ignore it (for now) if you are not interested.

    An animation showing a glowing dot that can be clicked to start a tour. This one cannot be clicked since it's an animation.
    ^ This glowing dot cannot be clicked since it’s just an animation.

    During the tour, that element of the web page will be highlighted like this:

    Since the Polyglot contributors got good feedback about this tour and its potential applicability to other areas of Make WordPress, they then collaborated with 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. contributors @psrpinto and me (@akirk) to convert this tour into a dedicated plugin, simply called Tour, and added an easy way to create such tours (similar like you might know the Inspector of browser developer tools).

    In order to restart a tour that you already completed (or dismissed), and for better accessibilityAccessibility 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 “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), there is also a Masterbar menu to start the tours that are visible on the current page:

    There is also a shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. and an “Available Tours” GutenbergGutenberg The 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/ 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. that allows you to embed the list of tours in a place of your choosing on the website so that there is also an additional path of starting a tour for people who are not logged in (and thus don’t see a Masterbar).

    Demos

    To demo this, we created two videos, one to show what it’s like to go through a tour, and one to show how to create a tour. Finally, a screenshot to show what updating a tour looks like.

    Taking a Tour (Video)

    Creating a Tour (Video)

    Updating a Tour (Screenshot)

    A screenshot of the Edit tour screen that shows individual fields that make up a tour like tour title, step title, text and css selector.
    You can update each step separately (title, text and CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. selector) and HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. is available in the description.

    Also note that tours are a custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. with revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision., so you can undo any changes. While creating, testing, and editing a tour, you can keep it as a draft so that it won’t be visible to users who cannot see drafts.

    The Tour plugin is not yet in the 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/ or can be cost-based plugin from a third-party directory but you can download the ZIP file from Github and install it on any WordPress site.

    On Make WordPress, we have activated the plugin on the Meta and the Polyglots P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. and we’d be happy to activate it on other Make teams if they want to use it on their own P2 for whatever they feel it could be useful.

    Accessibility

    I’d like to give a special invitation to the +make.wordpress.org/accessibility/ team to try the tour and let us know which improvements we’d need to make to make it more accessible. We think that an important aspect to start with is that it doesn’t open up automatically and gets in the way of people who were trying to do something different in the first place. The underlying driver.js library had in the past made some strides to make it accessible and per suggestion from @joedolson, we have added alternative ways (such as the Masterbar or Gutenberg block) to start tours.

    Try It On this P2

    We have created a first tour here on the Meta P2 (see the logo in the blue bar at the top of the page, or start it using the Masterbar). It is just a very quick demo, we’ll probably expand it in future. You can take it to get an idea of how such a tour could work and if you’d like to discuss with your own Make team whether you’d like to try it out as well. Please reach out in the comments!

    Matrix Chat Summaries

    This post is a retrospective of #matrix meetings that happened between August 31st, 2023 and November 23rd, 2023. The meetings were conducted in the #meta channel of the Make WordPress Slack and, in parallel, on Matrix in the room #meta:community.wordpress.org. This was enabled by our SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/./Matrix bridge.

    Summary of all meetings

    • The community.wordpress.org Matrix server is kept “in sync” with the Make.WordPress slack. Messages sent on Slack (in public channels) are automatically posted to a corresponding Matrix room. Newly-created public Slack channels automatically get a new Matrix room.
    • The Matrix rooms contain the complete history of the Slack channels, as if those rooms had existed since always.
    • We’re looking for community feedback on what tooling is needed to address administrative tasks on Matrix, like GDPR erasure, moderation, etc.
    • We’re in the process of migrating Slack integrations to Matrix (e.g, “slash commands”, Welcome Bots, RSS feeds, etc),  but there is still quite some work to be done on this front. We’ve started with making an inventory of all Slack integrations.
    • We have created documentation to visually explain how to join rooms via Matrix:

    August 31, 2023

    Start of the meeting on Slack / Matrix

    • Open floor.
    • Shared progress on the status of the Slack-Matrix bridge, so that messages sent on Slack are also sent to Matrix, and vice-versa.

    September 14, 2023

    Start of the meeting on Slack / Matrix

    September 28, 2023

    Start of the meeting on Slack / Matrix

    • Shared progress on import of private Slack channels. Mentioned users who wish to migrate the history of private channels should get in touch with @akirk @ashfame or @psrpinto.
    • Shared documentation on how to join the community.wordpress.org Matrix server, and on available Matrix clients.
    • Mentioned there are Matrix-based chat pages for each Make team, e.g. https://make.wordpress.org/meta/chat/
    • A Community member asked about how Matrix administrative tasks will differ from Slack (e.g. GDPR erasure requests). 
    • How will the administration differ from Slack? For example Slack has procedures for data erasure requests, that is very important that gets carried over. 
    • Clarified Matrix administration needs (e.g.GDPR erasure requests) are on our radar, but we would like to understand the kind of administrative operations that are more common, so that we can provide necessary tooling for those needs.

    October 12, 2023

    Start of the meeting on Slack / Matrix

    • Open floor.
    • Clarified what Matrix tooling exists and, what is possible to achieve with it, specifically on what concerns integrations (like at-group on Slack).
    • Clarified that there was not yet a date for an eventual Slack-to-Matrix “switch”, and that we were planning on operating both for the time being
    • Clarified that our goal would be to make Matrix the preferred way of joining Making WordPress chat for new people.

    November 9, 2023

    Start of the meeting on Slack / Matrix

    • Open floor.
    • Debugged an issue that prevented a community member from logging in to the Matrix server.

    November 23, 2023

    Start of the meeting on Slack / Matrix

    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 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/, 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 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 be the repository owner. https://github.com/ repository, and you can view the staging site here: developer.wordpress.org/redesign-test

    Design

    The Developer Resources redesign follows the new WordPress.org aesthetic that debuted with the Showcase redesign 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.

    Below is the redesigned homepage.

    The redesigned homepage versus the current site.

    The internal page design takes inspiration from other popular documentation sites, such as React and MDN Web Docs. 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 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 that sits atop the WordPress.org parent block theme. Much like the newly redesigned 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 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 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 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, GitHub, or the #website-redesign channel in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at 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.

    If you would like to propose a change or report an issue, please do so in the wporg-developer 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 Slack channel if you are interested in additional updates coming to WordPress.org and want to contribute. Thanks!

    Props to @laurlittle, @markoserb, and @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 #developer-hub

    Plugin Directory: Preview button revisited

    Based on feedback about our first attempt at testing a plugin preview feature, we have an improved version ready to go. This version builds on feedback and suggestions, and in particular is designed to give 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/ or can be cost-based plugin from a third-party developers the opportunity to safely experiment and test the preview experience for their plugins before making them public.

    About Plugin Previews in the Playground

    If you haven’t noticed it yet, the WordPress Playground is an amazing feature that lets anyone safely run a temporary WordPress install within their browser. It uses WASM to run a complete WordPress install – PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php., database, and all – entirely from within your web browser. No server needed, nothing to install.

    For a while now Playground has supported loading any plugin or theme from the plugin directory; here’s how.

    About the new Plugin Preview button

    As with the last attempt, the new Plugin Preview feature simply adds a convenient button to plugins in the plugin directory. The button takes the user to Playground with that plugin installed. It’s right beside the Download button, like this:

    The important differences this time around are:

    1. The button is double-opt-in. It’s not shown by default for any plugins.
    2. It’s now possible for plugin developers to configure the preview environment and install dependencies (other plugins and themes).
    3. Plugin developers can test the preview before making it available to the public.
    4. Most php extensions are now supported.
    5. Remote network requests are now supported.

    I’ll explain these in more detail below.

    Opt-in.

    There are two things required for a plugin preview button to appear to all users:

    1. A valid blueprint.json file must be provided in a blueprints sub-directory of the plugin’s assets folder.
    2. The plugin preview must be set to “public” from the plugin’s Advanced view by a committer.

    Note: Part 2 is intentionally not yet deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors., meaning no plugin preview buttons are yet available to the public. This is intended to give a grace period for plugin developers to experiment with blueprints, customize the experience, and decide if they want to use it.

    If a valid blueprint.json file is present, then the Preview button will be present for plugin committers only. In which case it will look like this:


    It’s called Test Preview because that’s why it’s there: to allow plugin committers to test their plugin in the Playground environment and decide whether or not to make it easily available to the public.

    Blueprints.

    Blueprints are jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. files used to set up a WordPress Playground instance.

    They can be used to specify things like PHP and WP versions, the landing page, and (most importantly) a series of automated steps such as logging in, and installing and activating plugins and themes.

    The blueprint for your plugin should be committed to the assets folder with subversionSVN Apache 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/. as assets/blueprints/blueprint.json. Initially only the one blueprint file is supported, but we expect to allow multiple in future.

    Here’s an example of a simple blueprint.json file that you could use as a starting point:

    {
        "landingPage": "\/wp-admin\/edit.php",
        "preferredVersions": {
            "php": "7.4",
            "wp": "5.9"
        },
        "phpExtensionBundles": [
            "kitchen-sink"
        ],
        "steps": [
            {
                "step": "login",
                "username": "admin",
                "password": "password"
            }
        ]
    }
    

    The features used here are:

    • landingPage, which specifies the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org of the page that the user will land on when the preview loads.
    • preferredVersions, which specifies versions of PHP and WordPress.
    • phpExtensionBundles, which in this case specifies that we want most common PHP extensions to be available (kitchen-sink).
    • steps, which tells Playground what to do before displaying the landing page. In this case, it will simply log the user in to wp-admin.

    Here’s an example of a more advanced blueprint.json that demonstrates some more features you could use to create a rich demo environment for users:

    {
    	"landingPage": "/wp-admin/post.php?post=5&action=edit",
    	"preferredVersions": {
    		"php": "7.4",
    		"wp": "5.9"
    	},
    	"phpExtensionBundles": [
    		"kitchen-sink"
    	],
    	"steps": [
    		{
    			"step": "login",
    			"username": "admin",
    			"password": "password"
    		},
    		{
    			"step": "installPlugin",
    			"pluginZipFile": {
    				"resource": "wordpress.org\/plugins",
    				"slug": "my-imaginary-plugin-dependency"
    			},
    			"options": {
    				"activate": true
    			}
    		},
    		{
    			"step": "installPlugin",
    			"pluginZipFile": {
    				"resource": "wordpress.org\/plugins",
    				"slug": "my-imaginary-plugin"
    			},
    			"options": {
    				"activate": true
    			}
    		},
    		{
    			"step": "installTheme",
    			"themeZipFile": {
    				"resource": "wordpress.org\/themes",
    				"slug": "my-imaginary-theme"
    			}
    		},
    		{
    			"step": "setSiteOptions",
    			"options": {
    				"some_required_option_1": "your_favorite_values",
    				"some_required_option_2": "your_favorite_values"
    			}
    		},
    		{
    			"step": "runPHP",
    			"code": "<?php\ninclude 'wordpress/wp-load.php';\nwp_insert_post(array(\n'import_id' => 5,\n'post_title' => 'Example Post',\n'post_content' => '<!-- wp:paragraph -->\n<p>a normal paragraph</p>\n<!-- \/wp:paragraph -->',\n'post_status' => 'publish',\n'post_author' => 1\n));"
    		}
    	]
    }
    

    This demonstrates some more advanced Blueprint features such as:

    • Installing plugin dependencies (my-imaginary-plugin-dependency)
    • Installing and activating a theme (my-imaginary-theme)
    • Setting wp_options (some_required_option_1 and some_required_option_2)
    • Running PHP code to create a demo post (runPHP)

    You’ll find much more about Blueprints in the Playground documentation, including several helpful examples.

    Almost any of the documented Blueprint features should work. There are some particular caveats to blueprints as used by the Plugin Preview button feature however:

    • Your blueprint.json file must validate as per PHP’s json_decode() function. If no Test Preview button appears, check that it’s valid. (Note that this means backtick quotes as used in this example are not supported as they are invalid in json) .
    • If you forget to install and activate your own plugin with an installPlugin step, the plugin directory will add that step for you when adding the blueprint to the Preview button.
    • The blueprint will be whitespace-normalized before use.
    • There is a 100kb size limit. This is an arbitrary limit necessary for tedious reasons; I expect we’ll increase or remove it in future.

    What’s next

    We expect to improve on the preview feature in a number of ways. In the short term:

    • We’ll take the preview button out of test mode and allow public use very soon, depending on your feedback.
    • A coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. patch will propose adding an identical Preview button to the plugin directory UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. in core. (Whether or not this is adopted will depend of course on core team discussion and process).
    • Better Blueprint validation and error reporting.
    • Support for multiple blueprint.json files.
    • UI/UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. design improvements.

    In the longer term, we’ll collect and discuss ideas, and post proposals in 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. tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets and/or Make p2 posts.

    Feedback, questions, and support

    You’re welcome to post suggestions, ideas, and questions in comments on this post.

    Over time we’ll direct support questions and requests to other forums as available.