Heptabridge Website Handover

Developer handover · 20 Nov 2026

Releasing heptabridge.com

Everything needed to host the new Heptabridge website and point the domain at it. The source code comes as a zip from the owner, with this same guide inside as HANDOVER.md.

  • Next.js 16.4.6
  • Static export → out/
  • Host: Cloudflare Pages
  • Secrets in code: none

Where things stand

Owner inputs before release

All in lib/site.ts. While a value is null, the site shows a visible bracketed placeholder.

FieldShown inStatus
supportEmailFooter, Privacy, Terms, Refund policyWaiting
postalAddressFooter, PrivacyWaiting
bookingUrl"Pick a time" button on /book (HubSpot meetings link)Waiting

The legal pages (/privacy, /terms, /refund-policy) show "Draft for lawyer review. Not yet in force." from components/LegalPage.tsx. Remove that line only after the owner confirms a lawyer approved the text. Rebuild and redeploy after any edit.

Build

Node 20.9 or newer (built and tested on Node 24).

npm ci
npm run build

Output is out/: about 98 files, under 2 MB. Pages export as about.html and so on, and Cloudflare Pages serves them at clean URLs (/about). For a local preview, run npm run dev and open http://localhost:3000.

Next.js was updated from 16.4.3 to 16.4.6 on 20 Nov to clear npm advisories, and npm audit now reports 0. None of those advisories affected a static export.

Hosting on Cloudflare Pages

Chosen because the free plan allows commercial use, public/_headers works with no extra config, and it is fast globally. Northwest's plan is WordPress-only, and Vercel's free plan is non-commercial only.

Option A: upload from your machine (simplest)

npx wrangler login
npx wrangler pages project create heptabridge --production-branch main
npx wrangler pages deploy out --project-name heptabridge --branch main

Option B: connect a Git repo

Build commandnpm run build
Build output directoryout
Environment variableNODE_VERSION = 24

Either way, the project lives in the owner's Cloudflare account. Ask the owner to invite you as a member rather than sharing a password. The temporary heptabridge.pages.dev address is kept out of search engines by a rule in _headers.

Domain and DNS

Registered at Northwest, with a transfer lock on. Do not transfer the domain. Only the DNS changes.

The domain has live email at Northwest. MX, SPF, DMARC and any DKIM records must survive the switch, or company email stops or lands in spam.

Live DNS on 20 Nov 2026

RecordValue
NSns1/ns2.hosting.businessidentity.llc
A @, www66.223.49.89 (current Northwest site)
MX @mailserver.businessidentity.llc, priority 10
TXT @v=spf1 a mx include:spf.postal.businessidentity.llc ~all
TXT _dmarcv=DMARC1; p=quarantine; rua=mailto:bounce@dmarc.businessidentity.llc; ruf=mailto:bounce@dmarc.businessidentity.llc; fo=1

Recommended: move DNS to Cloudflare (free)

  1. In Cloudflare, add the site heptabridge.com on the Free plan and let it scan the records.
  2. Ask Northwest for a full zone export and compare. The scan can miss DKIM (selector._domainkey TXT records), so add anything missing by hand.
  3. Keep every mail record DNS only (grey cloud).
  4. If DNSSEC is on at Northwest, turn it off first.
  5. Ask Northwest to switch to the two Cloudflare nameservers. Their support chat can do it.
  6. When the zone is active, go to Pages → heptabridge → Custom domains and add heptabridge.com and www.heptabridge.com.
  7. Redirect www to the bare domain with a 301 Redirect Rule. The canonical URL in the code is https://heptabridge.com.
  8. Send a test email to and from a heptabridge.com address.

Alternative: keep DNS at Northwest

Point www at heptabridge.pages.dev with a CNAME. Pages can't serve the bare domain unless the zone is on Cloudflare, so the bare domain would need a forward to www at Northwest, if they offer one. In that case, set site.url to https://www.heptabridge.com.

The form (HubSpot)

Release checklist

Content rules

Don't change copy without the owner.

Map of the code

PathWhat it is
lib/site.tsCompany details, nav, HubSpot IDs
lib/content.tsThe seven leaks, bundles and the full service list (one source for every page)
lib/submitCheck.tsForm submission
app/*/page.tsxOne folder per page
components/home/Homepage sections and logo animation (logo-motion.js)
components/pages/Page visuals: clinic day arc, job route, no-show maths
public/_headersProduction security headers

What was tested

31 OctLocal production build: all pages and links, logo animation, reduced motion, headers on a Cloudflare-style server, phone width, and one real form submission that reached HubSpot.
20 NovAfter the Next.js update: rebuild passed, and the homepage, Capabilities and Book pages load with no console errors.
Not yetOn Cloudflare's servers, on real phones, or with the final owner details filled in.