Blueprint
Blueprint is the intersection of functional programming and content management.
Composable. Predictable. Built to last.
Conceptual Origins
The genesis for this project started a little over two years ago in November of 2023 (as I'm writing this it's Jan 13, 2026). I was working a complex project that involved reverse engineering a WordPress site running "WPTux" which was/is a higher-education e-learning site/theme from Wiley.
I would like to thank two people from the Cascade CMS ecosystem Wing Ming Chan, and Artur Tomasiak for planting some seeds in my brain. In 2019, Wing Ming Chan gave a talk at the Cascade CMS User Conference about "A Tree Based Approach" and that sparked somethign in my brain. Artur and I worked on a "Fed Ex" day project together towards the end of my 2nd stint with Hannon Hill and the concept was essentially "what if the build package was also maintained by the CMS" and I thought "yeah, that would make sense". I.e. a straight pipe from the HTML factory (in our case Webpack) to the CMS, which in turn has its own asset factory to generate system and page components.
All of which to say, this methodolgy has been brewing for a while.
The Long Haul, The Long Game
After working the project that inspired this framework I was super-burned out and it was the 2nd tough project I worked in a row that was essentially a bespoke build. One was a ProcessWire/WordPress project (ProcessWire managed a locations oriented CMS, and WordPress managed the marketing side),, and the other was the aforementioned Cascade CMS project.
My goal/dream was to create a system that would allow me to manage a large amount of websites so that I could build some "passive income" stream and then turn my focus back to more creative efforts like music and photography.
Much, much, easier said than done, and I ended up shooting myself in the foot a lot.
I spent the last 6 months of 2025 goind down the "vibe code" rabbit hole and when I realized that what I had was a solid proof of concept, but nothing that was going to be solid enough to build on, I decided to "retreat" to another project I had on "deep freeze" and that was a Webpack tutorial that this whole methodology is based on.
Thematically Speaking
Currently, web pack is the way I build the HTML theme content that is transpiled into PHP functional partials that WordPress and FlightPHP consume.
Functional Components
Although I didn't draw on any particular source of inspiration other than my own mind for the functional component aspect of this project, I can remember two points in my life where I started to dabble in the React universe through some tutorials and learning paths.
For my work, and interests, I never really gratitated toward that method, however, I believe I would be lying if I didn't at least tip that cap to other frameworks and ecosystems I've dabbled in. I also tried Astro out on two separate occasions, and both times I ended up continuing down the path that has led me here.
I'm happy I did, although I do wish I would have reached out to other people to .. although I suppose I did try at one point and it led me to just continuing on "Lone Wolf" style.
Recursive Data Structures
The Blueprint methodology relies on the systems ability to define data structures in a recursive pattern. This approach was first tried in ProcessWire and then later came to life in WordPress using Carbon Fields.
I spent the last 6 months fine-tuning the approach, and we are a close to the "WordPress" bone as possible.
Bootstrap
My first introduction to HTML frameworks was Foundation, but my longest relationship has been with Bootstrap. I like the way it looks out of the box the most compared to other HTML frameworks. I chose to spend most of my effort in the functional PHP build and management with the mentality that would the hardest part, and I could go back (and dive deeper) into Bootstrap when the time came.
End Result
The goal with Blueprint was to create a CMS wrapper that would allow for max-reuse and durability. I would trade the extra time it takes to build out site pages now in the classic WordPress knowing in the future I can add TipTap style page building on the front end, and still have a method to go as granular as I want on the backend if need be.