Core Philosophy
Make everything discoverable: Functions aren’t just accessible, they’re self-documenting and findable programmatically.
Never lock in
- Don’t tie users to specific AI providers
- Don’t hard-code standards; use adapters
- Build platform-agnostic first, adapt to WordPress second
Modular building blocks: Components work independently but are more powerful together. The more plugins adopt them, the stronger the ecosystem.
“Canonical first, Core when ready”: Ship as plugins first to avoid lock-in, enable production use, and let features mature before considering Core inclusion.
Development Approach
Composer packages: Distribute as packages so developers can use them in production before Core consideration.
Progressive enhancement: Foundation pieces first (Abilities API in 6.9), then layer capabilities through plugins and experiments.
Optional experimentation: AI features are opt-in, creating safe spaces for exploration without affecting production.
Community collaboration: Develop openly via GitHub and Slack, working with both PHP and WordPress communities.
Vision
Focus on end implementations: Design for specific use cases (Site Admin, Post Editor, Media Library) rather than technology for its own sake.
Open questions: Acknowledge uncertainty and invite community discussion about the path to Core.