open-design/design-templates/waitlist-page/example.html
Tom Huang b5eb8c1647
feat: generic skills + split skills/design-templates + finalize-design API (#955)
* feat: general-purpose skills with @-mention composition and user import

Lift skills from "one mode-bound skill per project" to a generic capability
the user can compose per turn:

- Daemon: scan multiple skill roots (user-skills under runtime data, then
  the bundled `skills/`); user-imported skills can shadow built-ins by id.
- New `POST /api/skills/import` and `DELETE /api/skills/:id` endpoints,
  with CONFLICT/BAD_REQUEST/NOT_FOUND error codes and built-in delete
  protection.
- ChatRequest gains `skillIds: string[]`; the chat run concatenates each
  picked skill's body (and merges craftRequires) into the system prompt
  for that turn only — the project's persistent `skillId` is untouched.
- Web composer: `@` popover now lists skills alongside project files;
  picks render as removable chips above the textarea and ride along with
  the request as `skillIds`.
- Settings → Library: import form (name/description/triggers/body),
  per-card delete for user skills, "user" origin badge.

* chore(web): drop welcome pet teaser + add ds→prompt-template mapping util

- SettingsDialog: remove the inline pet adoption teaser from the welcome
  panel so the first-run modal stays focused on configuration.
- New `inferPromptTemplateCategoriesForDs(ds)` helper that maps a design
  system's authored metadata to prompt-template gallery categories.
  Imported by the design-system gallery wiring on a sibling branch; no
  callers in this branch yet.

* feat: split skills/design-templates and add finalize-design API

Phase 0 of the skills/design-templates refactor (specs/current/
skills-and-design-templates.md):

- Move ~104 rendering catalogue entries from skills/ to design-templates/
  and keep skills/ for the small set of functional skills that *do work*
  on user input (utilities, briefs, packagers).
- Add design-templates/AGENTS.md and skills/AGENTS.md describing the
  contract, and a brand-agnostic craft/ surface for opt-in craft rules.
- Daemon: add DESIGN_TEMPLATES_DIR / USER_DESIGN_TEMPLATES_DIR roots and
  an /api/design-templates surface mirroring /api/skills. Asset/example
  routes still span both registries so existing srcdoc URLs keep
  resolving across the rename.
- Web: split LibrarySection into SkillsSection + DesignSystemsSection,
  rename the EntryView "Examples" tab to "Templates", and update locales
  + the New-project picker accordingly.

Adds the finalize-design endpoint:

- New apps/daemon/src/finalize-design.ts and packages/contracts/src/api/
  finalize.ts — one-shot synthesis of a project's transcript + active
  design system + current artifact into <projectDir>/DESIGN.md via the
  Anthropic Messages API. Per-project .finalize.lock mirrors the
  transcript-export hygiene from PR #493; provider credentials are not
  persisted by the daemon.

Other supporting changes:

- README + AGENTS.md updates to document the new directory split and
  craft/ surface, plus i18n strings across 13 locales.
- Test refactors and new coverage (finalize-design, runs, sidecar
  server, plus refreshed daemon integration tests).
- .gitignore: scope the *.exe ignore to /OpenDesign.exe so legitimate
  vendor binaries are no longer hidden.

* fix(merge): move clinical-case-report to design-templates/

Origin/main added the clinical-case-report skill under skills/ before
the skills/design-templates split landed. Its od.mode is prototype, so
per specs/current/skills-and-design-templates.md it is a design template
and belongs alongside the other rendering catalogue entries — not under
the slimmed-down functional skills/ root. Moving it keeps the EntryView
Templates tab consistent with origin/main's intent.

* feat(skills): curated design/creative catalogue + collapsible Settings rows

Seed ~100 curated design/creative skill stubs under skills/ sourced from
awesome-claude-skills (ComposioHQ) and awesome-agent-skills (VoltAgent).
Each stub carries an od.category tag so the new filter pill row in
Settings -> Skills can group them. The seed script
(scripts/seed-curated-design-skills.ts, pnpm seed:curated-design-skills)
is idempotent: it only creates folders that don't already exist, so
hand-edited stubs are never overwritten.

- Daemon: parse and surface od.category on SkillInfo with a strict slug
  normaliser; mirror the field on SkillSummary in @open-design/contracts.
  Category is purely a UI hint — system-prompt composition is unchanged.
- Web: rewrite SkillsSection from a left-list / right-detail grid into a
  vertical stack of collapsible rows mirroring the External MCP panel
  (header always visible with name + mode/source/category pills + per-row
  enable toggle; SKILL.md preview, file tree and inline edit form expand
  on demand). Add a Category filter row above the list. Reorder Settings
  nav so Skills + External MCP sit above the Composio/MCP cluster. Update
  composer placeholder/hint across 17 locales to advertise '@ files or
  skills · / for commands'.
- Docs: extend skills/AGENTS.md with the curated catalogue rules
  (idempotency, category vocabulary, no upstream vendoring).

Co-authored-by: Cursor <cursoragent@cursor.com>

* test(skills): teach localized-content + system-prompt tests about the skills/design-templates split

mrcfps blocking review on PR #955: the skills/design-templates split
(b5993385) moved ~110 SKILL.md entries out of `skills/` and into
`design-templates/`, but two repo-level tests still hard-coded the
single-root layout, so CI gates went red on the merged branch:

- `e2e/tests/localized-content.test.ts` only scanned `<repo>/skills`
  while the locale `skillCopy` map keeps id-keyed entries spanning
  both roots (ExamplesTab/Templates uses one lookup regardless of
  origin). Teach the helper to read both `skills/` and
  `design-templates/`, deduplicating ids so the union matches the
  localized claim.
- `apps/daemon/tests/prompts/system.test.ts` read
  `skills/live-artifact/SKILL.md`, which now lives under
  `design-templates/live-artifact/`. Update the absolute path so
  composeSystemPrompt's coverage of the live-artifact preamble is
  exercised again.

Also enroll the curated design/creative catalogue (PR #955, ~91
stubs sourced from awesome-claude-skills / awesome-agent-skills) in
the DE / FR / RU `_SKILL_IDS_WITH_EN_FALLBACK` lists. The stubs are
English-only by design (frontmatter advertises an upstream URL); the
fallback list is exactly the place to acknowledge "we know this id
exists, English copy is fine here" so the localized-content coverage
gate passes without forcing a translation task per locale.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix(skills): always quote frontmatter name so importUserSkill round-trips numeric / boolean ids

mrcfps PR #955 review: `buildSkillMarkdown` emitted `name:
${escapeYamlString(name)}` without quotes, so YAML coerced names
like `123`, `true`, `false`, or `null` into non-string scalars on
re-parse. listSkills() then read `data.name` as a number/boolean
and the import flow's follow-up `findSkillById(skills, result.id)`
missed it, falling into `/api/skills/import`'s "imported skill
could not be re-read" 500 path for those ids.

Switch the emitter to a quoted scalar (`name: "..."`) — the
double-escape already in `escapeYamlString` makes the quoted form
safe — and add a round-trip test covering `123`, `true`, `false`,
`null`, and `0` to lock in the contract.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix(web): drop staged-skill chips when the matching @<id> token leaves the draft

mrcfps PR #955 review: `submit()` always forwarded every id in
`stagedSkills`, but that state was only mutated on picker click and
chip removal. Hand-deleting an `@<id>` token from the textarea left
the chip staged, so the request still carried `skillIds: [<id>]` and
the daemon composed a skill the prompt no longer referenced.

Sync the chips with the draft inside `handleChange()` by pruning
`stagedSkills` whenever the new value no longer contains the
`@<id>` token (using the same whitespace boundary as
`removeStagedSkill`'s strip regex). Comment explains why this
prune does not run for `staged` file attachments — users frequently
add files via the upload button without leaving an `@<path>` token,
so a symmetric prune there would erase legitimate uploads.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix(daemon): stage @-composed skills' side files alongside the active skill

codex PR #955 review: composing a per-turn `@`-picked skill into the
system prompt appended its body (with the `withSkillRootPreamble`
guidance pointing at relative paths under `<cwd>/.od-skills/<folder>/`)
but never staged the actual folder. `startChatRun` only copied
`activeSkillDir`, so when the project's primary skill was different
(or absent) the composed skill's references/, examples/, and scripts/
files lived only at their absolute repo path — agents that honour
the cwd-relative form (or that don't get `--add-dir`, e.g. Codex with
allowlisted gpt-image projects) couldn't reach them.

Thread the composed skills' dirs out of `composeDaemonSystemPrompt`
as `extraSkillDirs` and stage each one through the same
`stageActiveSkill` API used for the primary skill. Dedupe by folder
basename so a project whose primary skill is also `@`-composed isn't
copied twice. Each preamble already advertises its own folder, so the
prompt and the staged tree stay aligned without further changes.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix(web): respect the Library disable toggle in the project @-mention picker

codex PR #955 review: only `EntryView` received `enabledSkills`
(filtered against `config.disabledSkills`); active projects still
got `skills={skills}` raw, so a skill the user disabled in Settings
kept appearing in the project's `@`-mention popover and could ride
along to the daemon via `skillIds`. That broke the Library toggle
for any project opened on the post-split branch.

Compute a functional-skills-only enabled subset
(`enabledFunctionalSkills`) and pass it into `<ProjectView>` instead.
Templates stay separate — design-templates are filtered through their
own `enabledDesignTemplates` memo for the Templates gallery — so
ProjectView's chat composer still only sees skills, never templates,
matching the pre-split prop surface.

Co-authored-by: Cursor <cursoragent@cursor.com>

* test(e2e): mock /api/design-templates for example-use-prompt flow

The Templates tab in EntryView fetches from /api/design-templates after
the skills/design-templates split (specs/current/skills-and-design-templates.md).
The example-use-prompt Playwright scenario only mocked /api/skills, so the
gallery card never appeared and the test timed out waiting on
example-card-warm-utility-example. Serve the same fixture summary on both
endpoints so the templates gallery renders the card the test clicks.

Co-authored-by: Cursor <cursoragent@cursor.com>

* test(tools-pack): create design-templates fixture for resources test

The packaging resources copy now bundles the new design-templates tree
alongside skills (see resources.ts BUNDLED_RESOURCE_TREES). The
copyBundledResourceTrees fixture only created skills, design-systems,
craft, etc., so the recursive copy crashed with ENOENT on
design-templates before it could check the prompt-templates assertion.
Add the missing fixture directory so the test exercises the same set
of resource trees the packaged build does.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix(skills): clone built-in side files into the shadow on first edit

mrcfps PR #955 review: editing a built-in skill wrote a USER_SKILLS_DIR
shadow folder that contained only a new SKILL.md. The next listSkills()
pass surfaced the shadow as the active dir, but every side-file resolver
(/api/skills/:id/files, /example, /assets/*, the system-prompt preamble,
and the per-turn cwd staging) reads through skill.dir. With nothing but
SKILL.md in the shadow, the bundled assets/, references/, scripts/, and
examples/ disappeared the moment the user hit save — a built-in like
last30days or live-artifact would break immediately after edit instead
of just having its body overridden.

Teach updateUserSkill() to take a `sourceDir` and clone every entry
except SKILL.md / dotfiles into the shadow on the very first edit. The
shadow stays self-contained, so all the resolvers keep working without
fallback bookkeeping. Subsequent edits detect the existing shadow and
skip the clone, so user tweaks under the side tree survive a re-save.

Wire `sourceDir: skill.dir` from server.ts's PUT /api/skills/:id handler
and add two regression tests:
- 'clones built-in side files into the shadow on the first edit' walks
  the file tree after save and asserts assets/template.html, references/
  notes.md, and scripts/helper.sh all round-trip from the built-in.
- 'preserves user-edited side files on subsequent edits' edits the
  staged assets/template.html, re-saves, and confirms the user content
  is still there.

Co-authored-by: Cursor <cursoragent@cursor.com>

* test(e2e): rename home tab from Examples to Templates

The Examples tab was renamed to Templates in EntryView (b5993385's
skills/design-templates split — entry.tabExamples became entry.tabTemplates
and the tab value moved from 'examples' to 'templates'), but
entry-chrome-flows still asserted the old label and testId. Update both.

* fix(skills+web): preserve template body in API mode and dir-based skill delete

Two follow-ups from PR #955 review:

1. ProjectView only received `enabledFunctionalSkills`, but
   `composedSystemPrompt()` still resolved `project.skillId` through that
   prop and `fetchSkill()`. Projects created from the new
   `/api/design-templates` surface keep a template id in `project.skillId`,
   so opening one in API mode dropped the template body from the system
   prompt and the upstream request ran without the project's primary
   template instructions. Now ProjectView takes a separate
   `designTemplates` prop (the unfiltered template list, so a
   later-disabled template still loads for projects already created from
   it) and `composedSystemPrompt()` plus the metadata / `isDeck` lookups
   fall back to that list, with `fetchDesignTemplate()` as the body-fetch
   fallback to `fetchSkill()`. The chat composer's `@`-picker keeps
   receiving only the enabled functional skills.

2. `DELETE /api/skills/:id` used `deleteUserSkill(USER_SKILLS_DIR, skill.id)`
   which re-slugified the frontmatter id and removed
   `<userSkillsDir>/<slug>/`. That matched the import shape but missed the
   install shape — `installFromTarget` writes the folder at
   `sanitizeRepoName(url)` (GitHub) or `path.basename(realpath)` (local
   symlink), neither of which is guaranteed to equal the slugified
   frontmatter `name`. A duplicate `app.delete('/api/skills/:id', ...)`
   handler at the install routes never fired because Express resolved the
   earlier registration first, leaving the install/uninstall path without
   working teardown. The handler now removes `skill.dir` (the absolute
   path listSkills already discovered) under a USER_SKILLS_DIR safety
   check, using `lstat` + `unlinkSync` so symlinked local installs unlink
   cleanly without recursing into the user's source tree. The dead
   duplicate handler is removed; `deleteUserSkill` is dropped from the
   server.ts import set (still exported and unit-tested in skills.ts).
   Regression coverage in `apps/daemon/tests/skills-delete-route.test.ts`
   pins both shapes plus the symlink-preserves-source case.

* test(daemon): point hyperframes system-prompt test at design-templates

The merge with main brought in a hyperframes system-prompt test that
reads `skills/hyperframes/SKILL.md`, but this branch's split moved
`hyperframes` into `design-templates/` (same migration as `live-artifact`
already handled above in this file). CI was failing with ENOENT on the
old path.

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-11 17:48:34 +08:00

400 lines
12 KiB
HTML

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Meridian — Coming Soon</title>
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Syne:wght@700;800&family=DM+Sans:wght@400;500;600&display=swap" rel="stylesheet">
<style>
:root {
--bg: #FDE8DF;
--fg: #1A1410;
--color-ink: #1A1410;
--accent: #1A1410;
--deco: #E8835A;
--deco-logo: #E8522A;
--deco-stripe: #F5A623;
--input-border: rgba(196, 169, 154, 0.38);
--success: #2D6A4F;
--btn-label: #FDE8DF;
--ticker-bg: rgba(0, 0, 0, 0.9);
--ticker-fg: rgba(255, 255, 255, 0.9);
--deco-stroke: rgba(0, 0, 0, 0.12);
--logo-shadow: rgba(0, 0, 0, 0.08);
--font-body: 'DM Sans', sans-serif;
--font-display: 'Syne', sans-serif;
}
*, *::before, *::after {
box-sizing: border-box;
margin: 0;
padding: 0;
}
html, body {
height: 100%;
overflow-x: hidden;
}
.logo {
position: absolute;
top: 20px;
left: 24px;
display: flex;
align-items: center;
gap: 14px;
z-index: 10;
}
.logo-container {
width: 48px;
height: 48px;
flex-shrink: 0;
border-radius: 50%;
background: linear-gradient(135deg, var(--deco-logo) 0%, var(--deco) 100%);
display: flex;
align-items: center;
justify-content: center;
overflow: hidden;
box-shadow: 0 2px 8px var(--logo-shadow);
}
.logo-svg {
width: 100%;
height: 100%;
object-fit: contain;
padding: 2px;
}
.logo-text {
display: flex;
align-items: center;
gap: 10px;
flex-shrink: 0;
}
.logo-name {
font-family: var(--font-display);
font-weight: 700;
font-size: 18px;
letter-spacing: -0.02em;
color: var(--color-ink);
}
.logo-dot {
font-size: 10px;
color: var(--deco-logo);
opacity: 0.6;
}
body {
font-family: var(--font-body);
background-color: var(--bg);
color: var(--fg);
display: flex;
flex-direction: column;
min-height: 100svh;
overflow-x: hidden;
overflow-y: auto;
}
.upper {
flex: 0 0 auto;
display: flex;
flex-direction: column;
align-items: center;
justify-content: center;
text-align: center;
padding: 60px 24px 40px;
position: relative;
z-index: 2;
}
.headline {
font-family: var(--font-display);
font-weight: 800;
font-size: clamp(56px, 8vw, 96px);
letter-spacing: -0.03em;
line-height: 1.0;
color: var(--fg);
text-align: center;
max-width: 900px;
margin: 0 auto 22px;
}
.subtext {
font-size: clamp(15px, 1.5vw, 18px);
font-weight: 400;
line-height: 1.6;
color: var(--fg);
max-width: 420px;
margin-bottom: 44px;
}
.form-row {
display: flex;
gap: 8px;
width: 100%;
max-width: 560px;
justify-content: center;
}
.form-row input {
flex: 1;
min-width: 0;
padding: 14px 18px;
font-family: var(--font-body);
font-size: 15px;
color: var(--color-ink);
background: transparent;
border: 1.5px solid var(--input-border);
border-radius: 4px;
outline: none;
transition: border-color 0.2s;
}
.form-row input::placeholder {
color: var(--input-border);
}
.form-row input:focus {
border-color: var(--fg);
outline: 2px solid var(--fg);
outline-offset: 2px;
}
.form-row button {
flex-shrink: 0;
padding: 14px 22px;
font-family: var(--font-body);
font-size: 15px;
font-weight: 500;
color: var(--btn-label);
background: var(--accent);
border: none;
border-radius: 2px;
cursor: pointer;
white-space: nowrap;
transition: opacity 0.15s, transform 0.1s;
}
.form-row button:hover {
opacity: 0.85;
}
.form-row button:active {
transform: scale(0.98);
}
.success-msg {
display: none;
margin-top: 18px;
font-size: 15px;
font-weight: 500;
color: var(--success);
}
.success-msg.visible {
display: block;
}
.deco-section {
flex: 1;
position: relative;
overflow: hidden;
min-height: 25vh;
display: flex;
flex-direction: column;
}
.coil-row {
display: block;
width: 100%;
height: 60px;
flex-shrink: 0;
background: var(--bg);
}
.stripe {
width: 100%;
height: 14px;
background: var(--deco-stripe);
flex-shrink: 0;
}
.grid-floor {
flex: 1;
position: relative;
background-color: var(--deco);
min-height: 80px;
}
.grid-svg {
position: absolute;
inset: 0;
width: 100%;
height: 100%;
}
.ticker-wrap {
width: 100%;
overflow: hidden;
background: var(--ticker-bg);
padding: 10px 0;
flex-shrink: 0;
}
.ticker-track {
display: flex;
gap: 24px;
white-space: nowrap;
animation: ticker-scroll 20s linear infinite;
}
.ticker-unit {
font-family: var(--font-body);
font-size: 11px;
font-weight: 600;
letter-spacing: 0.15em;
text-transform: uppercase;
color: var(--ticker-fg);
flex-shrink: 0;
display: flex;
align-items: center;
gap: 12px;
margin-right: -12px;
}
.ticker-star {
color: var(--deco-stripe);
margin-right: 4px;
}
@keyframes ticker-scroll {
from { transform: translateX(0); }
to { transform: translateX(-50%); }
}
@media (prefers-reduced-motion: reduce) {
.ticker-track {
animation: none;
}
}
@media (max-width: 600px) {
.logo {
left: 16px;
top: 16px;
gap: 10px;
}
.logo-container {
width: 40px;
height: 40px;
}
.logo-name {
font-size: 14px;
}
.upper {
padding: 30px 16px;
flex: 0 0 50vh;
}
.form-row {
flex-direction: column;
align-items: stretch;
}
.form-row input,
.form-row button {
width: 100%;
}
}
</style>
</head>
<body>
<div class="logo">
<div class="logo-container">
<svg class="logo-svg" viewBox="0 0 100 100" xmlns="http://www.w3.org/2000/svg">
<circle cx="50" cy="50" r="48" fill="var(--deco-logo)"/>
<text x="50" y="60" font-family="'DM Sans', sans-serif" font-size="42" font-weight="700" text-anchor="middle" fill="var(--btn-label)" letter-spacing="-1">Md</text>
</svg>
</div>
<div class="logo-text">
<span class="logo-name">Meridian</span>
<span class="logo-dot">·</span>
</div>
</div>
<section class="upper">
<h1 class="headline">Meridian is<br>almost here</h1>
<p class="subtext">The workspace that connects your ideas before you've finished thinking them.</p>
<form class="form-row" id="waitlist-form">
<input type="text" name="firstname" placeholder="First name" autocomplete="given-name">
<input type="email" name="email" placeholder="Work email" autocomplete="email" required>
<button type="submit">Join the Waitlist</button>
</form>
<p class="success-msg" id="success-msg" role="status">You're on the list! We'll be in touch.</p>
</section>
<div class="deco-section">
<svg class="coil-row" viewBox="0 0 1440 60" preserveAspectRatio="none" xmlns="http://www.w3.org/2000/svg">
<g fill="none" style="stroke: var(--deco-stroke);" stroke-width="1.5">
<path d="M 9,60 A 41,30 0 0 1 91,60"/>
<path d="M 94,60 A 41,30 0 0 1 176,60"/>
<path d="M 179,60 A 41,30 0 0 1 261,60"/>
<path d="M 264,60 A 41,30 0 0 1 346,60"/>
<path d="M 349,60 A 41,30 0 0 1 431,60"/>
<path d="M 434,60 A 41,30 0 0 1 516,60"/>
<path d="M 519,60 A 41,30 0 0 1 601,60"/>
<path d="M 604,60 A 41,30 0 0 1 686,60"/>
<path d="M 689,60 A 41,30 0 0 1 771,60"/>
<path d="M 774,60 A 41,30 0 0 1 856,60"/>
<path d="M 859,60 A 41,30 0 0 1 941,60"/>
<path d="M 944,60 A 41,30 0 0 1 1026,60"/>
<path d="M 1029,60 A 41,30 0 0 1 1111,60"/>
<path d="M 1114,60 A 41,30 0 0 1 1196,60"/>
<path d="M 1199,60 A 41,30 0 0 1 1281,60"/>
<path d="M 1284,60 A 41,30 0 0 1 1366,60"/>
<path d="M 1369,60 A 41,30 0 0 1 1451,60"/>
</g>
</svg>
<div class="stripe"></div>
<div class="grid-floor">
<svg class="grid-svg" viewBox="0 0 1280 400" preserveAspectRatio="none" xmlns="http://www.w3.org/2000/svg">
<g style="stroke: var(--deco-stroke);" stroke-width="1" fill="none">
<line x1="640" y1="0" x2="0" y2="400"/>
<line x1="640" y1="0" x2="128" y2="400"/>
<line x1="640" y1="0" x2="256" y2="400"/>
<line x1="640" y1="0" x2="384" y2="400"/>
<line x1="640" y1="0" x2="512" y2="400"/>
<line x1="640" y1="0" x2="640" y2="400"/>
<line x1="640" y1="0" x2="768" y2="400"/>
<line x1="640" y1="0" x2="896" y2="400"/>
<line x1="640" y1="0" x2="1024" y2="400"/>
<line x1="640" y1="0" x2="1152" y2="400"/>
<line x1="640" y1="0" x2="1280" y2="400"/>
<line x1="0" y1="80" x2="1280" y2="80"/>
<line x1="0" y1="160" x2="1280" y2="160"/>
<line x1="0" y1="240" x2="1280" y2="240"/>
<line x1="0" y1="320" x2="1280" y2="320"/>
<line x1="0" y1="390" x2="1280" y2="390"/>
</g>
</svg>
</div>
</div>
<div class="ticker-wrap" aria-hidden="true">
<div class="ticker-track">
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
<span class="ticker-unit">COMING SOON <span class="ticker-star"></span></span>
</div>
</div>
<script>
document.getElementById('waitlist-form').addEventListener('submit', function(e) {
e.preventDefault();
if (!this.checkValidity()) {
this.reportValidity();
return;
}
this.style.display = 'none';
document.getElementById('success-msg').classList.add('visible');
});
</script>
</body>
</html>