SureAdhere marketing website
The public marketing site for SureAdhere by Dimagi. It is a static HTML site: no framework, no build step, no database. You edit HTML and CSS files directly, or have Claude Code do it using the skills below.
This README is the orientation guide. The day-to-day editing rules live in CLAUDE.md, which Claude Code loads automatically.
Status: live
The site is live at https://sureadhere.dimagi.com/ (launched 2026-07-27). How it's wired:
- Hosting: GitHub Pages, deployed from this repo (
sureadhere/marketing), main branch, root folder. Merging to main publishes automatically; the live site updates about a minute later.
- Custom domain:
sureadhere.dimagi.com is set in Settings → Pages (the CNAME file in the repo root belongs to that setting — do not delete it), with Enforce HTTPS on. The domain is also org-verified for GitHub Pages (takeover protection).
- DNS: a CNAME record
sureadhere.dimagi.com → sureadhere.github.io in the dimagi.com Cloudflare zone, deliberately DNS-only (grey cloud) so GitHub can manage the TLS certificate. DNS changes go through Dimagi web infra.
- Legacy URLs:
sureadhere.com and dimagi.com/sureadhere both 301-redirect here. Old sureadhere.github.io/marketing/* URLs redirect automatically.
- Launch checklist (all done): app-store privacy-policy URLs updated (Play live; iOS ships with the next app version), HubSpot cookie banner verified on the new domain.
Pages and where they live
Live URLs are relative to https://sureadhere.dimagi.com/.
| File | Live URL | Notes |
|---|
index.html | / | Homepage |
clinical-trials/index.html | /clinical-trials/ | Solution page |
public-health/index.html | /public-health/ | Solution page |
behavioral-health/index.html | /behavioral-health/ | Solution page |
resources/index.html | /resources/ | FAQ, timeline, release notes |
publications/index.html | /publications/ | Shown as "Evidence" in the nav: list of studies |
contact/index.html | /contact/ | Demo request and contact |
privacy-policy/index.html | /privacy-policy/ | Legal (sync with Dimagi legal) |
privacy-policy-chinese/index.html | /privacy-policy-chinese/ | Legal, Chinese |
login/index.html | /login/ | Bare redirect to the secure app |
404.html | served on not-found | Has nav and footer |
Shared assets: assets/styles.css (all shared CSS), assets/images/ (all images), assets/favicon.png.
SEO files: sitemap.xml, robots.txt.
Run and preview locally
The site is plain files, so any static server works. The repo is already configured two ways:
- Claude Code preview (recommended when working in Claude Code): ask Claude to preview; the config in
.claude/launch.json serves it on port 3030.
- Manually: from this folder run
npx serve -p 3030 . and open http://localhost:3030.
Always view the page you changed plus one other page, to catch header/footer drift.
Making common changes
| You want to... | Do this |
|---|
| Change a nav link, the logo, or anything in the footer | Run the update-header-footer skill (ask Claude: "update the header/footer"). It edits every page consistently. |
| Add a whole new page | Run the add-page skill. It scaffolds the page and registers it in the sitemap and footer. |
| Add a study to the Evidence page | Run the add-publication skill. |
| Edit copy or images on one existing page | Edit that page's HTML directly, following the brand and content rules in CLAUDE.md. |
| Change colors, spacing, or shared components | Edit assets/styles.css, using the existing CSS variables. |
Skills (in .claude/skills/)
- update-header-footer: propagate a nav/footer change to all 10 pages, handling the root-vs-subpage path difference and the active-nav state.
- add-page: create a new page from the canonical template and register it everywhere it needs to appear.
- add-publication: add a correctly formatted study to the Evidence page.
SEO files to keep current
sitemap.xml lists every public URL on sureadhere.dimagi.com. Update it when you add, remove, or rename a page.robots.txt points the sitemap at https://sureadhere.dimagi.com/sitemap.xml.- Each page has its own
<title>, <meta name="description">, canonical URL, and Open Graph (og:) tags in its <head>. When you clone a page, change all of these; do not leave the source page's metadata in place.
Brand and assets
- Teal
#0DA89D primary; Work Sans and JetBrains Mono fonts.
- Logo:
assets/images/sureadhere-logo-full-color.png (rendered white via a CSS filter in the nav and footer).
- App store badges:
assets/images/badge-app-store.svg, assets/images/badge-google-play.png.
Layout conventions
A few site-wide patterns set in assets/styles.css that are easy to undo by accident:
.section-head is centered. Every section heading block (eyebrow + h2.section-title + .section-lede) is center-aligned, max-width: 760px, with auto horizontal margins. Page heroes use .hero-title directly, not .section-head, so they stay left-aligned. Wrap any new section heading in <div class="section-head"> and it picks up the right style automatically.- Footer external links show a
↗ arrow. A scoped rule (footer .footer-col a[target="_blank"]::after, footer .footer-bottom a[target="_blank"]::after) appends the indicator. Internal links and the app-store badge links stay clean.
- Green sector pills on the home Partner Stories cards use
.sector-tag, defined inline in index.html under .partner-stories-dark. Reuse the class on any new partner-story card to keep the pattern consistent.
- Hero video on the homepage autoplays muted via the standard Wistia embed (
autoPlay=true muted=true playsinline=true). Browsers will not autoplay with sound; the player's own unmute control is the only way for visitors to hear it.
Handle with care
- Legal pages. The two privacy policies are legal text. Coordinate edits with Dimagi legal.
- External links. The "Sign In" button, the login redirect, the help site, and the app store badges point to live systems. Do not change these URLs without confirming the new target.
- Version control. This folder is a git repository with its origin at
github.com/sureadhere/marketing — the production repo, since GitHub Pages deploys straight from main. Commit every change so the team has history and a safe undo, and push (or merge a PR) to publish.
Deploy
Merging (or pushing) to main is the deploy. GitHub Pages rebuilds automatically — watch the "pages build and deployment" run under the repo's Actions tab — and the live site updates in about a minute. There is no separate staging environment and no per-PR preview build; preview changes locally before merging (see "Run and preview locally" above). Anyone with write access to this repo can publish.
All canonical URLs, og:url, JSON-LD @id/url, sitemap.xml, and robots.txt point to https://sureadhere.dimagi.com/ and are correct as-is.
