Wesley Financial Group Marketing All tools

Landing Page System  /  How to use it

One foundation. Every page free to experiment.

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

Lock the system Free the layout
Status dashboard
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 WFG Vault, so the design stays on-rails while the layout stays yours.

Step 02 / gate

Approve the content

Copy, claims, stats, and branding get approved on the local file. Both are locked from here on.

Step 03

Drop it into the repo (Claude Code)

Stage the approved HTML and images in the page's Drive subfolder, then hand the HTML to Claude Code. It builds the page from the template, wires the lead path, registers it as in-review, checks it at phone width, 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 lp.wesleyfinancialgroup.com/<page-slug>; share the link and PIN (ask Zach) 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, David, or Cameron

An approver reviews the real URL and flips the page 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). Conversion tracking and lead attribution are automatic; every lead lands in Salesforce through the shared Zap.

2

The page lifecycle

Four statuses. 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>/<page-slug>-fix, edit only your 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, David, Brandon, Morgan (+ Paul, Lilah): build pages, self-merge their own page PRs.
  • Approvers — Zach, David, Cameron: flip pages to approved (live) or archived (retired).
  • Reviewers — Charles, Cameron: review gated pages, build experiment pages like any builder.
  • System owners — Zach (+ David): the locked layers (shared assets, server, 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.
  • Style with brand tokens only; green is for CTAs only.
  • Start from the template and keep its locked includes.
  • One page per branch (<you>/<page-slug>), PR into main.
  • Lead capture through the locked paths only, never a custom form.
  • Copy follows the Vault compliance rules; mobile ready at 390px; images lean.

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, and the CI that holds it all together.