Marketing All tools

Landing Page System  /  How to use it

One foundation. Every page free to experiment.

Ship a landing page to go.kindhomepainting.com fast. The brand, the tracking, and the lead pipeline are already handled.

Lock the system Free the layout
Status dashboard Team PIN: 2017
Cowork iteration Content approval Repo, PR to main Deploys PIN-gated Team reviews real URL Approver flips registry Live

There is no staging site

The PIN gate does that job: every page ships to production but stays invisible to the public until an approver flips it live.

1

How a page ships

Six steps, idea to live. Claude knows the system, so at every step you can just ask it to do the work.

Step 01

Iterate in Cowork Layout free

Build whatever layout the campaign needs as a single local HTML file. Claude pulls the brand and canonical stats from the Kind Home Vault, so the design stays on-rails while the layout stays yours.

Step 02 / gate

Approve the content

Copy, claims, and stats get approved on the local file. All of it is locked from here on.

Step 03

Drop it into the repo (Claude Code)

Hand the approved HTML to Claude Code. It builds the page from _template, wires the lead path (locked form → relay → Salesforce → Apptoto), registers it as in-review, checks it at 390px, and opens the PR.

Step 04

Merge it yourself

No waiting on reviewers: when the Page lint check is green, merge your own PR. The page deploys behind the team PIN at go.kindhomepainting.com/<slug>; share the link and PIN with anyone who should see it.

Form test: submit with Testing123 as the name. It stays out of Salesforce but shows in Zapier.
Step 05 / gate

Approval Zach or Corey

An approver reviews the real URL and flips the registry to approved. The moment that deploys, the gate lifts and the page is live.

Step 06 / live

After launch

Watch every page on the status dashboard (/status, team PIN). Every lead lands in Salesforce through the shared relay and Zap, and booking hands off to Apptoto by ZIP.

2

The page lifecycle

Anything not approved shows the PIN gate, even on production.

in-progress in-review approved = live archived

Archive, don't delete

Done pages get flipped to archived: a retired notice for the public, still openable with the PIN. Pause any ads first.

Fixing a live page

Branch <you>/<slug>-fix, edit only your page folder, self-merge on green. The page stays live.

3

Who does what

Builders ship their own pages. Only approvers change what the public sees.

  • Builders · Zach, Corey (+ anyone onboarded): build pages, self-merge their own page PRs.
  • Approvers · Zach, Corey: flip pages to approved (live) or archived (retired). CI enforces this by GitHub login.
  • System owner · Storystak (Zach): the locked layers (shared assets, relay, template, CI).
4

The guardrails

CI enforces these on every PR, and Claude knows them all. The short version:

  • Only build inside your own page folder.
  • Brand tokens only. Coral is THE cta color: one per page.
  • Start from the template and keep its locked includes.
  • One page per branch (<you>/<slug>), PR into main.
  • Lead capture through the locked form only, never a custom form or direct webhook.
  • Copy follows the Vault rules: canonical stats via get_canonical_stat, Michael never Steven, no em dashes.
  • Mobile ready at 390px.
  • Images lean (under 400 KB, CI-enforced).

Full detail on every rule lives under the hood.

What's under the hood

How the system is built: the locked layers, the review gate, the lead pipeline, the Apptoto handoff, and the CI that holds it all together.