Matt Mullenweg 12:45 pm on August 18, 2022

Navigation

Items in our main navigation are totally out of control. The … it shows when the screen is too wide is not intuitive. It’s unclear why Five for the Future is a drop-down under Get Involved, or why Support needs two sub-menu items.

Finally there’s a duplicate logo, with its own hidden drop-down, in a slightly different dark grey color, in the built-in MS nav bar:

To the right it has its own Register and Log In, and a duplicate search box.

This is a mess! What can we simplify here?

slickremix 12:54 pm on August 18, 2022

Morning! One suggestion would be adding a resources menu option and the drop down would contain the Learn, News, About, Showcase, Mobile and other like menu items?
- Jon Brown 1:28 pm on August 18, 2022
  
  That’s interesting. I’d be inclined to do almost the opposite. Create a “resources” top level item and put plugins, themes, patterns, and mobile under that.
  
  This is 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/, I would think the assumption is folks are new and getting started when they land here. Themes, plugins patterns are more commonly directly accessed from the individual sites dashboard, they don’t need to be top level items here.
Samuel Wood (Otto) 1:05 pm on August 18, 2022

Everybody thinks everything should be top level. Truth is, most of it shouldn’t. Consolidate everything into a few drop downs.
- Matt Mullenweg 12:05 am on August 23, 2022
  
  Drop downs are like sliders — a way to squeeze everything in when people can’t agree what’s actually important.
  - Samuel Wood (Otto) 9:31 pm on August 24, 2022
    
    True. But the truth is we have so many different sections on 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/, with so many different things going on, and so many different ways to contribute. The alternative is to consider a different layout entirely for the site as a whole. Which is not a bad alternative, but, different than the way we’ve traditionally been doing it in the past.
    
    Realistically, we’ve got room for about six or seven top level nav items. Pointing into sections of our existing site is the way it’s been done in the past. But it doesn’t have to be that way. There’s decent arguments are making onboarding pages. Just need to decide what they are.
Courtney Robertson 2:03 pm on August 18, 2022

One possible organization:

About:
Showcase

Extend (or a better name that includes all these):
Plugins
Themes
Patterns
Photos
Openverse
Mobile
Hosting

Support:
Documentation
Forums
Learn
Jobs (https://jobs.wordpress.net)
WPTV

Get Involved:
Handbook
Five for the Future
Overview (Possibly renamed)

Noting that various locales are not the same in handling the navigation. Worth asking Polyglots folks about terminology before the change.

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) folks also noticed that the drop-downs weren’t configured for screen readers. Would suggest consideration from that group as well.

Do we have split testing tools and metrics to conduct some experiments?
- Nicholas Garofalo 2:03 am on August 19, 2022
  I like @courane01‘s approach here because it focuses on visitor intent (Ie. what are they here to do). I’d shift just a few things around and maybe surface some of the About sub-pages.
  
  About
  - Requirements
  - Features
  - Philosophy
  - Showcase
  Download & Extend
  - Plugins
  - Themes
  - Patterns
  - Photos
  - Openverse
  - Mobile
  - Hosting
  Support
  - Documentation
  - Forums
  - Learn
  - WPTV
  Get Involved
  - Five for the Future
  - News
  - Events
  - Jobs
- Nicholas Garofalo 2:09 am on August 19, 2022
  
  Do we have split testing tools and metrics to conduct some experiments?
  
  Testing the main menu is tough because navigation is so suggestive. Plenty of visitors will click every link in the menu just because it’s there. I like to think of the main menu as a statement about what the site author considers important rather than a question for the visitor.
  
  There’s also the issue that testing requires some pretty invasive tracking that a lot of folks are not going to be comfortable with.
- Tellyworth 4:40 am on August 19, 2022
  
  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) folks also noticed that the drop-downs weren’t configured for screen readers.
  
  Are you referring to this bug that was fixed in June? Or is there an ongoing a11yAccessibility 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) issue that we’re not aware of?
Joy 2:05 pm on August 18, 2022

Why isn’t this a ticket in the repo??
Why show the admin bar on the front end?
- Samuel Wood (Otto) 2:51 pm on August 18, 2022
  
  Admin bar wasn’t supposed to show on the home page if you’re logged out. Only page it’s not supposed to do that. Corrected.
geoffgraham 2:26 pm on August 18, 2022

Ooo, I like @courane01‘s outline. I’ll toss an idea into the hat:

Create
Getting Started
Themes
Patterns
Blocks
Hosting

Resources
Tutorials
Lesson Plans
Developer Resources
Mobile Apps
Ooenverse

Community
Latest News
Forums
Documentation
WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.
WordPress TV

Contribute
Contributor Handbook
Meetings
Team Updates
Project Updates
Five for the Future

Get WordPress
- Courtney Robertson 2:30 pm on August 18, 2022
  
  That overview page is an RSS automation from all the teams and their outposts. I haven’t sorted out if there’s a better name and how to organize where that lives on the current Get Involved page, but things move so fast and a single source to see what all teams and such are up to would be really helpful.
  
  I do like the idea of the additional items in Contribute/Get Involved.
  
  Also not sure where to put Jobs, but there’s a Meta trac ticket for it that was closed and not implemented. It is still maintained and sees high quality postings pretty frequently. Footer, top nav as a child, something somewhere. It’s been off the main site for 4 years I think.
- Remkus de Vries 2:58 pm on August 18, 2022
  
  I’m very much in favor of these main navigation items and the items they show in the drop-down as suggested by Geoff!
- David Ryan 2:59 pm on August 18, 2022
  
  I like ‘Contribute’ over Get Involved 💯
  
  I’d also suggest one big omission is Events.
  
  I’m less sure on “Create.” I realize we create using Themes, Plugins, etc… but I think this could get confused with “how to create a 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.”
  
  I’d lean towards “Extend” (though “extension” and “plugin” are a bit too close in meaning for my taste) or another ideation. I’d rule out “Build” and “Make” for being confusing. I think given a different type treatment “Get” could be interesting. “Get Plugins… Get Mobile Apps… Get Hosting…” etc.
  
  But I will play devil’s advocate… I think burying Plugins, Themes and Patterns in a submenu is probably necessary (add Photo directory, another next-gen directory in the future) but are there some items that should be top-level? Do we have analytics we can gleam some prioritization from for order and level?
- Angela Jin 8:30 am on August 19, 2022
  
  Overall, I really like what @courane01 and Geoff have suggested!
  
  Strongly recommend we have Community or Events as top level, as that a key way WordPress brings in new users and contributors.
  
  I’m thinking through Contribute or Get Involved though. If you’re brand new to our space, Contribute could be confused with financial donation.
  - Nalini Thakor 3:46 pm on August 23, 2022
    
    Get involved is a clearer message. Support this idea that contribute the first time new people or potential contributors read it, they may misunderstand it as involving some kind of financial transaction or associate it with submitting code only to a software project. In WordPress terms, it means so much more, and Get involved is an encouraging way to show this.
  - Courtney Robertson 3:26 pm on August 27, 2022
    
    Suggested adding link to Handbook as 2nd item under Get Involved.
Aleks Phell 9:35 pm on August 18, 2022

Agree: “This is a mess! “
Denis Žoljom 11:35 am on August 22, 2022

Am I the only one who is a bit taken aback by this post?

I fully agree that the nav bar is a mess, and something should be done about it, but usually, the process is such that the issue is debated on meetings and tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets, then somebody comes up with a proposal, and then the proposal is debated in the comments and subsequent meetings.

The tone of this post comes off as an order, not a constructive criticism IMO.
- Matt Mullenweg 12:03 am on August 23, 2022
  
  If the design by committee and debate in comments and subsequent meetings had produced something of high quality, we wouldn’t be having this discussion in the first place. There are some excellent suggestions above on how to simplify things, and ultimately we’ll need to just have some decisions on a way forward. Criticizing the tone of this discussion is not bringing us closer to a better outcome for our users — in fact it sounds like you’re ordering how changes should be made.
  - Denis Žoljom 6:39 am on August 23, 2022
    
    Sorry to be blunt, but I’m not the one with the ultimate power in this space. You are, and you are using that power.
    
    So to imply that I’m ordering how changes should be done is extremely hypocritical, not to mention you are using a strawman fallacy here.
    I’m merely saying how things are usually done. And when things aren’t done in that way, all hell is brought upon those who do that.
    
    If the design by committee and debate in comments and subsequent meetings had produced something of high quality, we wouldn’t be having this discussion in the first place.
    
    Were there ever discussions about the nav bar? From what I can remember, one day the nav bar just changed. If there were discussions either 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. or in the design team meetings why weren’t there an official make post about that where we could have had this discussion before things changed?
    
    I’m criticizing the tone of your post because of the double standards and lack of governance.
Sam Munoz 1:43 pm on August 22, 2022

I’m concerned about the admin bar not being shown on the homepage. While I understand that will add 2 WordPress logos (which, other pages also have) – it takes navigating to another page on the site to access the Register / Login links. This is confusing.

Even if we don’t want the admin bar shown on the Homepage, I suggest we have the Register / Login links somewhere on that page or within the navigation.
- Matt Mullenweg 12:04 am on August 23, 2022
  
  I agree, we need to integrate it into the global headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes., but there’s no room until we remove some of the stuff that we’ve put into the navigation.
Matt Mullenweg 11:59 pm on August 22, 2022

I see it’s been dropped from the homepage, but still present many other areas including /news and the forums.
- Samuel Wood (Otto) 9:37 pm on August 24, 2022
  
  The admin bar for logged out users In most places where it’s used, it’s used because of the login link. Because of that, you can merge it with the global headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. if desired, and thus eliminate it being necessary. Easy enough to do. But takes up some space.
Matt Mullenweg 12:07 am on August 23, 2022

From a user point of view, I think someone clicking on “learn” and “documentation” would have similar goals. I’m not sure why they’re separate except that different teams worked on them.
- Hugh Lashbrooke 9:56 pm on August 23, 2022
  
  They’re separate because the content lives in separate places. If you’re suggesting that we should possibly merge the training materials on Learn WordPress with our documentation, then I’m definitely interested in exploring that. I think it makes a lot of sense, but we would need to be very thoughtful and clear about how/why we’re doing it.
- SeReedMedia 10:05 pm on August 24, 2022
  
  They are both education, however they are very different types of content. Documentation is (primarily) code documentation, i.e. the Codex, etc. Learn is tutorials and lesson plans and videos. Very different content that lives in different places.
  
  Worth noting that there is currently a discussion happening in Learn led by @courane01 about merging content types (the discussion does not include Documentation, but perhaps it could/should, for example in terms of a new CPT that links Docs and Learn materials):
  https://make.wordpress.org/training/2022/07/19/proposal-to-merging-lesson-plans-video-tutorials-and-slides/
- Estela Rueda 1:53 pm on August 29, 2022
  
  Users may have the same goal “to learn how to do something” but they also have different ways of learning (a lesson vs an easy-read article). The reason why they are separate is not because they have been worked by different teams but because they fulfill a different step in the user learning process.
  
  Both training and docs teams are talking about how can we link a lesson to a docs article and vice versa as a “learn more” type of link.
  
  But merging them or throwing them together in a bucket would be a disservice to new users and those who consult the site in the rare occasion.
Daniel Schutzsmith 12:45 am on August 23, 2022

From my experience on doing a couple hundred website redesigns for big brands and non profits, I’d suggest looking at two things if you’re rechanging the main nav: where people go, and where you want them to go.

Where people go: do you have analytics and user paths that can help show where traffic is going and how they’re clicking through to get there? Does the project have access to analytics?

Where you want them to go: there’s always a ton of competing needs for a main navigation but what are the overall goals of the project? Is it more installations? Is it more contributors? In what prioritized order would they go in.

Doing a deep dive on those two areas always gets to like 80% of the way on what that main navigation should be. The last 20% is a miss mosh of appeasing influential stakeholders with their preferences.
Daniel Schutzsmith 12:51 am on August 23, 2022

Side note, I’d remove hosting from the main nav if that page is not updated to reflect the industry leaders in managed WordPress Hosting – WPEngine, Pantheon, WordPress VIP, Pagely, Kinsta, Cloudways, etc.
Damon Cook 1:10 am on August 23, 2022

I think @eidolonnight ‘s rendition is the closest for me.

I prefer “Get Involved”, as opposed to “Contributor”.
JuanMa Garrido 9:53 am on August 23, 2022
I agree the Menu bar could be much more intuitive

Here’s my proposal based on some of the ideas thrown in this thread:
- Get WordPress
- Mobile Apps
Discover
- ShowCase
- Plugins
- Themes
- Patterns
- Openverse
- Hosting
Learn
- Documentation
- Courses
- Forums
- WordPress TV
- Developers
Get Involved
- Work Groups
- Five for the Future
The WordPress project
- About
- News
- WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.
A diagram with this proposal can be viewed here
webcommsat AbhaNonStopNewsUK 5:09 pm on August 23, 2022

Thanks @matt for starting this discussion.

A tweaked version of a menu incorporating my suggestions, comments above, and avoiding some abbreviations potentially unfamiliar with audiences – proposal
https://docs.google.com/document/d/1Vpe0LOiPzFdRgegA2Q0bcMQskbDTy6od3ut6T57Vl8Y/edit?usp=sharing

For those who are curious with the suggestions, I have explained more below.

A reduced and clearer direction navigation, such as the combination of @courane01 and @eidolonnight, would be an improvement particularly on mobile and for screen readers reading out the menu options. It would also make it more logical than the current – navigation can tell a story to visitors too and at the moment, this is quite hard to follow.

The five maximum items on the menu they and others have suggested would be clearer, less overwhelming and easier to use and for users to scan and remember. But they may be a little too reduced if the unique content on the site is not easily and quickly found. When working with 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. for navigation menus, we often use the Nielsen research on IA, which can help here in terms of thinking about the goals of the navigation, how effective we can make the text descriptors, and that unique content that users will not find about WordPress on other sites. So increasing the number from four or five to a couple more (keeping well below the current number) may be useful if we can signpost at an early level to unique or most popular content.

A reduced menu and the flexibility of using polyhierarchy in the navigation may be useful to help highlight new areas without having to regularly changing the top level navigation. So for example, adding an aspect of Blocks in more than one top level navigation when needed. It can also help build a sense of familiarity with the site if the top level of headings if they stay constant for a period of time, so I would advocate for a change to be one that is around for a while rather than regularly adding to again at the top level.

I would use ‘Courses’ under a ‘Resources’ or similar heading as well as ‘Learn WordPress’ to assist in key words that users may be looking for in the navigation. This may be more effective when then the materials on Learn WordPress have increased significantly.

The row of highlighted content underneath the main picture could also pick up key areas which are further down in the menu navigation without having to clutter it up at the top-level. It would help not to have duplication between this and the main menu.

Download
I particularly think the word ‘download’ in Nicholas’ version is important to have a clear place for people go to get the software. It is also clearer than ‘Get WordPress’. From work with other software and wider research on encouraging and clear signposts to get software, users tend to look for this word.

I agree ‘extend’ is clear in some settings but like Courtney think it may need an alternative word for a top level navigation and taking into account the needs of polyglots.

For this reason and as a practical and flexible call to action I would suggest ‘Download and Use’. This would incorporate the items underneath in Nicholas’ list too.

About
I warm to Nicholas’ keeping of the ‘About’ in the top level navigation as it helps to immediately signpost what 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/ is focused on and that difference between arriving on this site and WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ or a site about WordPress.

I was unsure where the requirements page would go to and whether this would be a word that would work.

Events
Events will be what many people will come to the site to look for and this may be clearer than ‘Community’. It will also be more likely to attract users who would be more likely to choose to find out more about a WordPress event than click on a link to ‘Community’, which could represent an area or group they are unfamiliar with. In external testing environments, ‘Community’ has sometimes been misunderstood as a log-in or private area.

User-focused navigation
In general, if the menu can be user-journey focused and less team focused, this will also aid the experience and reinforce that WordPress is increasingly working across teams focused on the user.

News
I would advocate for keeping ‘News’ as this is one of the key areas to find what is different or new in WordPress. Though at second level under ‘About’ it would still feel a natural area to check if it could not be in the top level hierarchy.

As ‘News’ is aimed at a wider audience than those already in the community or looking to join it, I would suggest it fits better under ‘About’ than ‘Get involved’.

Learn and Support words
As ‘Learn’ is linked to a branded resource, that is Learn WordPress, just having a reference to ‘Courses’ (which are what the resource has more of at the moment) becoming a sub-head does not have the same reinforcement. However, I am unsure users wanting to learn about WordPress would look for it under a heading named ‘Support’. If this navigation was being set up from scratch, then @juanmaguitar‘s idea of a parent heading of ‘Learn’ would be more intuitive, and support and documentation would sit well under there too.

< Mobile>
This may be a confusing descriptor and ‘mobile apps’ make it clearer what it is for and would fit better under a ‘Download and use’ top level.

The challenge will be for understanding more in-depth how users currently navigate and to check how a change supports that will be access and making sure to respect users’ choices in terms of tracking. incorporating my suggestions, others comments, and avoiding some abbreviations potentially unfamiliar with audiences.
- webcommsat AbhaNonStopNewsUK 5:10 pm on August 23, 2022
  
  Interesting formatting it decided to add not in the preview! The link is https://docs.google.com/document/d/1Vpe0LOiPzFdRgegA2Q0bcMQskbDTy6od3ut6T57Vl8Y/edit?usp=sharing
  - webcommsat AbhaNonStopNewsUK 5:16 pm on August 23, 2022
    
    If anyone has access rights to be able to delete the entire text that has duplicated under the sub head ‘For anyone…’, please feel free to do so. Thanks and apologies for anyone reading it twice. Using 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) tools in the 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/. is not a fun experience!
    - Dion Hulse 2:08 am on August 25, 2022
      
      For documentation purposes; noting that I’ve done this for you @webcommsat , and corrected the incorrect <code> nesting at the start, as you’re right it was easy to miss that it was duplicated.
- Nicholas Garofalo 12:39 pm on August 24, 2022
  
  I was unsure where the requirements page would go to and whether this would be a word that would work.
  
  There are actually a whole bunch of pages semi-hidden under the About page. This is the requirements page: https://wordpress.org/about/requirements/
JuanMa Garrido 6:22 am on August 24, 2022

What would be a good next step to move these proposals forward?
SeReedMedia 9:58 pm on August 24, 2022

Since it’s been proposed, I think we should take this opportunity to surface pages that haven’t been as prominent. For example, the Enterprise page (https://wordpress.org/enterprise/), which is not linked anywhere and no one really know about.

Also, since creating new pages is a different beast altogether, if this is meant to be a quick process (and I’m pretty sure it is!) then I think it makes sense for pages that don’t yet exist (e.g. https://wordpress.org/get-started) to be proposed and developed separately.

IMO the first step needs to be a comprehensive site map of all of the published pages. This list doesn’t include pages on the subdomains (make, learn, etc) and many of the current Nav items link there, so it is incomplete, but nonetheless here is a sitemap with all the pages on the dot-org site: https://wordpress.org/sitemap-1.xml

Incidentally, 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 has discussed this issue and drafted a plan for implementation, first looping in the Marketing team to synthesize these suggestions with the project goals and create a proposal.
Channing Ritter 3:34 pm on August 25, 2022

Hi all, I tried to capture some of these ideas in a couple of new 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/ issues.

Here’s one for discussing changes to the site navigation:
https://github.com/WordPress/wporg-main-2022/issues/104

Here’s one for discussing how to simplify/better integrate the wp-admin bar: https://github.com/WordPress/wporg-main-2022/issues/105

Explorations for both are in this Figma file: https://www.figma.com/file/SQwX90pGxS0XlNTEyNhDRE/WordPress.org-Navigation-Explore?node-id=2%3A1965
- Courtney Robertson 3:28 pm on August 27, 2022
  
  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/ links aren’t working for me. Noting I suggest adding https://make.wordpress.org/handbook under Get Involved.
jominney 1:24 pm on September 9, 2022

There is no ‘get involved’ anymore and no immediate obvious link to the teams? The ‘Community’ link goes to make.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/ but it’s kind of… unexpected?

Also I made 2 attempts to comment here about my thoughts on this, and neither were published 🙁
- Ian Dunn 9:36 pm on September 14, 2022
  
  Hi Jo, sorry about your earlier comments. It looks like they were incorrectly flagged as spam (possibly because of the links). If that happens again, please reach out in #meta and someone can check the queue.
  
  I agree the previous iteration was confusing, I’ve added some new links to hopefully make it more clear.

Welcome to 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!

Contact

Navigation

Welcome to 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!

Contact

Share this: