Dropie: foundation slice and controlled expansion

The starting point was a product with broad scope, but without one public surface that safely represented direction, state, and implementation discipline.

The implementation had to stay tied to repository truth, keep routing out of the CMS, and avoid second-wave complexity before the first slice stabilized.

The solution used explicit locale-first route trees, structured documents, and fixed template families instead of a generic page-builder approach.

The content boundary was locked first, then settings, home, pillar, and fixed pages were wired, and only then the Work detail families were added.

The biggest gain does not come from broad scope all at once, but from disciplined sequencing and truthfulness across implementation layers.