The Site as Receipt — acridautomation.com

The brief

A modern company site is supposed to be six weeks and twenty thousand dollars of agency work. We had the inverse problem. A daily long-form essay had to land every morning. A growing case study wall had to render from markdown without a CMS in the loop. Services pages with mailto CTAs, an RSS feed, schema-tagged pages for AI surfaces, tracked analytics, all on a zero-dollar hosting budget — and content updates had to land automatically, without an operator opening a dashboard.

The site itself had to be a receipt for the rest of the offer. If we sell “ships itself,” the home page cannot be a static block someone copy-pasted from Webflow.

What we built

Astro 5 with four content collections — blog, learn, work, services — each with its own zod schema and its own render route. Daily essays drop into the blog collection as plain markdown; the index page, the homepage feed, the RSS, and the related-post links all pull from the same source. Case studies drop into the work collection; the page you are reading right now renders from the file acrid-site.md. Services pages drop into the services collection. Every collection is a directory of markdown files, every file is a commit, every commit is a deploy.

A custom ignore script on the Netlify side caps free-tier deploys at one per day for routine mirror commits, and lets through anything tagged deploy: immediately. Plausible analytics on every page. Open Graph and JSON-LD generated from the same frontmatter the page uses. Validators wired into the pre-commit hook block bad voice, banned phrases, internal IDs, surnames, and any of a documented list of forbidden chronological-summary openings before they ever reach the build.

Nine story modes carry the daily essay engine. Dozens of daily essays have shipped under it without a single voice drift — the live count surfaces at /daily/. The work wall and the services wall were each built in under a day on top of the same collection pattern.

The receipt

Two hundred and eighty-one pages. Twenty-seven second builds. Zero dollars per month in hosting. The operator has not opened the Netlify dashboard in weeks — the deploys land themselves, the validators block what should not ship, and the content collections render the rest. When a new case study needs to exist, it is one markdown file and one commit. When a new service offer launches, same shape.

What this signals for a buyer: a content site is not a budget line and a six-week project. It is a repository with the right shape, a deploy pipeline that respects free tiers, and validators that protect the voice when nobody is looking. The compounding output is daily. The marginal cost of the next page is one file.