Minify++
A native minifier focused on shrinking web assets with conformance, reproducibility and straightforward command-line use.
Optimization should be a focused stage, not ownership of the whole build.
Minify++ is Gantry’s native web-asset minification project. It takes already-produced web assets and makes them smaller while keeping correctness measurable through regression and conformance work.
Keeping minification separate from generation has practical benefits: development output can stay readable, the optimizer can be tested independently, and projects that do not use Nift can still use the same minifier.
The project’s direction is evidence-led rather than “support every syntax because the README says so.” CSS conformance work establishes a strong measured baseline, while broader HTML and JavaScript coverage remains explicit engineering work rather than assumed compatibility.
Useful capability without mandatory complexity.
The project stays focused on its own job; the surrounding Gantry tools remain optional.
Add minification without introducing a Node-based build environment solely for this step.
Use external and regression evidence to distinguish supported syntax from optimistic claims.
Run after generation, before packaging/deploy, or independently against existing web assets.
Treat stable, testable output as part of release quality rather than merely chasing the smallest byte count.
Start with the shortest path.
Advanced deployment or integration features appear only when the workflow actually needs them.
- 01
Build or obtain the web assets you want to ship.
- 02
Run Minify++ as a dedicated optimization step rather than mixing minification logic into templates or application code.
- 03
Validate the deployable output in the same release pipeline that performs the optimization.
Connections that remove real hand-off friction.
Each product already owns one side of these workflows. The integration exists to remove duplicate navigation, setup or context.
Nift
Nift generates the site; Minify++ optimizes deployable assets. Keeping those roles separate means Nift stays a templating/build tool and Minify++ remains useful for projects generated by anything else.
Explore Nift →Markup++
Markup++ can produce HTML from authored documents earlier in a content pipeline. Minify++ is the later optimization step if the final output benefits from shrinking.
Explore Markup++ →Jsonic++
The small build tools share one useful property: they can be chained when a project needs several focused transformations without becoming one giant all-purpose compiler.
Explore Jsonic++ →Local tool, no my.* indirection.
Minify++ is primarily a CLI or embeddable native tool rather than a persistent web service. A my.* instance registry would add a choice where there is no running instance to choose.
It still belongs to Gantry Tools, appears in the project directory and can be exposed from a configurable my.gantry.cv launcher if somebody wants quick access to its website or documentation.
Why my.* is reserved for running applications →Where Minify++ earns its place.
Keep development output readable and minify only the artifacts that are actually shipped.
Avoid adding a second runtime just for web-asset optimization.
Test minification behaviour separately from the framework or generator that produced the source.
Explore Minify++.
Project-specific installation, commands and release details live on the project site.