Title: WordPress – WordPress.org Project

---

#  Tag Archives: WordPress

 [  ](https://profiles.wordpress.org/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/)
6:43 pm _on_ January 13, 2023     
Tags: [q&a ( 3 )](https://make.wordpress.org/project/tag/qa/),
[wcus2022 ( 2 )](https://make.wordpress.org/project/tag/wcus2022/), WordPress   

# 󠀁[2022 State of the Word Q&A](https://make.wordpress.org/project/2023/01/13/sotw22qa/)󠁿

State of the WordState of the Word This is the annual report given by Matt Mullenweg,
founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing,
and the future of WordPress. [https://wordpress.tv/tag/state-of-the-word/](https://wordpress.tv/tag/state-of-the-word/).
2022 was held in New York City on December 15, 2022. It was a welcome feeling to
gather together again in person for this annual and anticipated event. After a keynote
address that looked at the year’s successes and a peek at what’s to come in the 
year ahead, the WordPress project’s co-founder [@matt](https://profiles.wordpress.org/matt/)
engaged in a warm and insightful question and answer session with the in-person 
attendees.

State of the Word 2022

As with events past, this post will list the questions from WordPress users and 
contributors that could not be answered live. 

> Q1. “Own your content” has long been a rallying cry of WordPress. How does this
> fit with Tumblr’s model of a centralized content server? 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/](https://wordpress.com/) allows me to own my content
> because I can export it to an independent instance. Will we see a standalone Tumblr,
> like WordPress?

A1. Think of both of them as having different frontends but the same great coreCore
Core is the set of software required to run WordPress. The Core Development Team
builds WordPress. (WordPress) on the backend. Tumblr is a SaaS service and, from
the standpoint of owning your content, quite a bit of work has gone into data portability.
It’s true that Tumblr’s not quite yet open sourceOpen Source Open Source denotes
software for which the original source code is made freely available and may be 
redistributed and modified. Open Source **must be** delivered via a licensing model,
see GPL. yet, but a lot of work is planned to unify APIs, support RSS, and generally
make it more open overall.
In a recent [Hallway Chats podcast](https://hallwaychats.com/episodes/episode-161-a-chat-with-matt-mullenweg/)(
beginning at 29:07) with Topher DeRosia and Nyasha Green, Matt offered the following
analogy:

> “My hope is that basically Tumblr and wordpress.com, they’ll be essentially like
> two different restaurants that share the same kitchen. You have a different vibe,
> different dishes, different experience, different kind of front-end experience,
> but on the back end, the same great ingredients, the same attention to detail,
> same infrastructure, same sort of stuff that makes it excellent. Food is actually
> a good analogy.” 
> Matt Mullenweg; January 6, 2023

> Q2. Will WordPress be a thing after the entire focus is moved to 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/](https://wordpress.org/gutenberg/)?

A2. WordPress is here to stay. The purpose of the Gutenberg project is to evolve
WordPress and its capabilities. The Gutenberg 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. itself is a tool for early testing
and stabilization of features that will land in and improve WordPress Core, but 
will not replace it. Matt [addresses](https://youtu.be/s52wGjNfRko?t=1323) this 
further during the State of the Word.

> Q3. Are we doing enough for the open-source Contributors and what more can we 
> do to recognize or give back to the community to grow the number of Contributors?

A3. It’s hard to define what “enough” is when it comes to supporting open source
contributors. Everyone is invited to celebrate the work done within the project,
and a simple way to do so is to recognize folks in the [Making WordPress Slack](https://make.wordpress.org/chat/)
[#props channel](https://wordpress.slack.com/archives/C0FRG66LR). There is always
room for improvement, though. If you’ve got thoughts about how we can do that, we’d
love to hear them! [Join the discussion](https://make.wordpress.org/project/2023/01/09/request-for-feedback-how-can-we-improve-the-five-for-the-future-contributor-journey/)
on how to improve the contributor experience. 

> Q4. Can we perhaps have a second Q&A event with Matt each year to allow for more
> active feedback and comments from the community in person?

A4. Several other Q&A opportunities with Matt occur throughout the year at most 
flagship 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](https://central.wordcamp.org/about/). events in Asia,
Europe, and the Americas. This year the Community Summit will resume, which is also
another great opportunity for contributors to exchange feedback and ideas in person.
[Submit your topic](https://make.wordpress.org/community/2022/12/08/suggest-topics-for-the-2023-wordpress-community-summit/)
by January 16.

> Q5. Why is polylingual functionality in Core less important than collaboration?
> More than 50% of WordPress installs are not in English.

A5. WordPress is committed to making itself available in as many languages as possible.
As part of that commitment, Multilingual is on the roadmap for Phase 4 and set to
commence immediately after Phase 3: Collaboration and Workflows, which begins this
year.

From a technical point of view, making WordPress natively multilingual is quite 
challenging. Adding collaboration tools in advance will help support Phase 4 technical’s
implementation and provide tools to manage multilingual content out of the box, 
like translation and review workflows. So Phase 3 will not just “inform” Phase 4
but will actually create the infrastructure and features central to making Phase
4 possible.

Listen to Matt’s full response [here](https://youtu.be/7x74kWqWMDY?t=1247).

> Q6. Can Media Library finally get a refresh? We need to be able to organize the
> images in there. 

A6. Yes! Revamping the Media Library and providing better management, discovery,
and collaboration tools for media content are on the roadmap for Gutenberg’s Phase
3.

> Q7. Are you concerned about the implications of AI image generation being built
> on top of the copywritten work of artists without their knowledge or consent?

A7. The WordPress open source project supports a free and open web; as long as AI
image generation supports initiatives that abide by CC licensing requirements, then
AI image generation can be a good thing that helps augment natural human creativity.
Listen to Matt’s thoughts on the subject in [the Q&A session](https://youtu.be/s52wGjNfRko?t=1735).

> ​Q8. Will there be preferred browsers for playground dev?

A8. Currently, WordPress Playground works across all browsers apart from Edge. To
learn more and to start using the tool, please visit: ​​[https://developer.wordpress.org/playground/](https://developer.wordpress.org/playground/)

> Q9. WordPress introduced and pushed “post formats” with the 2014 theme. Regarding
> the development in the Twitterverse, what are your thoughts on the post format
> asides? And what do you think of post formats in 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. editor world?

A9. Currently, post formats are in a stable state; they are still supported and 
usable, but there are no real plans to foster adoption or add additional functionality
around them. There are no plans to focus on them during the remaining phases of 
the Gutenberg project, but if there were a group of motivated contributors who wanted
to spend some time on post formats, we would welcome those contributions!

> Q10. 2022 shows some progress in the design of mobile features in WordPress: fluid
> typography, fluid spacing, gaps, etc. However, there are some missing functions:
> is there some plan to add responsive block order, show/hide, and more features
> for responsive menus? We work with some African companies and their customers 
> are almost all on mobile (80%). So for them, mobile-first is the rule.

A10. Continued improvement of the mobile experience is absolutely on our collective
minds for 2023. There is an active discussion about the limitations of breakpoints
vs the opportunities represented by intrinsic web design principles. You can follow
and participate in that topic [on GitHub](https://github.com/WordPress/gutenberg/issues/34641).

> Q11. Does the project have any plans for future updates to the full administrator
> 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., i.e.“
> the dashboard,” as it appears dated particularly when compared to other website
> builders? 
>  _Several State of the Word attendees asked about the modernization of the dashboard
> and its 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./UI. This question
> has been modified to reflect that._

A11. Revamping the administration interface (which many of us refer to as “wp-admin”
or “the dashbaord”) is included in plans for Phase 3 as it is arguably intrinsic
to better collaboration. So far the features being explored are new content management
screens (for blocks, styles, fonts, etc.), new admin tools like a global search,
and a refresh of notifications.

> Q12. What is the word on the need for child themes when customizing block themes?

A12. Block themes are much simpler to customize than classic themes, so while the
creation of child themes is supported by block themes, it’s often not needed. Child
themes are still valuable, though, when seeking to extend themes from other developers
or Core.

> Q13. What is the state of the traditional theme?

A13. While the future belongs to block themes, many modern WordPress features are
supported by classic themes to help smooth the transition and upgrade path. For 
example, WordPress 6.1 allows block template parts in classic themes.

> Q14. Is the style guide also visible for non-block themes?

A14. There isn’t a guide currently because Styles aren’t available for non-block
themes. You can learn more and discuss on this [GitHub issue](https://github.com/WordPress/gutenberg/issues/41119).

> Q15. Will the plugin directory for developers always use 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/.? Or are there
> any plans to go full git?

A15. There are no plans to move toward git at this time. There are ongoing discussions
on how to support more integrations with 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/)
or GitLab that you can learn more about [here](https://meta.trac.wordpress.org/ticket/6087).

> Q16. Years ago, it was much easier to grow a plugin for WordPress and make an 
> impact. What can plugin devs do outside of Freemium/Premium/Paid Add-On models?
> Donors/sponsors are difficult to find

A16. Plugins are quite similar to consumer products, and finding the right product-
market fit and building it to ensure the highest quality are key factors in terms
of finding success for a plugin. Careful market landscape research and quality checks
will help plugin devs evaluate whether their efforts find the right fit with users.

> Q17. Will Canonical Plugins get a blue checkmark?

A17. There isn’t yet a specific plan for how canonical plugins will be displayed
on the plugin directory, but this is a wonderful suggestion for [Make Design](https://make.wordpress.org/design/).

> Q18. Regarding backend UX/UI, can consideration be given to a standard way of 
> grouping/organizing plugins in the menu? Multiple plugins that insert a link into
> the menu can make it cluttered.

A18. Though this part of very future forward work, this topic is currently being
explored [in this post](https://make.wordpress.org/design/2022/06/13/thinking-through-the-wordpress-admin-experience/)
under the section “Make it extensibleExtensible This is the ability to add additional
functionality to the code. Plugins extend the WordPress core software..” 

> Q19. How is WordPress addressing the incessant notifications in the WP dashboard–
> will there be a Notifications ban in the dashboard and the set up of a Notifications
> Central point? If not, why not?

A19. The [feature notifications project](https://make.wordpress.org/core/2019/08/05/feature-project-proposal-wp-notify/)
work is ongoing, and there is renewed interest in getting the MVPMinimum Viable 
Product "A minimum viable product (MVP) is a product with just enough features to
satisfy early customers, and to provide feedback for future product development."-
[WikiPedia](https://en.wikipedia.org/wiki/Minimum_viable_product) completed this
year. Some new contributors have been joining the conversations, and anyone interested
in this feature can join the [#feature-notifications channel in the Make WordPress Slack](https://wordpress.slack.com/archives/C2K1C71FE).

> Q20. The notification interface, is it also for promo and banners?

A20. As recommended in the [Plugin Developer Guidelines](https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#11-plugins-should-not-hijack-the-admin-dashboard),
the WordPress notification interface is not intended to be used for advertisements
or promotions.

> Q21. How will Collaboration will be developed: as a Gutenberg plugin or WP Core
> integration? And when 6.2 or 6.4?

A21. Collaborative Workflows will be developed within the Gutenberg plugin. While
it’s too soon to tell when and what collaboration tools will land in WordPress core,
using the Gutenberg plugin allows for early access to all these features as soon
as they are available

> Q22. When was the last time someone actually used “Post via email” in the settings
> area?! (followed up with: more along the lines is why is it still in core? I get
> users totally confused by it all the time as they think it’s email settings, etc..)

A22. That is still in use! The feature was originally [created](https://wordpress.com/blog/2009/05/12/post-by-email/)
as a parity tool for Posterous and has remained in Core. A helpful guide for support
is located [here](https://wordpress.org/support/topic/troubleshooting-the-basic-post-via-email-feature/).

> Q23. What about the third-party Site Builders, are they a thing of the past?

A23. The Block Editor provides numerous APIs for third-party site builders, which
they are encouraged to use to leverage the benefits of storing content in block 
format.

> Q24. Will ActivityPub support be added to WordPress and will Mastodon publishing
> be added to Jetpack?

A24. Yes, the ActivityPub plugin is up for review as a canonical plugin later this
year, and Mastodon publishing is also due to be added.

> Q25. How does WP support the GDPR, privacy, e.g. relating to territorial disputes
> regarding privacy issues between the EU and the US and increased cyber threats?

A25. Many of these issues relate to how and where each individual site is operated,
so it is difficult to find and apply a global solution in WordPress Core. Solutions
are best found in the various plugins and integrations available.

> Q26. Not sure if this is the right platform, but the removal of “Active Installs”
> raised a few questions. Maybe shed some light on the idea behind that.

A26. Others have raised this topic recently, which has been deeply discussed on 
[this Trac ticket](https://meta.trac.wordpress.org/ticket/6511).

> Q27. I’m wondering about the custom post types/custom fields.. are we going to
> see them baked in Core soon?

A27. These are currently supported in core programmatically, and there are currently
no plans to expose a UI in the dashboard for the management/creation of these. There
are existing plugins that fill this need if required.

> Q28. Is there any plan or conversation about integrating Composer into WordPress
> for sites to manage their dependencies (plugins, themes, custom libraries, Core)
> via code?

A28. Within the WordPress community, composer holds different definitions for different
groups. For example, there’s a non-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/)
packager that many WordPress-via-composers use, like [https://wpackagist.org/](https://wpackagist.org/).
The work on the Plugin Dependency feature is ongoing too. Read more about the recent
work on [this Trac ticket](https://core.trac.wordpress.org/ticket/22316) or [this call for testing plugin dependencies](https://make.wordpress.org/core/2022/10/12/call-for-testing-plugin-dependencies/).

_Enormous thanks to [@akirk](https://profiles.wordpress.org/akirk/), [@zieladam](https://profiles.wordpress.org/zieladam/),
[@annezazu](https://profiles.wordpress.org/annezazu/), [@bengreeley](https://profiles.wordpress.org/bengreeley/),
[@cbringmann](https://profiles.wordpress.org/cbringmann/), [@dd32](https://profiles.wordpress.org/dd32/),
[@harishanker](https://profiles.wordpress.org/harishanker/), [@priethor](https://profiles.wordpress.org/priethor/),
[@psykro](https://profiles.wordpress.org/psykro/),[ @jpantani](https://profiles.wordpress.org/jpantani/),
[@mcsf](https://profiles.wordpress.org/mcsf/), [@eidolonnight](https://profiles.wordpress.org/eidolonnight/),
[@rmartinezduque](https://profiles.wordpress.org/rmartinezduque/) for their help
in researching, answering, and editing this post._

[#qa](https://make.wordpress.org/project/tag/qa/), [#wcus2022](https://make.wordpress.org/project/tag/wcus2022/),
[#wordpress](https://make.wordpress.org/project/tag/wordpress/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fproject%2F2023%2F01%2F13%2Fsotw22qa%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/cbringmann/) [Chloe Bringmann](https://profiles.wordpress.org/cbringmann/)
3:33 pm _on_ September 19, 2022     
Tags: WCUS, [wcus2022 ( 2 )](https://make.wordpress.org/project/tag/wcus2022/),
WordPress   

# 󠀁[WCUS 2022 Q&A](https://make.wordpress.org/project/2022/09/19/wcus-2022-qa/)󠁿

[WordCamp US 2022](https://us.wordcamp.org/2022/) convened from September 9 to 11
in San Diego, California. It felt reminiscent of earlier gatherings that offered
a comfortable environment for reconnecting, learning, and discussing all things 
WordPress. The highlight for many was the closing session with the project’s co-
founder, [@matt](https://profiles.wordpress.org/matt/), who shared a sneak peek 
at features slated for the upcoming 6.1 release and engaged in conversation with
attendees in a Town Hall Q&A.

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](https://central.wordcamp.org/about/). US 2022 Q&A

In an effort for no questions to go unanswered, those submitted on Livestream and
Twitter are listed below with answers from WordPress contributors. 

> Q1. How do we convince legacy web builders, agencies, and companies to more quickly
> adopt new WordPress features? I’m seeing a ton of opportunities to support older
> sites (5.0), but very few agencies/projects/companies are moving to build on 6.0.

A1. A few teams are working hard to share and educate users about new features in
the latest WordPress releases. The [Training Team](https://make.wordpress.org/training/)
publishes [tutorials](https://learn.wordpress.org/tutorials/) to help ease adoption.
[Marketing](https://make.wordpress.org/marketing/) highlights new [#WordPress](https://make.wordpress.org/project/tag/wordpress/)
features across multiple social networks. [@annezazu](https://profiles.wordpress.org/annezazu/)
hosts regular [Hallway Hangouts in Test](https://make.wordpress.org/test/tag/fse-hallway-hangout/).
Your thoughts on additional adoption initiatives are welcome.

> Q2. How close is WordPress to editor collaboration? It’s sometimes frustrating
> that two people can’t be in the editor at the same time. 

A2. The [project roadmap](https://wordpress.org/about/roadmap/) shows the big picture
goals and upcoming releases, and [@matveb](https://profiles.wordpress.org/matveb/)
shared some [early thoughts about building a “multiplayer” experience](https://make.wordpress.org/design/2022/06/13/thinking-through-the-wordpress-admin-experience/),
but there is no release date for this feature yet. As noted in the Q&A, some big
questions need to be addressed before collaboration can be addressed. That said,
some exciting plugins explore comments and other collaborative tools.

> Q3. Any thoughts on p2’s release date for self-hosting? It looks lovely!

A3. The [new version of P2](https://wordpress.com/p2/) requires 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/](https://wordpress.com/) hosting to power its more
advanced feature set, so there is currently no self-hosted version available. You’re
welcome to try the [O2 plugin](https://github.com/Automattic/o2) and the [P2 Breathe theme](https://wpcom-themes.svn.automattic.com/p2-breathe/),
but please note that this 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. is [not in active development](https://wordpress.org/support/topic/p2-self-hosted-sites/).

> Q4. What commitment does WordPress CoreCore Core is the set of software required
> to run WordPress. The Core Development Team builds WordPress. have to advance 
> 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)
> for disabled WP users and also for baking it into WordPress sites created?

A4. Accessibility is top of mind while developing WordPress, and WordPress 6.1 has
seen 40 accessibility improvements [listed under milestones 13.1-14.1 in the ](https://github.com/WordPress/gutenberg/issues?page=1&q=is%3Amerged+label%3A%22Accessibility+%28a11y%29%22)
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/](https://wordpress.org/gutenberg/)
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, if you would like to follow along, with more expected in upcoming releases.
As Matt mentioned in the Q&A session, there is an interest in slowing down the fast
clip of Gutenberg development to allow for necessary improvements, like accessibility.

> Q5. What is the plan for making the Site Editor accessible?

A5. Every new release includes a variety of accessibility improvements. You can 
read about [WordPress 6.0 Accessibility Improvements](https://make.wordpress.org/core/2022/04/20/wordpress-6-0-accessibility-improvements/)
and expect more in 6.1. You can also get involved with this work by joining the 
[#accessibility](https://wordpress.slack.com/archives/C02RP4X03) channel in [Make Slack](https://make.wordpress.org/chat/).

> Q6. Are there any plans to make future WordCamps hybrid to take advantage of the
> aspects of video conferencing that we discovered during the pandemic?

A6. WordCamp US 2022 had a captioned [Livestream available throughout the event](https://us.wordcamp.org/2022/livestream/)(
recordings also available). Community members in San Diego and at home kept the 
conversation going with [#WCUS](https://make.wordpress.org/project/tag/wcus/) across
social platforms, especially on [Twitter](https://twitter.com/hashtag/WCUS). WordCamp
organizers are committed to iterating and exploring how best to bring the experience
to participants both in-person and online.

> Q7. What is the timeline for removing the “BetaBeta A pre-release of software 
> that is given out to a large group of users to trial under real conditions. Beta
> versions have gone through alpha testing in-house and are generally fairly close
> in look, feel and function to the final product; however, design changes often
> occur as part of the process.” tag from the Site Editor?

A7. The [Core Team](https://make.wordpress.org/core/) is discussing open issues 
and blockers to the removal of the Beta label. You can follow along with the discussion
on [GitHub](https://github.com/WordPress/gutenberg/issues/39293).

> Q8. Right now, the navigation 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. is basic. Are they planning to improve this?
> For example, I would like to easily create a mega menu.

A8. Navigation is a crucial part of the site editing experience and can cover a 
wide array of use cases, from simple “all pages” navigation to complex structures.
Currently, the project is focused on ensuring the best experience possible for the
most common use cases while still allowing extensibility. Once that experience is
polished enough, the editor will be extended to allow more complex navigation structures
such as mega menus.

Do you have a question? Comment below, and join one of the many [teams making WordPress](https://make.wordpress.org/)
for answers.

[#wcus2022](https://make.wordpress.org/project/tag/wcus2022/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fproject%2F2022%2F09%2F19%2Fwcus-2022-qa%2F%23respond&locale=en_US)