What Caddy solved well
Caddy kept HTTPS and static hosting straightforward. For a project like this, the real value was not novelty but operational calm: fewer moving parts and a smaller deploy surface.
The part that needed care
Clean URLs, asset caching, and API proxy behavior needed deliberate rules. The site now has more entry points, so a shallow misconfiguration would show up quickly as stale assets or broken internal navigation.
What I watch after deploy
- Do hub pages load the right styles and canonical tags?
- Do API-backed tool pages keep working while static pages are served normally?
- Are docs and blog links crawlable without confusing the main workflow pages?