Title: Uncategorized | Page 3 | WordPress.org Project

---

#  Category Archives: Uncategorized

 [  ](https://profiles.wordpress.org/akirk/) [Alex Kirk](https://profiles.wordpress.org/akirk/)
5:01 pm _on_ November 30, 2023     
Tags: matrix   

# 󠀁[Embracing Matrix for Enhanced Communication](https://make.wordpress.org/project/2023/11/30/embracing-matrix-for-enhanced-communication/)󠁿

As WordPress continues to evolve, so do the tools the community uses to connect,
collaborate, and contribute. The [shift from IRC to Slack in 2014](https://make.wordpress.org/core/2014/10/29/modernising-real-time-communication/)
was an important transition, making SlackSlack Slack is a Collaborative Group Chat
Platform [https://slack.com/](https://slack.com/). The WordPress community has its
own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
one of the primary tools for contributors’ communications and chats. For over a 
year now, in the spirit of the project’s continuous improvement, we (Matrix and 
WordPress contributors) have been [actively exploring Matrix](https://make.wordpress.org/meta/2023/01/25/a-meta-subproject-for-evaluating-matrix/)
as a possible replacement for Slack, providing [regular updates](https://make.wordpress.org/meta/tag/matrix/),
and listening to feedback.

The work done so far represents an effort to bring in a new 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. chat system that meets WordPress’ evolving needs and aligns with
the project and community’s ethos. We need your help to see this next transition
happen.

## Progress and achievements thus far

As a first step in getting the community to test and use Matrix earlier this year,
a Matrix server went live at [community.wordpress.org](https://community.wordpress.org/).
We [enabled a bridge](https://make.wordpress.org/meta/2023/07/20/matrix-chat-summary-july-20-2023/)
that allows you to follow chats and participate from either Matrix or Slack, with
real-time messages showing up.

Since then, Matrix has been used by several Make WordPress teams for discussions
and contributions, including successful meetings with a significant percentage of
participants joining via Matrix. During this phase, insights continued to be gathered
from contributors, and more enhancements were made.

Here’s what’s been achieved as part of the ongoing explorations.

### Better contributor onboarding

A significant amount of time is spent on helping new and casual contributors get
onboarded to Slack. [At the beginning of the year](https://make.wordpress.org/meta/2023/01/25/a-meta-subproject-for-evaluating-matrix/),
we successfully implemented a [Single-Sign-On (SSO) flow](https://wordpress.org/plugins/openid-connect-server/)
to streamline the Matrix login process.

This approach provides a straightforward and convenient onboarding for contributors
compared to Slack for several reasons. First, it allows them easy access to Matrix
chats with their 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/)
credentials, eliminating the need for invitations and going through [several steps](https://make.wordpress.org/chat/)
required to join Slack. Second, it reduces the need to remember and manage multiple
passwords.

### More ways to join Make team chats

Each Make team now has its own Matrix chat page integrated into their respective
Make WordPress blogs. For example, [make.wordpress.org/test/chat/](https://make.wordpress.org/test/chat/).
This method leverages the SSO login experience to access chats. It facilitates a
simpler, direct avenue for contributors to attend meetings, collaborate, or participate
in conversations with other community members—directly within the familiar WordPress.
org interface.

Moreover, Make teams can create dedicated chat pages with different rooms depending
on their needs. This is made possible through [Chatrix](https://wordpress.org/plugins/chatrix/)’
s integration, which allows embedding a Matrix chat as a 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/) 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. into any WordPress
post or page.

### Preserved chat history

All Making WordPress Slack chat history in public channels has been migrated to 
Matrix, ensuring no past conversations are lost. While the search functionality 
is not (yet) as powerful as Slack’s, efforts are ongoing to improve this aspect.

### Room joining

Questions about re-joining or looking for your existing channels (called “rooms”
in Matrix) have been resolved. When joining Matrix, you will automatically be in
all the rooms you were part of in the Making WordPress Slack.

## Additional opportunities

### The open (source) advantage

Matrix provides a secure, decentralized, and real-time communication platform, encouraging
a better collaboration and communication system for WordPress contributors without
relying on a proprietary platform.

As an open source protocol, it aligns closely with the principles of the WordPress
project and supports community-driven development, allowing anyone to contribute
and fostering innovation and improvement. Consequently, this can lead to the development
of new features and enhancements around Matrix and WordPress that benefit the entire
user community and ecosystem.

While the WordPress project provides a homeserver for its community members, Matrix’s
decentralized nature allows individuals to use the homeserver of their choice, empowering
them with control over their communication environment and identity.

### Bringing local communities into a unified platform

Currently, there are different Slack workspaces for local WordPress communities.
Matrix has the potential to bridge this gap and allow these communities to coexist
within a unified platform for better collaboration. By integrating them into Matrix
at the community.wordpress.org server, the project encourages broader participation
and a more connected WordPress community.

### Interoperability and client flexibility

Matrix clients are applications or software that allow you to interact with the 
Matrix communication protocol. We have streamlined joining Matrix [through the browser](https://matrix.wordpress.net/)
or [chat pages](https://make.wordpress.org/chat/matrix/using-a-p2-chat-page/), lowering
the entry barrier by using pre-configured clients. This means that many contributors
won’t need to start a dedicated client.

However, for those who prefer to join from a desktop/mobile app or upgrade their
experience, Matrix supports a diverse variety of clients to choose from, catering
to the different preferences and needs of contributors. These include feature-rich
clients like Element ([recommended](https://make.wordpress.org/chat/matrix/chatting-in-matrix-using-element/)),
FluffyChat (similar to Telegram), and Hydrogen (a minimal Matrix chat client).

## Known challenges

During the testing and exploration phase, we encountered and heard about a few challenges
that may affect your experience. For transparency, the following are some known 
concerns the team is working on or has already reported to the Element client community:

 * **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)**: The Accessibility team tried Matrix and identified
   some barriers to usability in the Element client, [as detailed in this post](https://make.wordpress.org/accessibility/2023/08/07/matrix-test-results/).
   While we’ve [tracked down](https://make.wordpress.org/accessibility/2023/08/07/matrix-test-results/#comment-73234)
   and flagged these areas for improvement with Element, not all have been addressed
   yet. Further community explorations, testing, and feedback about alternative 
   clients will be helpful in identifying opportunities to ensure an inclusive and
   positive experience for all.
 * **Direct Messages (DMs)**: Exporting data from a proprietary platform like Slack
   is difficult because of the lock-in. And, unfortunately, Making WordPress Slack
   private messages cannot be directly transferred to the Matrix chat. As a workaround
   to save your DMs, you can use a browser extension to export them, as explained
   in [this guide](https://make.wordpress.org/chat/matrix/tips-for-transitioning-from-slack-to-matrix/).
 * **Slack-Matrix feature parity:** Common Slack features and integrations are available
   in Matrix, such as channels, direct messages, file sharing, and search. However,
   others don’t have a direct counterpart or work differently, such as notification
   handling or group pings. Matrix presents an opportunity to work on a collaborative
   roadmap and contribute to enhancements that help meet the community’s needs. 
   So, if there are specific features from Slack that you find essential and would
   like to add, please share them.

## What’s next?

Progress so far has been communicated and shared with project leaders Matt and Josepha,
who encourage the community to actively switch to Matrix in replacement of the Making
WordPress Slack by the end of this year.

To be clear, this doesn’t mean Slack will go away overnight. The Slack-Matrix bridge
will remain active until the community has migrated to help ease the transition 
and minimize disruption. All Making WordPress Slack public channels and content 
are accessible through Matrix, where you can follow and participate in existing 
conversations. Toward the end of December, posting to Slack will become more limited,
though the history and chats will still be readable.

We will evaluate progress over the next month and expect to complete the migrationMigration
Moving the code, database and media files for a website site from one server to 
another. Most typically done when changing hosting companies. early next year.

## How you can help

The best way to prepare for the transition is to start using the Matrix chat and
get acquainted with it and its features.

We recommend using the pre-configured instance of the Element Web client by visiting
[matrix.wordpress.net](https://matrix.wordpress.net/) from your browser. However,
as mentioned above, there are more ways to get started. [Please visit this page to learn more](https://make.wordpress.org/chat/matrix/)
and choose your preferred method.

If you’re familiar with Matrix, help support fellow community members in switching.
Another great way to collaborate, especially if you are a Make team repTeam Rep 
A Team Rep is a person who represents the Make WordPress team to the rest of the
project, make sure issues are raised and addressed as needed, and coordinates cross-
team efforts., is to spread the word about the transition within your teams and 
invite them to start running the contributor meetings from Matrix.

### Your input matters

As you or your teams explore Matrix, please share your feedback, questions, and 
suggestions in the `#matrixhelp` room (available from Matrix and Slack) or on [this Matrix GitHub repo](https://github.com/WordPress/Matrix/issues/new/choose).

Your input and engagement are instrumental in shaping the Matrix experience to meet
WordPress’ collaborative needs. Together, we can contribute to making a powerful
communication platform for WordPress and the open source community.

---

We know this move means changing how we chat and collaborate, so it’s natural to
feel a mix of emotions, from excitement to concerns about stepping away from a familiar
tool. Recognizing these feelings, we want to ensure we’re here to support and guide
each other through this transition.

Thank you for your collaboration and continued support as WordPress embraces the
opportunities Matrix brings to the project! Stay tuned for updates as we continue
to work on the migration.

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

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fproject%2F2023%2F11%2F30%2Fembracing-matrix-for-enhanced-communication%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/dansoschin/) [Dan Soschin](https://profiles.wordpress.org/dansoschin/)
6:22 pm _on_ September 15, 2023     
Tags: [q&a ( 3 )](https://make.wordpress.org/project/tag/qa/),
WCUS2023   

# 󠀁[WordCamp US 2023 Q&A](https://make.wordpress.org/project/2023/09/15/wordcamp-us-2023-qa/)󠁿

[WordCamp US 2023](https://us.wordcamp.org/2023/) convened from August 24 to 26 
in Washington, D.C. Nearly 2,000 attendees gathered for two days of engaging sessions,
learning, and community-building. Saturday’s agenda concluded with back-to-back 
keynotes by WordPress co-founder [Matt Mullenweg](https://profiles.wordpress.org/matt/)
and Executive Director [Josepha Haden Chomphosy](https://profiles.wordpress.org/chanthaboune/)
and a subsequent Q&A session. [Read more](https://wordpress.org/news/2023/08/the-future-of-wordpress-whats-next-for-gutenberg/)
about the event and watch recordings of the keynotes.

Watch the recording of the Q&A session from the WCUS keynotes by Matt & Josepha

As with past events, this post collects questions from in-person and online WCUS
attendees that could not be addressed live—with answers from Josepha Haden Chomphosy
and Matt Mullenweg. The community submitted some wonderful questions about all things
WordPress and beyond. Due to the large volume of inquiries submitted, please note
that a compilation of the list’s seven most representative and highly voted questions
has been made. Tune in to the [WordPress Briefing Podcast’s](https://wordpress.org/news/feed/podcast)
future episodes for answers to additional questions and discussion on related topics.

Let’s dig in!

Q. How do we ensure web 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) remains at the forefront of design innovation?

One of the things we learned in the [Accessibility conversation](https://make.wordpress.org/summit/2023/08/22/community-summit-discussion-notes-accessibility-in-the-wordpress-project/)
during the Community Summit is that checklists and blocking requirements (while 
a great starting point) can only do so much. Accessibility requirements are more
nuanced than that and require a fair amount of collective judgment. It was noted
that there needs to be awareness and training of foundational concepts, like defining
DOM order before visual order, defining desired functions before scoping projects,
and generally being more intentional about testing things with users. This all, 
of course, has to happen in concert with contributors throughout the product development
timeline so that what starts with our designers carries on through the development
process as well.

Q. How can we better reach users/audiences unaware of WordPress or who looked at
it five years ago but not recently?

The tactical answer here is that we need a couple of different brand campaigns: 
conquest and re-introduction. But since WordPress has overwhelmingly always relied
on word of mouth marketing, it can be hard to coordinate that sort of effort. What
we would have to do in order to accomplish this would be a grassroots drive for 
testimonials and such, then hope that we can generate a viral pattern in social 
media platforms. 

Q. How can we encourage developers to learn WordPress?

There are a few tactical answers that are always worth pursuing. We should find 
a way to partner with schools (especially at earlier ages) to introduce what WordPress
can do. We should collaborate with organizations that already work directly with
the groups of learners and developers we feel would benefit most from WordPress.
And finally, we should invest in our self-serve learning platforms and event series.

It also might be worth thinking through a shift in our mindset. It’s hard to predict
the future, but we do know that there are skills and values that are useful for 
anyone early in their career. Advanced 21st century skills (esp critical thinking,
cross-cultural communication, and time management) are going to be vital as more
companies and opportunities are distributed, as well as an enterprising spirit to
see and adapt to challenges as they arise; all of which you can learn in the WordPress
project.

Q. As AI gets better with written/spoken language translation, how might that affect
the direction of Multilingual WordPress support?

For starters, I want to be clear that I think applications of AI should always be
guided by the question “how can we streamline or reduce menial tasks for people”
and never by the question “how can we replace this person”. That being said, I think
that any value of AI to multilingual activity in WordPress will primarily be on 
the Polyglot team side. I don’t think we can overstate the importance of having 
both a well-translated CMS and the opportunity for that CMS to natively host well-
translated content as our world gets more connected. I do hope that we are able 
to take full advantage of the potential for shortened workflows in the work of translating
elements inside the WordPress project. Between [Translate Live](https://make.wordpress.org/polyglots/2023/05/08/translate-live-updates-to-the-translation-playground/)
and the opportunity to have human moderation of AI suggested translations, I hope
to make WordPress more available across the world, but especially for locales that
represent at-risk languages and therefore have no GTEs.

Q. How do you envision WordPress integrating with the Fediverse in the Future?

I love the idea of a bespoke, hyper-local social network that can take the place
of group texts or any number of “friends only” implementations in current social
media platforms—just you and your book club friends bloomscrolling through your 
latest gardening experiments!

I also think we have a handful of plugins and solo projects in the ecosystem that,
with a little collaboration, could offer that to WordPress out of the box through
a canonical/community 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..

Q. 1,000 plugins in the queue; is the Plugin Review team still growing?

It is! And if you want to learn more about contributing to the WordPress project
in that way, [you can apply to join us](https://make.wordpress.org/plugins/handbook/apply/)!

Q. What is the biggest opportunity for WordPress in the next decade?

I think the popular answer here is “Artificial Intelligence,” and of course, that
is certainly an opportunity. But I think if we look at “opportunity” in the sense
of “where we can grow the most” I will always say connecting to the communities 
we currently have the least connection to. More connections mean more knowledge 
shared, more skills honed, and more economic opportunities for this world (and web)
that we hope to make into a better place.

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

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

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fproject%2F2023%2F09%2F15%2Fwordcamp-us-2023-qa%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/jpantani/) [Jonathan Pantani](https://profiles.wordpress.org/jpantani/)
9:06 pm _on_ April 19, 2023     
Tags: Showcase   

# 󠀁[Revitalizing the Showcase](https://make.wordpress.org/project/2023/04/19/showcase-content-moderation/)󠁿

## Showcase Content Moderation Efforts

_The Showcase aims to show the world what can be done with WordPress and help demonstrate
the capabilities of WordPress as a publishing platform with a vast array of use 
cases of sites for personal bloggers and small businesses to enterprise companies
and national governments._

With [efforts](https://github.com/WordPress/wporg-mu-plugins/issues/251#issuecomment-1228545353)
made throughout 2022 to highlight the incredible capabilities of the WordPress platform,
solidifying its values and identity, many eyes have been drawn to the opportunity
that it presents. 

WordPress is a brand that many people are unaware of, but interact with daily. Within
the WordPress ecosystem, it’s known for its flexibility, popularity, and freedom
to own one’s content. From personal blogs to enterprise websites, millions of sites
are powered by WordPress. To highlight the power and breadth of the CMS, the project
ought to showcase stunning and unique sites from all across the open web. What better
way for WordPress to become a household name than to share and celebrate some of
those stories? 

The showcase represents the best of what’s possible with WordPress. Infinite possibilities
of what you can create on the platform. Millions of sites could make it. Great, 
right? There are already [some guidelines](https://wordpress.org/showcase/submit-a-wordpress-site/)
in place for submissions. A little more polish through a few updates could have 
added benefits to the collection. There are lessons from the guidelines for [Moderating Photos](https://make.wordpress.org/photos/handbook/moderating-photos/)
that can serve as a beneficial example. First, remember that keeping the guidelines
flexible and short can encourage people to submit. Second, it would be overly prescriptive
to say things ought to be from specific categories or regions. By design, the Showcase
should be diverse in every sense. 

Knowing what’s worked well for the Project in the past, like the [WP Photo Directory](https://wordpress.org/photos/),
while aligning it to WordPress brand values will make the Showcase one of WordPress’s
most valuable marketing and communications assets.

## History

Despite this goal, the existing [WordPress.org Showcase](https://wordpress.org/showcase/)
has faced long-standing technical and moderation hurdles which made it difficult
to keep updated. A variety of discussions about the Showcase’s purpose, design, 
and moderation are cataloged in [Github](https://github.com/WordPress/Marketing-Team/issues/55).

The moderation process is cumbersome, relying heavily on a fragile automation process
that has had issues over the years. Editing has been very manual, and elevated editor
privileges have created bottlenecks over the years. Revisiting the showcase now 
should help alleviate some of the issues. 

The Showcase receives hundreds of new submissions every year, about a third of which
are spam/broken, and many more which do not meet the submission guidelines. Note
too that current submission guidelines are open to a lot of interpretation, thus
making the entire process of moderating Showcase far more complex than it needs 
to be. 

The Showcase is a valuable asset for the WordPress project and re-starting efforts
to keep it current and fresh will surely inspire others of the infinite possibilities
of a WordPress-powered website.

## Coming up

A companion post outlining the proposed guidelines for the WordPress Showcase has
been [posted to the Make Marketing blog](https://make.wordpress.org/marketing/?p=10817).
If you want to weigh in and get more involved in revitalizing the showcase, the 
Make Marketing team looks forward to hearing community voices!

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

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fproject%2F2023%2F04%2F19%2Fshowcase-content-moderation%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/jpantani/) [Jonathan Pantani](https://profiles.wordpress.org/jpantani/)
10:51 pm _on_ April 13, 2023     
Tags: marketing, wp20   

# 󠀁[Building Blocks: The Evolution of WordPress 2013-2023](https://make.wordpress.org/project/2023/04/13/wordpress-at-20-in-print/)󠁿

### Provide feedback via 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/)󠁿 with first-look access to the upcoming WP20 Book.

![](https://i0.wp.com/wp20.wordpress.net/wp-content/uploads/Community.png?w=1600&
ssl=1)

### 20 years — a new milestone

On May 27, 2023, WordPress celebrates a significant milestone in its journey as 
the project reaches its [20th anniversary](https://wp20.wordpress.net/). As part
of the planned activities to mark this achievement, project leadership commissioned
a book last year to document the years since its first commissioned work, [_Milestones – The Story of WordPress_](https://milestonesbook.wordpress.com/)(
2003-2013.)

The next volume, _Building Blocks: The Evolution of WordPress,_ spans the history
of WordPress from 2013-2023 and catalogs its wins, learnings, and everything in 
between. From changes to how users engage with the platform to confronting a worldwide
pandemic, the book reflects on the most impactful moments over the last decade.

As the book gets ready for general release on the anniversary of WordPress, you,
the community, have a role to play in ensuring that the story comes to life.

### How you can help

You’re invited to play the role of editor by reviewing one or all of the 16 chapters.
The book’s chapters are available on [GitHub](https://github.com/WordPress/wp20-book);
each chapter has its own markdown file and is immediately available for download.

As you get started, a very important resource that can prove helpful is The [WordPress Writing Style Guide](https://make.wordpress.org/marketing/handbook/resources/style-guide-and-brand-book/).

Please focus on the content in your review rather than syntax, for instance. Here
are some tips for what helpful feedback will look like providing additional source
materials, including helpful links, offering potential images, spotting potential
grammatical issues or typos, as well as any contextual documentation. Unhelpful 
feedback looks like offering a total rewrite or critique of the writing style.

To log a suggested edit, please create a new GitHub issue (one issue per ticket,
please) and assign it to [jpantani](https://github.com/jpantani), who is assisting
with this project’s wrangling.

### Quick steps to take action

 * Step 1: Familiarize yourself with the [WordPress voice and tone](https://make.wordpress.org/marketing/handbook/resources/style-guide-and-brand-book/)
 * Step 2: Visit and download the [WP20-Book repo](https://github.com/WordPress/wp20-book)
 * Step 3: [Download](https://github.com/WordPress/wp20-book/tree/trunk/Content)
   and review the chapters
 * Step 4: [Log issue](https://github.com/WordPress/wp20-book/issues/new) (one issue
   per ticket) and assign it to [jpantani ](https://github.com/jpantani)
 * _(Optional) Step 5_: Reach out on Making WordPress slackSlack Slack is a Collaborative
   Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community
   has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
   [#marketing](https://make.wordpress.org/project/tag/marketing/) channel and tag
   [@jpantani](https://profiles.wordpress.org/jpantani/)

Please share your feedback by April 30, 2023.

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

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fproject%2F2023%2F04%2F13%2Fwordpress-at-20-in-print%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/)
10:30 pm _on_ January 27, 2023     
Tags: [5ftF ( 13 )](https://make.wordpress.org/project/tag/5ftf/),
[discussion ( 8 )](https://make.wordpress.org/project/tag/discussion/), [Five for the Future ( 13 )](https://make.wordpress.org/project/tag/five-for-the-future/)

# 󠀁[Discussion: Ending the Eternal September](https://make.wordpress.org/project/2023/01/27/discussion-ending-the-eternal-september/)󠁿

As part of our ongoing discussion around [improving the contributor journey](https://make.wordpress.org/project/2023/01/09/request-for-feedback-how-can-we-improve-the-five-for-the-future-contributor-journey/),
I recently asked a few folks their thoughts on [Eternal September](https://en.wikipedia.org/wiki/Eternal_September)
in 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.. More specifically, I wondered:

 1. What makes it difficult for our seasoned contributors to mentor new contributors
    in the open source project?
 2. What happens for existing contributors when we have an influx of new contributors?
 3. Where are the pain points for existing contributors when we bring in new contributors?

## Some Initial Thoughts

There were a lot of interesting responses, but there we a few common threads I heard:

**Lack of Clarity**

It’s hard for existing contributors don’t know a new contributor is in their onboarding,
and therefore also hard to see if they are stuck or what could get them unstuck.

**Lack of Skills**

The primary work for teams is focused, i.e., marketing, coreCore Core is the set
of software required to run WordPress. The Core Development Team builds WordPress.,
etc. Welcoming and teaching new contributors is a different skill set from those
specific focuses. And ever after accounting for that skills gap, there are unspoken
cultural norms to get work looked at and moved forward which takes time and observation
to learn, rather than task-oriented training.

**Lack of Certainty**

No matter whether a new contributor makes a single contribution or returns regularly
over the coming months, the time required to make sure they have their bearings 
is the same. This creates tension among team members/existing contributors—they 
wonder whether they should prioritize existing work (new contributions) or training/
support for new contributors.

## What do you think?

I’d like your thoughts on the questions I posed above, but I’d also like you to 
consider this:

If we believe that speed of feedback on a contribution is key to helping a casual
contributor become a regular contributor, then what would a good first contribution
experience look like for a mentor?

[#5ftf](https://make.wordpress.org/project/tag/5ftf/), [#discussion](https://make.wordpress.org/project/tag/discussion/),
[#five-for-the-future](https://make.wordpress.org/project/tag/five-for-the-future/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fproject%2F2023%2F01%2F27%2Fdiscussion-ending-the-eternal-september%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/)
5:44 pm _on_ January 18, 2023     
Tags: [goals ( 3 )](https://make.wordpress.org/project/tag/goals/),
[planning ( 3 )](https://make.wordpress.org/project/tag/planning/)   

# 󠀁[Big Picture Goals 2023](https://make.wordpress.org/project/2023/01/18/big-picture-goals-2023/)󠁿

To round out the excellent vision-setting done in both the [State of the Word](https://wordpress.com/blog/2022/12/14/state-of-the-word-2022/)
and [Letter to WordPress](https://wordpress.org/news/2023/01/letter-from-wordpress-executive-director-2022/),
here are some goals and projects that we can anticipate in the WordPress project
this year.

### A Quick Caveat

There are always unexpected projects that arise over the course of the year. And
there are big projects to move forward in pieces over the course of multiple years.
This project is too big for me to see everything all the time, and I rely on the
information from team reps and the vision from project leadership to help navigate
any surprises.

If you don’t see a project here, keep in mind that many are still valuable to the
overall success of our work. 

## From 10,000 Feet

There are three pillars that the year’s projects are focused on:

 1. **CMS**: Complete the [Main Tasks for Phase 2](https://github.com/WordPress/gutenberg/issues/33094)
    and begin explorations for Phase 3.
 2. **Community**: [Re-engage our community](https://make.wordpress.org/community/2022/12/09/december-update-global-meetup-reactivation-project/)
    through learning, events, and celebrating our 20th year as a project.
 3. **Ecosystem**: Update distribution methods and mechanisms for extenders and CoreCore
    Core is the set of software required to run WordPress. The Core Development Team
    builds WordPress. itself.

I’ve compiled a preliminary list of individual projects that support one of the 
above goals and are planned for 2023. This list will be updated throughout the year.

**CMS**

 * APIs:
    - All those related to Phase 3 of the 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/) project
    - Fonts APIAPI An API or Application Programming Interface is a software intermediary
      that allows programs to interact with each other and share data in limited,
      clearly defined ways.
    - Interactivity API
    - 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. API
 * Openverse search in Core
 * Navigation block
 * Media management
 * Simplify the release process
 * 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. [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php)
   8.2 compatibility (Core and Gutenberg)
 * Block theme dev tools
    - [Custom CSS](https://href.li/?https://make.wordpress.org/design/2022/11/07/design-share-oct-24-nov-4/)
    - [Custom CSS in Theme Variations](https://href.li/?https://github.com/WordPress/gutenberg/issues/45675)
    - [Template Content Preservation](https://href.li/?https://github.com/WordPress/gutenberg/issues/39324)
    - Starter Content in Block Themes
    - Theme preview

**Community**

 * Community Summit planning and coordination
 * Holistic contributor onboarding
 * Refinement of Polyglot tools
 * ~Maintain learning content speed to ship~ Continue to ship learning content at
   the current pace
 * Update content and refresh design across 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/)
 * Establish contributor and mentor programs
 * Develop a canonical 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. program

**Ecosystem**

 * WordPress Playground
 * Explore improvements to our contributor tools
 * Create a WordPress brand discipline
 * Simplify the release process (also in CMS)
 * Refinement of Polyglot tools (also in Community)
 * Develop a canonical plugin program (also in Community)

### How Can You Help?

I know that our code isn’t the only measure of our success. If you already know 
what type of contribution you’d like to make, you can [check out this list of teams](https://make.wordpress.org/updates/team-reps/)(
with links to their community sites) and team reps. If you’re not yet sure, here
are the areas that each team falls into:

 * Development, Technology, Code: Core/Editor, Mobile, CLICLI Command Line Interface.
   Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress./Tide,
   Security, Performance
 * Design, Product, 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./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.: Design,
   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), Test, Triage
 * Community, Extending WP, Education: Community, Themes, Plugins, Polyglots, Training
 * Contributor Experience: 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., Docs, Hosting, Privacy
 * Communications: Marketing, Support, WPTV

_A Note on Specialized Groups_

A couple of coordinated efforts provide essential support to the progress of multiple
teams.

 * Triage: The triage effort happens across multiple teams and has two purposes.
   One purpose is to ensure tickets are sorted and have all the elements needed 
   for someone to work on them. The second purpose is to determine priority. Not
   everyone has the information to set priority, but anyone can help sort and replicate
   reported bugs!
 * Test: The testing effort also happens across multiple teams and has multiple 
   purposes. One purpose is to validate bugs, bug fixes, and new features before
   they go to users. The second purpose is to bring continuous, high-quality feedback
   throughout the release cycle. A lot of that coordination happens on make.wordpress.
   org/test, but there are also calls to test during various points of the release
   process in the [Core channel](https://wordpress.slack.com/archives/C02RQBWTW).

[#goals](https://make.wordpress.org/project/tag/goals/), [#planning](https://make.wordpress.org/project/tag/planning/)

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

 [  ](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 ( 2 )](https://make.wordpress.org/project/tag/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/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/)
6:55 pm _on_ December 22, 2022     
Tags: covid, journalentry, wordcampasia, wordcampcentral

# 󠀁[Journal Entry: WordCamp Asia 2020 Cancellation Debrief](https://make.wordpress.org/project/2022/12/22/journal-entry-wordcamp-asia-2020-cancellation-debrief/)󠁿

_This is post-action documentation of what happened during the cancellation of 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/). Asia at the start of the pandemic.
There are no necessary action items remaining, this is simply to make the work and
process available publicly should the need ever arise again ~Josepha._

### Timeline – 2020

**Early Jan**:

 * 3 community members reached out to WordCamp CentralWordCamp Central Website for
   all WordCamp activities globally. [https://central.wordcamp.org](https://central.wordcamp.org)
   includes a list of upcoming and past camp with links to each. (WCC) to ask about
   how the coronavirus might impact WordCamp Asia (WCA).

**Jan 21**:

 * First mention of coronavirus among make.wp.org contributors, who were bringing
   concerns from their team members.

**Jan 22**:

 * WCC reached out to the WCA organizing team to discuss whether or not there was
   cause for concern.

**Jan 27**:

 * WCA organizing team publicly announced they were monitoring the situation: https://
   2020.asia.wordcamp.org/2020/01/27/novel-coronavirus-2019-ncov-outbreak-update/

**Jan 29**:

 * WCA team began researching contracts, etc. in case of a late cancellation.
 * Thai Department of Disease Control (DDC) made recommendations for gathering in
   crowded places, but no directives to postpone: https://ddc.moph.go.th/viralpneumonia/
   eng/file/recommendation/06crowded_place.pdf
 * WCC and WCA team collaborated on possible cancellation criteria and landed on
   travel advisory from US or UK to Thailand + travel advisory from any SE Asian
   country to Thailand.

**Jan 30**:

 * Declared a global health emergency by W.H.O.

**Feb 4**:

 * WCA local team member had a call with Thai Department of Disaster Prevention 
   and Mitigation officer.
 * WCA team publicly shared their cancellation criteria, and assurances that planning
   was proceeding as usual: https://2020.asia.wordcamp.org/2020/01/27/novel-coronavirus-
   2019-ncov-outbreak-update/

**Feb 10**:
 WCC received reports about the following:

 * a significant number of sponsors cancelled their travel
 * a significant number of speakers cancelled (due to health concerns or flight 
   cancelations)
 * some companies were not allowing them to attend
 * Some organizers privately shared their concerns about legal consequences if the
   event did happen and people were infected.
 * our contact inside the Ministry of Health assured us that the Thai gov was planning
   an announcement for big events to be postponed.

**Feb 11**:

 * WCC had several meetings with the WCA team discussing all these factors with 
   a focus on having our attendees’ safety as the main priority.
 * There was no unanimous position between WCA and WCA on what to do next.
 * Later that day, the DDC recommended that big events in Thailand be postponed 
   unless absolutely necessary: https://ddc.moph.go.th/viralpneumonia/eng/file/recommendation/
   016Recommendations.pdf

**Feb 12**:

 * WC Asia was officially cancelled.
 * https://2020.asia.wordcamp.org/2020/02/12/cancellation/
 * https://wordpress.org/news/2020/02/wordcamp-asia-cancelled-due-to-covid-19/

### Cancelling the Event

**Action Plan**
 WCC and worked through an 8-hr handoff, global communication plan.
Communicating the change was a lengthy process, due to the desire to maintain [ethical communication patterns](https://josepha.blog/2020/03/27/leadership-basics-ethics-in-communication/).
It was important to let anyone who would have to accomplish the bulk of the work(
or receive a bulk of the feedback) know first, and progressively share the information
from there.

**Inform the organizing team**:

 * The team was spread across several time zones.
 * Naoko delivered the news progressively across all three time zones.

**Inform the public**:

 * Andrea coordinated with the organizing team when and how to communicate the changes
   through their channels.
 * Josepha coordinated with Matt how to communicate the changes 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/](https://wordpress.org/)/news.

**Create supporting materials**:

 * Writing and proofreading posts for each property
 * Letters to request that fees/penalties be waived
 * Emails to attendees, sponsors, etc

**Logistics management**:

 * Canceling/moving dates with the venue
 * Negotiating changes with the hotel
 * Helping connect affected attendees to community initiatives
 * Monitor social media, private SlackSlack Slack is a Collaborative Group Chat 
   Platform [https://slack.com/](https://slack.com/). The WordPress community has
   its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
   instances, and influential bloggers

### Temp Checks and Feedback

Many factors were taken into account while discussing how to move forward. These
were some of the most concerning unknowns that we had:

 * Thai govt gave some inconsistent pointers, such as advice to avoid large gatherings
   but then not preventing them.
 * The unpredictability of quarantines, and other disruptions to travel.
 * Uncertainty of the incubation period, increasing the possibility of unknowingly
   spreading the virus.
 * Attendee-focused decisions were hard because putting the attendee first can be“
   making sure they can attend regardless” or “making sure we don’t put them in 
   harm’s way unnecessarily”.
 * People are worried about how this affects future flagship events.

[#journalentry](https://make.wordpress.org/project/tag/journalentry/), [#covid](https://make.wordpress.org/project/tag/covid/),
[#wordcampasia](https://make.wordpress.org/project/tag/wordcampasia/), [#wordcampcentral](https://make.wordpress.org/project/tag/wordcampcentral/)

 [  ](https://profiles.wordpress.org/angelasjin/) [Angela Jin](https://profiles.wordpress.org/angelasjin/)
3:33 pm _on_ December 21, 2022      

# 󠀁[Announcement: New WordPress Incident Response Team](https://make.wordpress.org/project/2022/12/21/announcement-new-wordpress-incident-response-team/)󠁿

Earlier this year, the WordPress community welcomed a [project-wide code of conduct](https://make.wordpress.org/handbook/community-code-of-conduct/)
and [incident response training](https://learn.wordpress.org/course/incident-response-team-training/).
Part of this was an [announcement and request for nominations](https://make.wordpress.org/updates/2022/05/26/announcement-incident-response-training/)
to a new incident response team (IRT).

As a reminder, the purpose of this team is to help everyone understand where they
can go if they see behavior or actions that don’t match the code of conduct. The
responsibility of the incident response team is not to actively search or monitor
behavior, but to be a resource to the community when things don’t go as expected.

Those nominated to the team have completed the incident response team course as 
part of a cohort, during which they met six separate times to discuss key topics
and practice essential skills through role play exercises. Following the course,
participants reported an increase in confidence for both taking and responding to
incident reports, identified ways to continue building essential skills for incident
response, and offered ideas to strengthen the WordPress incident response team itself.

Let’s welcome the first group of incident responders! 

[@megabyterose](https://profiles.wordpress.org/megabyterose/), [@mysweetcate](https://profiles.wordpress.org/mysweetcate/),
[@evarlese](https://profiles.wordpress.org/evarlese/), [@katiejrichards](https://profiles.wordpress.org/katiejrichards/),
[@kcristiano](https://profiles.wordpress.org/kcristiano/), [@juliarosia](https://profiles.wordpress.org/juliarosia/),
[@devinmaeztri](https://profiles.wordpress.org/devinmaeztri/), [@samsuresh](https://profiles.wordpress.org/samsuresh/),
[@adityakane](https://profiles.wordpress.org/adityakane/), [@harishanker](https://profiles.wordpress.org/harishanker/),
[@nao](https://profiles.wordpress.org/nao/), [@piyopiyofox](https://profiles.wordpress.org/piyopiyofox/),
[@_dorsvenabili](https://profiles.wordpress.org/_dorsvenabili/), [@peiraisotta](https://profiles.wordpress.org/peiraisotta/),
[@sippis](https://profiles.wordpress.org/sippis/), and [@angelasjin](https://profiles.wordpress.org/angelasjin/)

Two new SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
channels have been created as a next step: a public channel (`#incident-response`)
for anyone to ask public questions of the Incident Response team, and a private 
channel where IRT members can collaborate on confidential situations. This team 
is new, so practices will be iterated on as transparently as possible. However, 
for the safety of community members, incident response needs to be treated confidentially
wherever possible. Anonymized, annual reports ([similar to what the Community team has done in the past](https://make.wordpress.org/community/2020/03/10/2019-incident-reports-details-and-results/))
will be published.

## How can this team help you?

If you see something that doesn’t align with the [project wide](https://make.wordpress.org/handbook/community-code-of-conduct/)
or [events code of conduct](https://make.wordpress.org/community/handbook/wordcamp-organizer/planning-details/code-of-conduct/),
please feel free to reach out to any of the IRT members. To submit an incident report,
please email [reports@wordpress.org](https://make.wordpress.org/project/category/uncategorized/page/3/reports@wordpress.org?output_format=md).
You can also reach out with general questions, including ones around how incident
response works in WordPress!

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fproject%2F2022%2F12%2F21%2Fannouncement-new-wordpress-incident-response-team%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 ( 2 )](https://make.wordpress.org/project/tag/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)

# Post navigation

[← Older posts](https://make.wordpress.org/project/category/uncategorized/page/4/?output_format=md)

[Newer posts →](https://make.wordpress.org/project/category/uncategorized/page/2/?output_format=md)