Skip to content
Sign inJoin waitlist

Cerette documentation — Next.js

Everything you need to take Cerette 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, the video, projects, services, testimonials, the team, 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 forms 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, 32 addresses:
    • Home, About, Projects, Services, Blog, Contact and the 404 page;
    • a page for each of the 6 projects, the 6 services, the 12 posts and the 2 legal pages, built from the collections (Pages and sections).
  • 6 collections in src/content/collections/: projects (projects.ts, 6), services (services.ts, 6), testimonials (testimonials.ts, 6), the team (team.ts, 12), posts (posts.ts, 12) and legal pages (legal.ts, 2).
  • 1 inquiry form in two versions: on Contact and Services the project type is a list of choices; on a service’s page it starts with the service’s name. A server action each and four ways to deliver them (a log, a webhook, Mailchimp, Resend).
  • A fixed header on every page (see-through over the Home video, a project’s cover photo and the 404 photo, then in the page colour), with a phone menu.
  • Motion in the components, with reduced-motion support: the Home hero’s letter-by-letter title, the word-by-word titles of About and Projects, blocks rising into view, the services switcher and the team picker; 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, a browser icon, 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 demo’s hero video is not included either: it is streamed from another server, so use your own (Editing the content). The logo is drawn for the template.
  • These docs (docs/), the forms guide (Forms reference), the design system’s reference (Cerette 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, phone, e-mail, address 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), and the Home hero’s video (home.hero.video in src/content/pages/home.ts).
  4. Replace the logo (Making it look like your brand), the browser icons (public/icon.svg, 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, team, posts and legal pages in src/content/collections/. Search for “Cerette”: 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 and links to their pages, and the footer lists the services and the legal pages (Editing the content).