Complex workflows.
Useful systems.

The brief called for one administrator, local editing on a Mac Studio and the option to publish remotely. SQLite keeps content in the project’s storage directory, while uploaded originals retain their filenames. Drafts can be prepared before they appear publicly.

Keeping the application and its content separate makes container rebuilds repeatable. The persistent storage directory still needs a backup: an image cache can be regenerated, but original uploads cannot.

Collections use pagination instead of loading the full archive. Images are resized into cached WebP variants, and responsive source sets let the browser select a suitable size. Large originals stay out of the initial page load.

Case studies are rendered as HTML so headings, text and links are available directly. Canonical URLs, metadata and a sitemap support discovery without depending on client-side rendering.

Docker Compose runs the application alongside Caddy. Cloudflare Tunnel connects the public domain to the local HTTPS origin, with certificate verification enabled.

The initial public SSL failure also exposed a DNS routing problem: the domain was still pointing to the previous host. Fixing the end-to-end route mattered as much as getting the application running locally.

Imported case studies returned successful responses while responsive visibility classes hid content on smaller screens. The repair preserved the captured content and restored the missing panels at mobile and tablet widths.

That informed a more useful check: verify source text, images and panel visibility as well as HTTP status. Testing should reflect what someone can actually read and use.