Last updated on June 17, 2026
One of the most significant planning efforts currently underway is a new documentation initiative focused on the architecture and evolution of the site itself.
While the development section already contains articles covering many individual technologies and systems—including WordPress customization, custom post types, server infrastructure, security, workflows, and content organization—those articles were written over time and often focus on individual components rather than the larger system they collectively support.
The goal of this new project is to create a comprehensive overview explaining how a standard WordPress installation evolved into a structured knowledge platform through custom development, content modeling, automation, and AI-assisted architectural planning.
Rather than focusing exclusively on code, the project will attempt to show how the site’s various systems interact and why they were created in the first place.
Planned areas of documentation include:
- WordPress foundations and theme architecture
- Parent themes versus child themes
- Custom post type design and evolution
- Advanced Custom Fields (ACF) structures and relationships
- Shared templates and modular code organization
- Helper functions and reusable components
- Taxonomies and content classification systems
- Relationship mapping between content types
- Portal systems and navigation architecture
- Footnotes and content discovery systems
- Development workflows and version control
- AI-assisted development and architectural planning
A major component of the project will be the creation of visual architecture maps using simple text-based diagrams. These diagrams will help illustrate both the physical structure of the codebase and the logical structure of the knowledge systems built on top of it.
Examples include:
- Folder and file hierarchies
- Theme and template loading flows
- Custom post type relationships
- Taxonomy structures
- Content architecture maps
- Request and rendering workflows
- Evolution diagrams showing how the site changed over time
In addition to serving as public documentation, the project will act as a form of architectural review and knowledge preservation. By documenting the reasoning behind systems that were developed over several years, it becomes easier to understand how the platform functions today, how individual components interact, and how future development can be approached more systematically.
The long-term vision is to create both a high-level overview article and a collection of deeper technical breakdowns that together provide a complete picture of the platform’s design, evolution, and underlying architecture.