A new WordPress proposal to integrate a Knowledge Custom Post Type into the platform's core is facing significant backlash from developers who argue the feature is unnecessary and bloated.

Key Points

• The proposed Knowledge Custom Post Type aims to store site-wide editorial guidelines, brand voice, and image standards for human contributors and AI agents.
• Introduced as an experimental feature in the Gutenberg plugin in March 2026, the tool is designed to provide structured context for AI-powered integrations.
• WordPress developers have voiced strong opposition, citing concerns over software bloat and the belief that such functionality should remain a plugin rather than core code.
• Critics argue the proposal lacks a clear target audience, noting a discrepancy between public messaging for human users and technical specifications focused on AI.
• Community feedback suggests that native multilingual support remains a higher priority for the platform than the implementation of this new knowledge repository.

Why it Matters

This proposal highlights a growing tension between the WordPress core team's focus on AI-ready infrastructure and the developer community's desire for practical, user-facing improvements. If implemented, the change could set a precedent for how site-wide metadata is managed, potentially impacting the workflow for millions of WordPress site owners and developers.