sent here for Marquee
tailwind react saas landing page template · React and HTML source
MarqueeTailwind React SaaS landing page template
A dark-first Tailwind React SaaS landing page template for subscription reconciliation and finance operations.
- 67 / 67
- light / dark tokens
- 2
- modes, both designed
- 1
- DOM, rendered twice
- unlimited projects, client work included
- 12 months of updates
- 14 days, no questions
AGENTS.md and 4 skills ship in the zip, so your own agent keeps changing it after you buy.
docs: install, use, customizepages, composed from 18 sections
Every page is a real render from the publish gate, in the mode on show. Open any of them in the live preview.
- Recur — subscription analytics/
- site-header
- hero
- ticker-rail
- sources-band
- metrics-grid
- +4
Product — wire, match, close/product- site-header
- product-tour
- ticker-rail
- cta
- site-footer
Integrations: sources reconciled/integrations- site-header
- integration-catalog
- connection-detail
- source-request
- site-footer
Pricing — one meter, MRR tracked/pricing- site-header
- pricing-plans
- faq
- site-footer
Customers — closes with names on them/customers- site-header
- case-study
- ticker-rail
- customer-wall
- site-footer
Start free — the first match/signup- site-header
- signup-panel
- site-footer
Components/components- site-header
- hero
- ticker-rail
- sources-band
- integration-catalog
- +13
Seven routes ship a whole marketing site for Recur: the ticker-rail home, product tour, searchable integrations catalog with a read-only Stripe sample, pricing, customers, validated signup and the living styleguide. The integrations route separates provider availability, sample authorization, sync freshness, mapping completeness and close publication, with exact source objects and a visible frontend-only boundary. Local search, billing arithmetic, validation and focus recovery work in React without implying OAuth, persistence or data movement. Ships three self-hosted variable typefaces, 66 semantic tokens per mode, computed AA pairs, generated poster grain, 30 reusable components and a light variant designed as blush paper rather than an inversion. A framework-free HTML template edition carries the same seven routes as compiled documents, with local fonts and vanilla JavaScript in place of a React runtime.
sections and primitives
You get the parts, not just the demo site. Every frame is a real capture from the theme's own styleguide page, and the source path under it is where the file lands in your project. 22 frames cover them, with 13 primitives sharing the ui/* frame.
tokens, both modes
Change one variable and every part follows. Each badge is one token split down the middle: its light value on the left, its dark value on the right, with the theme's own paired ink on both halves.
hover or tab a badge for its name and both values, enter copies
The ticker rail: a full-bleed, hairline-bounded strip of timestamped mono events drifting edge to edge between sections — a different evidence feed on each of three routes (the wire, the match log, the go-lives).
every token
typefaces, self-hosted
Real woff2 files in src/fonts/, wired through next/font and licensed under OFL. Nothing is fetched from Google at build time, so the zip renders these letterforms offline. Scale ratio 1.333.
Marquee
A dark-first Tailwind React SaaS landing page template for subscription reconciliation and finance operations.
const { open, close } = useLedger("2026-03") // 0123456789
- display
- Bricolage Grotesque
- text
- Schibsted Grotesk
- mono
- Spline Sans Mono
- captionAg
- smallAg
- bodyAg
- leadAg
- d1Ag
- d2Ag
- d3Ag
- d4Ag
every width is a real render from the publish gate
Four viewports, each one a render the gate produced and checked. Switch between them: the frame narrows exactly as a window does, because that is what it is.
every token and every part on one page
The styleguide route is not documentation about the theme. It is a page in the zip that renders the real components from the real tokens, so it stays true the day you change one.
files in the zip
Two independently authored editions: React for applications, plus ready HTML, CSS and vanilla JavaScript for static hosts.
- AGENTS.mdthe theme's own rules, written for an agent
- .claude/skills/4 skills, each one job
- add-page/SKILL.mdCompose a new Marquee route from existing sections
- add-section/SKILL.mdAdd a new self-contained section to Marquee following its existing patterns
- check-quality/SKILL.mdRun Marquee's own gate locally
- rebrand/SKILL.mdApply a buyer's brand to Marquee
- src/
- theme.css67 tokens, light and dark
- fonts.tsthe faces, wired to the type tokens
- app/7 files
- components/18 files
- ui/18 files
- assets/1 markdown file, 1 image
- fonts/3 font files, 3 licenses
- app/7 routes, plus layout.tsx and globals.css
- theme.jsonthe manifest: tokens, components, pages
- html/the framework-free edition
- dist/7 compiled routes, deploy-ready — no build step
- src/the Nunjucks source the routes compile from
- scripts/build-html.ts · serve-html.ts — `bun run build:html` / `preview:html`
- README.mdquickstart
- 6 project filespackage.json · tsconfig.json · next.config.ts · postcss.config.mjs · env.d.ts · .gitignore
Your key goes in TAILTHEMES_LICENSE_KEY, and the registry entry goes in components.json. The snippet is on the docs page.
skills your agent can run
Your agent reads AGENTS.md before it edits, then runs the skill that fits the change. The skills are the theme's own, and the publish gate makes an agent complete every one of them in a scratch copy before the theme goes live.
34 components, 7 pages and 67 tokens, as a Next.js project.
AGENTS.md carries the design spec. Each skill is one job written against it.
Claude Code, Codex, or any agent that reads AGENTS.md. It runs on your machine, on your own account.
Built from the theme's own sections, on the same tokens and the same rhythm.
The source is yours to run, edit and deploy.
The spec ships inside the folder, so the page your agent adds next month is built by the same rules as the ten it came with. Nothing calls back here.
What the standard license coversWhat do I actually get?
Does it include the pages I'd otherwise have to build?
Will it work with my stack?
How long before it stops looking like a template?
Can I use it for client work?
A SaaS is two builds, not one.
Marquee is the site that sells the product. Appetite is the thing people log into once they have paid — same Tailwind version, same token architecture, so the two halves can be made to look like one company.
activity
- v1.4.2: The ticker rail has a keyboard-reachable Pause switch, retention and churn come from the close statement, the field-mapping table fits every width, and icons share one stroke.
- v1.4.1: The header's Start free is now an outlined button, so the hero's filled call to action is the only one in the first viewport.
- v1.4.0: Disclosure and the whole form family in both editions; a hundred lines of hand-rolled flow retire
- v1.3.1: Docs now state how tokens reach the HTML edition and what a new route owes it
- v1.3: Button disabled and busy states, a textarea, and a real submitting phase on the signup panel
- v1.2: Separate Nunjucks source and framework-free HTML output for every route
- v1.1: Integration coverage, sample sync health and exact field mapping
- v1.0.0 — dark-first SaaS landing: ticker rails, pricing switch, signup island
- a changelog route once the fiction ships releasesplanned
for agents
This listing is also a markdown document and a JSON endpoint. The theme's own agent kit is on the kit and agents plates above.
