Publishing

Deploy, edit, roll back

Static site on Vercel. Git push deploys. No build step.

Deploy path

  1. Commit changes on a feature branch (e.g. cnsvs-net-buildout).
  2. Open PR → review → merge to main.
  3. Vercel git integration auto-deploys production from main.
  4. Manual: vercel deploy --prod from a machine with project access.

Preview deployments are created per PR/branch for visual QA before merge.

How to edit a page

  1. Open the HTML file in the repo root or docs/.
  2. Keep the design system: palette vars, header/footer patterns from index.html / clinical-practice.html.
  3. No external fonts/CDNs. Inline CSS only. Keep each page lightweight.
  4. Preserve compliance copy rules (no diagnostic claims; demo attestation; patients handoff language).
  5. If the page is ad-funded, keep meta robots noindex and robots.txt Disallow entry.
  6. Include Umami snippet + GTM/GA4 placeholders; include UTM capture script on marketing pages.

Adding a new landing page

  1. Copy a persona page skeleton (hero → how it works → report → CPT → proof → dual CTA → escape → FAQ).
  2. Add nav/footer links from home if it should be discoverable.
  3. Update robots.txt and /docs/ads destination map.
  4. Pass UTMs in ad traffic: ?utm_source=…&utm_medium=…&utm_campaign=…

Rollback

Form / API notes

api/demo.js is the only serverless runtime code. Changing the demo contract requires coordinating with Dave (green-list + Salesforce). Do not load-test demo.php.

DNS (Phase 2)

Point cnsvs.net at Vercel when Dave adds records. Until then, previews validate pages on Vercel URLs.

Team bar

Every page includes <script defer src="/team-bar.js"> — a slim campaign overlay for Mark, Alan, and JSJD. Normal visitors never see it.

Edit the page↔campaign mapping in marketing/pages.json. Browse the full database at /docs/marketing.