WordPress Proposes Knowledge Custom Post Type for Core, Faces Strong Opposition
Review the Knowledge CPT proposal and decide if you want to adopt it as a plugin or wait for core integration.
Decide whether to adopt the Knowledge CPT as a plugin or wait for core integration.
Summary
WordPress is proposing to merge a Knowledge Custom Post Type (CPT) into core, a feature that would store site‑wide editorial rules such as brand voice, copy standards, image guidelines, and block‑level rules.
The CPT is already available as an experimental feature in Gutenberg and covers five knowledge types: Site, Copy, Images, Blocks, and Additional. The proposal was met with resistance from the developer community, with 29 comments largely against it; critics argue it should remain a plugin, add bloat, and prioritize other features like multilingual support. Developers also question its primary audience, noting that the feature appears designed for AI agents rather than human editors, and that it may benefit Automattic’s enterprise users more than the average site owner. Despite the pushback, the proposal remains under discussion, and its eventual inclusion would change how editors and AI tools interact with WordPress sites.
Key changes
- Proposal to add Knowledge CPT to core to store site‑wide editorial rules
- Currently experimental in Gutenberg with five knowledge types: Site, Copy, Images, Blocks, Additional
- 29 comments largely against the proposal, citing bloat and missing priorities
- Critics argue it should remain a plugin rather than core feature
- Feature appears aimed at AI agents more than human editors
- Potential benefit skewed toward Automattic enterprise users
- Opposition includes concerns about multilingual support and core bloat
- Proposal remains under discussion and may change editor and AI tool interactions