Design Philosophy
Aethraify Core follows four core principles: stability over trends, long-term usability over chasing the new; clear boundaries over flexibility, well-defined responsibilities; engineering consistency over personal preference, unified standards for collaboration; maintainability over short-term efficiency, clear structure for long-term evolution.
Architecture Advantages
-
Unidirectional Dependencies + Strong Boundaries
Separation of presentation, data, and configuration layers. Templates only render, they do not run WP_Query; Query / API centralize data preparation; ACF / Options handle data structure only. Users never touch system decisions. Classic implementation aligned with FSE philosophy.
-
Conditional Asset Loading
Load CSS/JS by page type: archive, single, page each independent. No Block global style pollution, no theme.json side effects. Unlike FSE where Block CSS is hard to strip, this approach is fully controllable. Clear performance budget, simple debugging.
-
Templates = Code
Templates live in the filesystem: versionable, auditable, rollbackable. No editor state dependency, no "Block editor state bugs." Unlike FSE templates in the database, better suited for enterprise and CI/CD.
-
AI Strong Constraints
Complete P0/P1/P2/P3 rule system. Template / Query / ACF / CPT fully split. grep / i18n / performance with clear acceptance criteria. Cursor Rules ensure AI-generated code follows architecture.
-
Low Debugging Cost
Clear error location: Query / Template / Asset responsibilities are distinct. No black box of "why does this Block work here," no theme.json site-wide implicit issues. Assets_Manager centralizes management, easy to trace.
-
Business Friendly
Core is stable, child themes are clear, commercial features are isolated. Licensing naturally sits in P1/P2 layer. Core is permanently free; commercial child themes can be licensed separately. Suitable for commercial theme development and multi-product lines.
-
Child Theme System
Templates overridable, styles injectable, extension architecture clear. Child themes are "extensible shells," not holes that erode Core. Core upgrades do not depend on child theme state; child themes must not fork Core logic.
Comparison with FSE Theme
| Dimension | FSE Theme | Aethraify Core |
|---|---|---|
| Architecture | Block-driven | Classic + Layered |
| Stability | Fast evolution, API changes | Long-term stable, SemVer |
| Control | theme.json implicit | Code explicit, fully controllable |
| Performance Control | Block CSS hard to strip | Conditional loading, strong |
| AI Friendliness | Rules hard to enforce | Complete rules, high |
| Child Theme System | Weak, almost meaningless | Strong, clear extension |
| Enterprise Readiness | Experimental | Production-ready |
Use Cases
Aethraify Core fits link directories, Tool Hubs, content platforms: stable page structure, frequently changing content, SEO-critical, performance-sensitive, no need for "drag-and-drop anywhere." Also fits commercial theme authors, studios, enterprise sites: long-term maintenance, multi-child-theme reuse, licensing isolation.