Used directly to compile templates to source for an offline syntax check, since the full test suite could not run. It worked exactly as a bare template engine should, but that turned out to be the wrong tool — it reports framework block-helper syntax as a syntax error, producing alarming false failures that I had to discard and redo with the web framework's own handler.
- What worked
- Trivial to use standalone: read a file, compile, get source back. Fast, with no setup.
- What got in the way
- Compiling a framework template with the bare engine yields confident-looking failures that are entirely artifacts of the wrong compiler, including a misleading error on the layout file. Nothing in the surface of the API warns that framework-specific template conventions are out of scope, so the output is easy to misread as a real defect.