Skip to content
Sign inJoin waitlist

Catchup documentation — Next.js

Everything you need to take Catchup for Next.js from the downloaded folder to a published site. Read in this order, or jump to what you need.

Guide What it covers
Install and run Requirements, install, the commands, what is in each folder
Editing the content Editing text, images, projects, services, testimonials, posts and legal pages — no CMS needed
Making it look like your brand Colours, the logo, fonts, text styles, spacing, motion, components, the style guide
Pages and sections The header, the sections of every page with a map of each, adding, removing and reordering pages and sections
Forms Making the inquiry form deliver to you
Using a headless CMS The collections and their fields, for connecting Sanity, Payload, Strapi, Directus or any other headless CMS
Going live Pre-launch checklist, deploying, domains, what to do after launch
Troubleshooting and questions Errors, questions and answers
  • 11 kinds of page, 28 addresses:
    • Home, About, Work, Services, Blog, Contact and the 404 page;
    • a page for each of the 4 projects, the 4 services, the 12 posts and the 2 legal pages, built from the collections (Pages and sections).
  • 5 collections in src/content/collections/: work (work.ts, 4), services (services.ts, 4, each with a Per Project and a Per Month plan), testimonials (testimonials.ts, 10), posts (posts.ts, 12) and legal pages (legal.ts, 2).
  • 1 form: the inquiry on Contact (name, e-mail, a service, budget, timeline, message), with a server action and four ways to deliver it (a log, a webhook, Mailchimp, Resend).
  • A fixed header on every page (on Home a see-through one over the hero, and the fixed one once you scroll past it), with a phone menu.
  • Motion in the components, with reduced-motion support: the Home intro, the hero slideshow, moving logos and testimonials, counting numbers, blocks rising into view; and a style guide of every component at /style-guide.
  • Search and sharing: a title, a description and a canonical link for every page, share cards, light and dark browser icons, sitemap.xml and robots.txt.
  • Placeholders: the photos in public/images/ are grey placeholders that show their sizes (the demo uses photos from Unsplash and Pexels, which can’t be sold with a template). The logo and the client logos are drawn for the template.
  • These docs (docs/), the forms guide (Forms reference), the design system’s reference (Catchup design system), CHANGELOG.md and LICENSE.md.
Terminal window
npm install
npm run dev
  1. Open http://localhost:3000.
  2. Put your studio’s name, title, description and domain in site, and your menu, social links, booking link, e-mail, phone and footer text in the same file, src/content/site.ts.
  3. Replace the images in public/images/ (keep the file names and you are done).
  4. Replace the logo (Making it look like your brand), the browser icons (public/icon-light.png, public/icon-dark.png, src/app/apple-icon.png) and the share image (public/opengraph-image.png).
  5. Edit the page copy in src/content/pages/, and your projects, services, testimonials, posts and legal pages in src/content/collections/. Search for “Catchup”: the demo studio’s name is in the copy, the footer and the legal pages.
  6. Point the inquiry form at your inbox: Forms.
  7. Deploy: Going live.

Nothing else is required: the site has no database, no account to create and no paid service to run.

  • Content is data. All text and every collection item live in src/content/. Pages read the collections through src/lib/content.ts, which is why swapping in a CMS later touches one file, not the whole site.
  • Design is tokens. Colours, breakpoints and easing curves are in src/design-system/theme.css; text styles and motion timings in src/design-system/tokens/. Change a token and every page follows (Making it look like your brand).
  • Components are shared. Every button, card, form field and section is in src/design-system/ or src/components/, and is shown at /style-guide on your own site.
  • Collections feed each other. A project lists its services, a service’s plans show a client from the testimonials, and the footer lists the services, the projects and the legal pages (Editing the content).