The new WordPress proposal seeks to integrate a new type of General Information Post directly into WordPress Core. The new feature, already in Gutenberg, serves as a central repository of guidelines and information about the website for use by people such as editors and contributors, as well as internal AI agents and tools. This proposal quickly received a thumbs up from developers, who often feel that the feature does not serve what users really need.
What is a Custom Post Type (CPT)?
Currently in WordPress, there are two types of post types:
- Posted
- and pages.
WordPress can also be extended with Custom Post Type (CPT) plugins that allow site owners to create new custom post types. For example, the WooCommerce plugin uses a custom post type called “product” that allows store owners to manage products.
Suggestion for Combining the Type of Information Post
The Knowledge Custom Post Type was proposed in February 2026 and a month later it was integrated into the Gutenberg plugin as a Test feature for the following knowledge types:
“Site — Your site’s goals, personality, target audience, and industry.
Copy – Tone, voice, brand personality, and word preferences. The editorial style guide, lives within WordPress.
Images – Preferred image styles, colors, moods, and topics to include or avoid.
Blocks – Block type rules for each block of content. For example, specifying that Paragraph blocks should favor short sentences, or that Image blocks should always include separate descriptive text.
Additional – Anything else: accessibility requirements, linking practices, formatting conventions, or rules that are inconsistent with the above sections.”
WordPress Causes Confusion Over Who’s New Feature Is
WordPress aims to centralize Knowledge Custom Post Type (CPT) so that all website operators, including humans, AI agents, tools, and plugins, can access website guidelines.
But the proposal is met with resistance for a number of reasons. One of them is that the proposal introduces a new feature as being for use by humans and AI, but the GitHub repository for this feature clearly lists it as being for use by AI only:
“Guidelines CPT maintains universal editorial rules — brand voice, copy standards, image guidelines. This is one type of educational content a site needs, but not the only one.
As AI-powered tools converge with WordPress, there is a growing need for sites to store various types of persistent, structured information that shapes how agents interact with the site. “
Usability and human usability are not mentioned once on that page. There is a gap between the description of the public proposal and the actual technical details. This makes it doubtful whether anyone really knows who or what the new feature is for and how it will be used.
That’s one of six reasons developers cited why the proposal felt ill-advised and unnecessary.
Opposition to the Proposal
This proposal was met with opposition from members of the WordPress developer community in the Dynamic WordPress Facebook group (must join to read the discussion), with 29 comments strongly opposing the proposal to make this feature core.
There were six reasons why engineers opposed the proposal:
- This should be a plugin, not a core functionality.
- The theme has enough of it; working out will only add to the bloat.
- There are important priorities, where many native languages are unanimously cited as the most important missing activity.
- There was some doubt as to whether the proposal had been fully considered.
- Many have suggested that this is not a user-facing task; for AI.
- A few have suggested that this functionality benefits Automattic business users on WordPress.com more than the average WordPress user.
Resistance to the proposal to centralize functionality has not been limited to social media, the announcement on WordPress itself has drawn questions about the need for core functionality.
A commenter shared:
“I know it says this feature is provided for both “author-facing and agent-facing” applications, but it sounds like AI/LLMs are driving the idea for the feature.
Furthermore, the basic assumption that “Most sites already have content standards” doesn’t strike me as accurate. That’s a real need and use case, but I’m not sure it’s one that would justify a major new feature on its own.
…I think there is a lot of promise in this aspect, but I also wonder if we need a broader lens that considers the full range of use cases, especially for humans.”
Namith Jawahar said:
“This seems like an unnecessary overreach. It’s better to let developers decide for individual sites than to force a post type on everyone.”
Aaron Jorbin commented that it sounds like a great feature but it feels incomplete at the moment.
“As it is, this feels incomplete. I think it sets the stage and with so much time left before 7.1, I think this would be a great addition.”
Second New Feature Asked
This marks the second time in WordPress version 7 that a new feature was highly requested. Version 7.0 saw developers question the need for Real-Time Collaboration (RTC), which was supposed to focus on Phase 3 collaboration.
Featured image by Shutterstock/MNStudio
