Biogard

Biogard is the first thing I built. My oldest saved chat on it is about a React app that would not start, and a hidden fly minigame was already in the plan early on. After that the site moved to Next.js 14 on Netlify with a Neon database. By the time of the rebuild it showed its age. The database's free tier ran out of quota and blanked the live blog (post pages returned 500). The icons were auto-traced and the FAQ had an 'Ask the AI' button.

I wrote a one-sentence brief: rebuild it to today's standard, keep the information and every URL, no AI look, hand-drawn illustrations, both languages. The agent wrote the shell first (i18n, routing proxy, SEO helpers, design tokens, header and footer), then fanned out eight agents in parallel across pages, blog, legal, APIs, illustration and SEO. A site crawler written during the fan-out became the quality gate. Production DNS then moved to the new server.

1. 01

   A URL contract

   Bulgarian pages are unprefixed and English lives under /en; a proxy rewrites both into app/[lang] and 308-redirects old /bg/ paths. The build guide forbids renaming a slug, because the slugs are the indexed URLs. At cutover the crawler reported 122 pages and 0 problems.

2. 02

   Hand-drawn SVG

   27 pest icons, 9 places and 2 scenes, drawn on a 64 by 64 grid with currentColor strokes, replaced the auto-traced set. I cut a generated hero video and put a drawn cutaway of a house in its place, with pests turning back at a red barrier. The copy rules ban em dashes and stock AI phrasing.

3. 03

   Isolated on a shared host

   Docker Compose runs Caddy, Next.js and Postgres 17, and only Caddy publishes ports. Containers are read-only with all capabilities dropped, no-new-privileges and CPU, memory and PID limits; images are pinned by digest, and gVisor is available for the internet-facing services. An egress firewall chain stops the containers from opening connections into the tailnet, cloud metadata or private ranges. Releases are timestamped directories behind a current symlink with a rollback script, each deploy runs smoke tests that check host isolation, and the database is dumped nightly.

4. 04

   SEO and compliance as a phase

   The SEO plan maps 55 routes in two languages to one primary keyword each, so pages do not compete for the same query, with titles of at most 60 characters, descriptions of 140 to 160, llms.txt and four sitemaps. The site publishes no prices, since each treatment is quoted individually. Claims that biocides are safe, non-toxic or eco were removed to comply with Article 72 of the EU Biocidal Products Regulation.

5. 05

   A bug game the site does not mention

   Off by default. Typing 'biogard' or the Konami code, or tapping the logo seven times, wakes 13 species including a golden fly and a Cockroach King boss; 'ddd' fumigates the page, and moths swarm between 21:00 and 05:00. Analytics count who finds it and who plays. It keeps the site personal without getting in a customer's way.

Live at biogard.bg since the DNS cutover. After PR #39, Google PageSpeed Insights scored the mobile home page 100 in all four categories, with LCP down from 2.7 s to 1.5 s (the agent's own run, not repeated for this page). Self-hosted, cookieless Umami counts visitors, filtered to Bulgarian time or language after foreign bot traffic showed up. Unfinished: the Google reviews block is built and stays off until the listing has three ratings, double opt-in for the newsletter was dropped as friction and sits as dormant code, and there are only 24 unit test cases, so the crawler is the main gate. The ads method is now a written playbook in the ValoxVSL repo.

• 

  Hand-drawn service scene: a drone over reeds.

• 

  Hand-drawn service scene: a kitchen.

• 

  Hand-drawn service scene: a park.

• 

  Hand-drawn service scene: an apartment block.

• 

  Hand-drawn service scene: a barn and a greenhouse.

• 

  Rebuilt as version two.

•