JAlcocerTech E-books

Lessons, as a Checklist

The short version of this book: what I’d do again from day one, and the traps that cost me hours.

Architecture

  • Own the endpoint, not the vendor. Forms post to /api/forms/* on your own domain. Whatever answers that path can change; your sites don’t have to.
  • Store first, everything else second. Alerts, emails and webhooks run after the lead is saved, and their failures never lose it.
  • Rules are data. Sites, kinds, retention, consent wording and the spam blocklist live in versioned files.
  • Keep a copy off-platform from day one. It’s your backup, your analysis database, and the first step of any exit.
  • Write the exit table before you need it. Any row that says “rewrite” is where the lock-in is.
  • Write decisions down, with the alternatives you rejected.
  • Consent is a data structure: what, when, which wording version.
  • Optional consent gets its own unticked box, never bundled into a required one.
  • Double opt-in with signed links: GET shows a page, POST acts, so mail scanners can’t confirm or unsubscribe anyone.
  • One-click unsubscribe headers on every marketing email, and check the raw message: header folding can break them silently.
  • A do-not-send list keyed by hashes, checked right before every send.
  • Retention enforced by code: a TTL or a nightly job, per kind, and by status for subscriptions.
  • Alerts carry no personal data: kind, site, email domain.
  • Write the privacy page against the code. It’s the best audit you’ll do.

Email

  • Send from a subdomain with SPF, DKIM and DMARC.
  • Check each message’s status, not just the HTTP response.
  • Turn tracking off per message if you promise not to track.
  • Capture everything locally (Mailpit) before anything goes out.
  • Test on production with an allow-list of your own addresses.

Sites

  • A real 404 page. Without one, Pages hides every broken link behind a 200.
  • Sitemap, robots.txt with a Sitemap: line, canonical, one host.
  • Security headers, committed, and a CSP checked in a real browser.
  • Self-hosted fonts. Read the LCP breakdown before blaming images.
  • Heavy embeds load on approach.
  • 1200×630 JPEG share cards, not WebP, not a logo.
  • Future posts hidden, daily rebuild on, with dates compared in your readers’ timezone.
  • Deploy only what you committed: a clean worktree, npm ci, the production branch.
  • Audit your own sites with everything on. Fix the tool first if it’s wrong.

Operations

  • The cheap box at home is never on the critical path. It pulls; it doesn’t receive.
  • Send an explicit User-Agent from every script; bot protection blocks the defaults.
  • PYTHONUNBUFFERED=1 in Docker, or your logs stay empty.
  • Runtime data never lives inside a git checkout.
  • Kill processes by port or PID, not pkill -f.
  • Watch the disk. A full /tmp breaks tools in confusing ways.
  • Print a secret’s length and hash prefix to debug it, never the secret.

The business part

The engine makes sure no attention is wasted. It doesn’t create attention. That still comes from writing, sharing and talking to people, which is where the time goes once the plumbing is done.

That’s the AI-business point from the introduction too: the data you’ll want to learn from later, such as who came, from where, what they asked and what happened next, only exists if you captured it cleanly from the first form.