A new suggestion for WordPress aims to include a new Knowledge Custom Post Type directly into WordPress Core. However, developers were not in favor of this proposal, as they believe it does not align with users’ actual needs.

What does Custom Post Type (CPT) mean?

Currently, there are two types of Post Types available in WordPress.

  1. Articles
  2. and Documents.

WordPress can be expanded using Custom Post Type (CPT) plugins to create new post types customized for specific needs. For instance, the WooCommerce plugin utilizes a custom post type named “product” for managing products.

Proposal for Combining a Knowledge Post Category

The Knowledge Custom Post Type was suggested in February 2026 and included in the Gutenberg plugin a month later as an Experimental feature for various types of knowledge.

Your website’s objectives, brand identity, audience, and sector. Essential information that any tool or contributor can utilize.

An editorial style guide within WordPress that includes tone, voice, brand personality, and vocabulary preferences.

Preferred image preferences, such as styles, colors, moods, and subjects to include or avoid.

Rules for different types of content blocks, such as Paragraph blocks emphasizing short sentences or Image blocks requiring descriptive alt text.

Additional information may include accessibility needs, linking methods, formatting standards, or other guidelines not covered in the previous sections.

WordPress Causes Uncertainty Regarding the Target Audience for the New Feature

WordPress plans to incorporate the Knowledge Custom Post Type (CPT) into its core system to enable all website users, including people, AI agents, tools, and plugins, to access site guidelines.

The proposal is facing opposition for various reasons, including the discrepancy between how it is portrayed for humans and AI and its actual intended use for AI only on the GitHub repository.

The CPT Guidelines contain overall editorial rules for the website, including brand voice, copy standards, and image guidelines. This type of instructional content is essential for a site, although there are other types needed as well.

AI-driven tools are increasingly being incorporated into WordPress, leading to a growing demand for websites to retain various forms of organized and enduring information that influences user interactions.

The page does not address the usefulness and practicality of the new feature, leading to a disconnect between the public description and the technical details, raising doubts about its intended audience and purpose.

Developers mention at least six reasons why they feel the proposal is unwise and unnecessary, with that being just one of them.

Opposition to the suggestion

Members of the WordPress developer community in the private Dynamic WordPress Facebook group expressed strong opposition to the proposal, with 29 comments unanimously against merging the feature into the core.

Developers opposed the proposal for six reasons.

  1. This ought to exist as a plugin rather than a feature within the core system.
  2. Core contains sufficient elements; adding more functionality will only result in unnecessary bulk.
  3. Native multilingual is consistently identified as the top priority for improvement, with other issues taking a back seat.
  4. There were uncertainties regarding the thorough consideration of the proposal.
  5. Many have proposed that this function is not intended for users; rather, it is meant for artificial intelligence.
  6. Some believed that this feature is more advantageous for Automattic’s business clients on WordPress.com compared to the typical WordPress user.

Resistance to integrating the function into the core was not just seen on social media, as the WordPress announcement also sparked inquiries about the function’s necessity in the core.

mrwweb, a commenter, shared:

I feel that AI/LLMs are influencing the development of this feature, even though it is meant for both authors and agents.

The idea that “Most websites already have content guidelines” seems questionable to me. It’s a valid need, but I’m unsure if it warrants a new primary feature by itself.

I believe there is great potential in this aspect, but I also question whether it requires a more comprehensive approach that takes into account a wider variety of scenarios, particularly those involving people.

Namith Jawahar made a comment.

This seems like an excessive intervention. It would be preferable to allow developers to make the decision for each site rather than impose a post type on everyone.

Aaron Jorbin believes the feature is promising but incomplete at present.

This seems unfinished as it stands. With the time left before version 7.1, I believe it has the potential to be a valuable addition.

A new feature is being questioned for the second time.

WordPress version 7 faced scrutiny for a new feature for the second time, with developers questioning the need for Real-Time Collaboration (RTC), a key aspect of Phase 3 collaboration.

Image provided by Shutterstock/MNStudio was highlighted.

LEAVE A REPLY

Please enter your comment!
Please enter your name here