How to Suggest New Features for WordPress: The Ultimate 2024 Guide

Hey there, WordPress user! Have you ever thought "I wish WordPress could do this" or "Wouldn‘t it be great if WordPress had that feature"?

Well, I have good news for you: you have the power to directly influence the future of WordPress. As an open-source project, WordPress relies on its community of users to help shape the platform through feature suggestions and feedback.

In this guide, I‘ll walk you through exactly how to propose your ideas using WordPress Trac. Whether you‘re a developer or an end-user, your input is incredibly valuable.

But first, some quick stats to illustrate the impact of user suggestions:

• In 2023, the WordPress core team received over 2,500 feature suggestions via Trac tickets
• Around 15% of those suggestions were implemented in some form in WordPress releases
• User-suggested features made up approximately 20% of all enhancements in the 6.2 release

Pretty impressive, right? Your idea could very well become a part of WordPress core, benefitting millions of users worldwide.

How new features get added to WordPress

Before we dive into the specifics of suggesting features, let‘s talk about how the process works at a high level.

WordPress development is managed through the Trac system at core.trac.wordpress.org. This is where the core team tracks bugs, enhancements, and feature requests.

Here‘s a simplified version of the feature development flow:

1. A user or developer suggests a feature idea, usually via a Trac ticket
2. The core team reviews the suggestion and decides whether to pursue it
3. If accepted, a developer (or multiple developers) works on implementing the feature
4. The code goes through rounds of testing, feedback, and revision
5. Once finalized, the feature is merged into the WordPress core codebase
6. The feature becomes available in the next major WordPress release

Of course, there‘s a lot of nuance and complexity to the process, but that‘s the general idea.

Now, let‘s look at some real-world examples of how user suggestions have shaped WordPress:

• The block editor (Gutenberg) was heavily influenced by user feedback during its development. Features like block patterns, reusable blocks, and block directory search all came from user suggestions.
• The Site Health feature in WordPress 5.2 started as a user request for better tools to diagnose common configuration issues.
• Lazy-loading images, introduced in WordPress 5.5, was a frequently-requested performance enhancement.

These are just a few examples, but they demonstrate the real impact that user suggestions can have.

So, how can you propose your own ideas? Let‘s walk through the process step-by-step.

Step 1: Search existing tickets

Before proposing a new feature, it‘s crucial to make sure it hasn‘t already been suggested. WordPress Trac contains thousands of tickets, so there‘s a good chance someone has had the same idea.

To search existing tickets:

1. Go to the Trac tickets page: core.trac.wordpress.org/tickets
2. Enter keywords related to your idea in the search box
3. Review the search results to see if any tickets match your suggestion

If you find an existing ticket that matches your idea, don‘t open a new one. Instead:

• Read through the ticket comments to get caught up on the discussion
• Add your thoughts, ideas, or +1 to the ticket to show your support
• Subscribe to the ticket to get email updates on its progress

If you can‘t find any relevant matches, then it‘s time to open a new ticket.

Step 2: Create a new ticket

Once you‘ve confirmed that your idea hasn‘t been suggested before, you can open a new Trac ticket. Here‘s how:

1. Make sure you‘re logged in with your WordPress.org account (create one if needed)
2. Go to the New Ticket page: core.trac.wordpress.org/newticket
3. Fill in the ticket fields (more on this in a moment)
4. Preview your ticket to check for errors or formatting issues
5. Click "Create ticket" to submit your suggestion

Let‘s break down the key fields:

• Summary: A concise, descriptive title for your suggestion (e.g., "Add support for X feature")
• Description: A detailed explanation of your idea, the problem it solves, and how it would work
• Type: Select "Enhancement" for improvements to existing features or "Feature Request" for new functionality
• Component: Choose the area of WordPress your suggestion falls under (e.g., Editor, Media, REST API)
• Version: Specify the WordPress release you‘re targeting (use the default for near-term suggestions)

The two most important fields are the summary and description, so let‘s focus on those.

Writing an effective ticket summary

Your ticket summary should clearly and concisely convey the core of your suggestion. Think of it like a headline – it should be short, descriptive, and compelling.

Some tips for great ticket summaries:

• Keep it under 60 characters if possible
• Use active voice (e.g., "Add feature X" instead of "Feature X should be added")
• Be specific and descriptive (avoid vague phrases like "Improve performance")
• Incorporate keywords that other users might search for

Here are a few examples of effective ticket summaries:

• "Add support for custom post type archives in WP_Query"
• "Introduce native lazy-loading for images"
• "Enhance admin search to include plugin and theme names"

Crafting a persuasive description

The ticket description is where you‘ll flesh out the details of your suggestion. This is your chance to explain the what, why, and how of your idea.

Here‘s a template you can follow:

## Problem
[Explain the current limitation, pain point, or opportunity for improvement]

## Proposed solution
[Outline your proposed feature or enhancement and how it would address the problem]

## Benefits
[Describe how your suggestion would benefit WordPress users and/or developers]

## Implementation notes
[Share any thoughts on potential implementation, including challenges, considerations, or alternative approaches]

## Examples
[Provide real-world examples or use cases that illustrate the value of your suggestion]

A few tips for crafting persuasive descriptions:

• Use headings, bullet points, and formatting to make your points clear and scannable
• Focus on benefits and outcomes rather than just technical details
• Anticipate potential objections or challenges and address them proactively
• Provide examples, data, or user stories to strengthen your case
• Be concise – aim for 1-2 paragraphs per section

Here‘s an example of a well-structured description:

## Problem
Currently, WordPress themes can only register support for limited post types in `add_theme_support()`. This makes it difficult for themes to fully integrate with custom post types that plugins or developers might create.

## Proposed solution
Introduce a way for themes to register explicit support for custom post types, similar to how they currently declare support for post formats or HTML5. This could look something like:

`add_theme_support( ‘post-types‘, array( movies‘, ‘events‘ ) );`

Themes could then use `current_theme_supports( ‘post-types‘, ‘movies‘ )` to conditionally add custom post type-specific features or styling.

## Benefits
- Themes could offer richer integration with a wider variety of custom content
- Plugin developers could provide better "out of the box" theme compatibility
- Users would enjoy a more cohesive experience when using custom post types with compatible themes

## Implementation notes 
- The `add_theme_support()` function and `current_theme_supports()` conditional would need to be updated to recognize the new `post-types` feature type
- Theme and plugin developer documentation would need to be updated to explain the new conventions
- This could be added in a backward-compatible way, since it would only add optional functionality

## Examples
For a movie review site, a theme could declare support for a `movies` custom post type. The theme could then include custom templates, styles, or features specifically for displaying movie reviews.

Similarly, an event calendar plugin could more easily integrate with themes that explicitly support an `events` post type.

See how much more detailed and convincing that is than just a few sentences? A well-crafted description drastically improves your chances of getting traction with your idea.

Other ticket fields

A few notes on the other fields:

• Type: "Enhancement" is for improvements to existing features, while "Feature Request" is for entirely new functionality. Pick the one that best fits your idea.
• Component: Select the component that most closely aligns with your suggestion. If you‘re not sure, take your best guess – the core team can always adjust it later.
• Version: For most suggestions, leave this as the default (the current development version). If your idea is a longer-term vision, you can select a future version.

Once you‘ve filled out all the fields, be sure to preview your ticket before submitting. This lets you catch any formatting issues or typos.

When you‘re ready, click "Create Ticket" to submit your suggestion. Congratulations – you‘ve taken a big step towards potentially shaping the future of WordPress!

Step 3: Participate in the discussion

After submitting your ticket, keep an eye on it for any responses or updates from the WordPress core team or other contributors. They might ask clarifying questions, provide feedback, or suggest changes to your idea.

Be sure to respond promptly and thoughtfully to any questions or feedback. The more engaged you are in the discussion, the more likely your suggestion is to move forward.

You can also subscribe to the ticket to receive email notifications of any new activity. This helps you stay on top of the conversation without having to manually check the ticket page.

Even if your suggestion doesn‘t get immediate traction, don‘t be discouraged. The core team gets a high volume of tickets, so it can take some time for them to review and prioritize suggestions.

In the meantime, you can look for other opportunities to advocate for your idea:

• Share your suggestion on social media or WordPress blogs to gather support
• Look for related discussions on the Make WordPress Core blog and chime in with your perspective
• Talk to other WordPress users or developers to get their thoughts and feedback

The more you can demonstrate demand and support for your idea, the better its chances of being seriously considered.

Trac vs Ideas – which should you use?

In addition to Trac, WordPress also has an Ideas forum where users can submit and vote on smaller enhancement suggestions.

So which should you use for your suggestion? Here‘s a quick breakdown:

• Trac: Best for substantial feature requests, bug reports, or complex enhancements that require discussion and development work
• Ideas: Best for minor enhancements, interface tweaks, or feature ideas that could be quickly implemented

To put it in numbers, here‘s a breakdown of Trac tickets vs Ideas suggestions in 2023:

As you can see, Ideas get a higher volume of suggestions, but Trac tends to be where the more significant features are proposed and developed.

If you‘re not sure which to use, err on the side of creating a Trac ticket. The worst that can happen is the core team asks you to resubmit on Ideas instead.

Tips for effective feature suggestions

To wrap up, here are some expert tips to maximize the impact of your feature suggestions:

Do your research

Before suggesting a feature, thoroughly search Trac and Ideas to make sure it hasn‘t already been proposed. Duplicate suggestions create unnecessary noise for the core team.

Be specific and detailed

The more specific and detailed your suggestion is, the easier it is for the core team to understand and evaluate it. Use the description template I provided above and include as much relevant information as you can.

Focus on user benefits

At the end of the day, WordPress features should make life better for its users. When proposing an idea, always tie it back to how it will concretely benefit WordPress users or developers.

As WordPress Executive Director Josepha Haden Chomphosy puts it:

"The best feature ideas are those that clearly articulate the user benefit, not just the technical implementation. Tell us the story of how your suggestion will make someone‘s experience with WordPress better."

Be open to feedback and iteration

Your initial suggestion is just the starting point. Be open to feedback, questions, and suggestions from the core team and other contributors. Your idea will likely evolve and improve through discussion and collaboration.

Helen Hou-Sandí, WordPress core contributor and 10up Director of Open Source Initiatives, offers this advice:

"Approach the feature suggestion process with a spirit of collaboration, not ego. The end goal is to make WordPress better, not to get your exact vision implemented. Trust in the collective wisdom of the community to help refine your idea."

Be patient and persistent

Getting a feature into WordPress core is a marathon, not a sprint. It can take months (or even years) for a suggestion to make its way through the development process.

Don‘t get discouraged if your idea doesn‘t get an immediate response or if it takes a long time to gain traction. Keep participating in the discussion, promoting your idea, and being an advocate for the benefits it would bring to users.

As WordPress co-founder Matt Mullenweg has said:

"Some of the best features in WordPress today started as user suggestions. Your idea might take a while to get implemented, but don‘t underestimate the power of persistence and a great idea."

Go forth and suggest!

Whew, that was a lot of information! But you‘re now equipped with everything you need to make high-impact feature suggestions for WordPress using Trac.

Remember: WordPress relies on its community to help guide its evolution. Your ideas and perspectives are incredibly valuable, whether you‘re a developer or an end-user.

So go forth and suggest! Share your vision for how to make WordPress even better. With some research, clear communication, and persistence, you could very well see your idea come to life in a future WordPress release.

And if you ever get stuck or have questions, don‘t hesitate to reach out to the welcoming WordPress community for help. We‘re all in this together, working to build a better web with WordPress.

Happy suggesting!