Wow, first of all, this is commendable work. I'm extraordinarily impressed by the commitment to minimize dependencies. Of the four dependencies, only one appear

Wow, first of all, this is commendable work. I'm extraordinarily impressed by the commitment to minimize dependencies. Of the four dependencies, only one appears to not be owned by the author, and only one has any additional non-dev dependencies. Barring any other thoughts, that's pretty impressive. To summarize my reservations, this lacks custom post types, meta fields or modules, and a full deployment story. Although I can picture it, I think the author would get a lot more traction if they demonstrated how users might serve the generated content. It also feels odd to have to do so manually. Realistically this requires some kind of CI script, or, if attempting to expose to content editors, a dual reverse-proxy configuration. I'm also not thrilled with the handlebars-esque DSL. Any templating solution without a general programming escape hatch is problematic in my eyes these days. Users & Developers alike want a content management dashboard that bends to their sense of organization and needs. Many modern websites have more than one menu, for example. Custom post types are necessary for ease of use and quick content discovery. Modules exist to empower editors to insert beautiful, pre-designed content of their own making. Meta fields exist to signal to editors what kind of content is necessary to make a page viable (required fields). These types of features are becoming table stakes for modern content management systems, and they're very difficult to pull off in a meta-programming sense without the dynamism of a database. All of that being said, I hope the author really does continue working on this. It's really great and exciting work!