Skip to content
Sign inJoin waitlist

Balancee documentation — Next.js

Everything you need to take Balancee 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, videos, services, case studies and posts, the timeline, the awards and the team — no CMS needed
Making it look like your brand Colours, the wordmark and the “B” icon, fonts, text styles, spacing, motion, components, the style guide
Pages and sections The header, the sections of every page with a map of each, the 33 addresses, adding, removing and reordering pages and sections
Forms Making the contact form and the newsletter box 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, 33 addresses:
    • Home, About, Services, Portfolio, Blog, Contact and the 404 page;
    • a page for each of the 8 services, the 8 case studies, the 9 blog posts and the 2 legal pages (Terms of Service, Privacy Policy), built from the collections (Pages and sections).
  • 4 collections in src/content/collections/: services (services.ts, 8), case studies (portfolio.ts, 8), posts (posts.ts, 9) and legal pages (legal.ts, 2).
  • 2 forms: the contact form (“Tell us about your project.”) on Contact and on the Services page, and the newsletter box in the footer of every page, each with a server action and four ways to deliver it (a log, a webhook, Mailchimp, Resend).
  • Page copy for the timeline, the awards and the team of About, the client logos, the testimonials and the closing call to action band, shared by several pages.
  • A fixed header with the menu and the “Contact us” button, and a phone menu.
  • Hover motion in the components, with reduced-motion support, 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 three videos play stock clips from the Pexels website: replace them with your own (Editing the content).
  • These docs (docs/), the forms guide (Forms reference), the design system’s reference (Balancee design system), CHANGELOG.md and LICENSE.md.
Terminal window
npm install
npm run dev
  1. Open http://localhost:3000.
  2. Put your company’s name, title, description and domain in site, and your menu, contact details, social links and footer 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 three videos (Editing the content).
  4. Replace the wordmark (Making it look like your brand), the browser icons (public/icon-light.svg, public/icon-dark.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 services, case studies, posts and legal pages in src/content/collections/. Search for “Balancee”, the team members’ names (they are also the posts’ authors) and “Brooklyn”: the demo’s company, people and address are named in many places. The legal pages say [Your Company Name] and [URL] where yours go.
  6. Point the contact 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 springs 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.
  • Blocks are shared too. The call to action band, “How we work” and the contact form appear on several pages from one copy each (Pages and sections).