Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

To suggest a feature for WordPress Core, first search Trac for an existing ticket. If there is no matching request, file a clear ticket describing the problem, use cases, and user-experience improvement, then choose the relevant component and suitable workflow keywords. Larger or exploratory ideas may be better suited to a feature project or feature-plugin proposal. A request starts a discussion; it does not guarantee the feature will be built or added to Core.

Choose the right place for your idea

WordPress support questions and feature proposals follow different routes. The Make WordPress Support site directs people seeking help to the support forums or IRC. For a proposed change to WordPress Core, use the Core ticket process and contributor channels.

What you want to do Where to go What to expect
Get help using WordPress or troubleshoot a problem Support forums or IRC, linked from Make WordPress Support Help and discussion, rather than a Core feature proposal
Request a specific, scoped Core improvement Search for and, if needed, create a ticket through the Core process in Contribute with Code A ticket for discussion and possible work; not a commitment to implement it
Explore a broader idea or organize work on a potential feature Consider a Core feature project, a feature-plugin proposal, or broader discussion through Core channels Exploration and collaboration; the work may remain a plugin or experiment, or may not proceed

How to submit a Core feature request

  1. Search for an existing ticket. Look for the idea in Core Trac before creating a new ticket. As you enter a summary, related tickets may appear. If a matching ticket exists, add useful details there instead of opening a duplicate. The Contribute with Code handbook explains the ticket process.
  2. Write a specific summary. State the proposed improvement in plain language so contributors can quickly understand what the ticket concerns.
  3. Explain the problem and who encounters it. Describe the relevant use cases and how the change would improve the experience for users. The handbook says: “If you are submitting a feature request, include a thorough description of your idea, stating use cases and/or user experience improvements.”
  4. Choose the relevant component. File the request in the part of Core it concerns, and use appropriate workflow keywords. The handbook gives needs-patch and needs-feedback as examples.

When to propose a project or feature plugin

Feature projects for exploration

A feature project can bring contributors together to explore an idea for possible inclusion in Core. Work may begin as investigation and develop into a patch or plugin, but a project’s existence does not mean the result will be merged.

Feature-plugin proposals for active leads

A feature-plugin proposal is a better fit when someone expects to take an active, primary role in organizing and developing the feature. The proposal should briefly cover the idea, its current stage, interested participants, and the help needed.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How to get feedback on a larger idea

Bring a concrete issue or proposal to the appropriate Core discussion rather than raising an abstract idea without context. The Navigating the Community handbook recommends explaining an idea in GitHub or Trac before bringing it to the open floor of an appropriate meeting. A larger proposal may also suit a Make blog post.

What happens after you submit it

A ticket or proposal opens a discussion; it does not commit WordPress Core to building the feature. Work may remain an experiment or plugin, or stop before implementation. For a feature plugin to be considered for merging, the handbook identifies a well-tested user experience, mature design, positive community feedback, core-quality code, and a judgment that the feature belongs in Core as relevant criteria. The release lead and Core team make the merge decision.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Can users vote on WordPress feature requests?

A response from a WordPress.org forum moderator says the former feature-voting area had been removed and points people to the Requests and Feedback forum and the Core handbook: Feature Request voting? Because that information comes from a forum response rather than formal current policy documentation, use the current contribution guidance and relevant discussion channels to share your idea. A vote should not be treated as a decision about what Core will build.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.