Skip to content
Sign inJoin waitlist

Overview — Compose Digi

Everything you need to take Compose for Astro 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, services, projects, posts and job openings — no CMS needed
Making it look like your brand Colours, the logo, fonts, text styles, spacing, motion, the custom cursor, 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 contact 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
  • 12 kinds of page, 47 addresses in the sitemap:
    • Home, About, Services, Projects, Careers, Blog, Contact and the 404 page;
    • a page for each of the 8 services, the 8 projects, the 12 blog posts and the 12 job openings, built from the collections (Pages and sections).
  • 4 collections in src/content/collections/: the services (8, each with a Weekly and a Monthly plan), the projects (8 case studies, each with a client testimonial), the posts (12) and the job openings (12).
  • 1 form: the contact form (“Send message”) on the Contact page. It runs in demo mode until you give it a destination: a form service or webhook on any static host, or the site’s own route with four ways to deliver (a log, a webhook, Mailchimp, Resend).
  • A plan card on every service page with a Weekly / Monthly switch, service rows on Home that open one at a time, a testimonial slider and a process chart on Services, a video window on About, and Load More on Projects, Blog and Careers.
  • A sticky header with a pill of links, and a menu that grows from the bar on phones.
  • Motion in the components (the project ticker of the Home hero, the footer’s services ticker, the client logos, the rolling button labels, the custom cursor that turns into “View Project”, “Read” or “More Details”, the project pages’ scroll effects, the parallax of the Services call to action, the hovers), 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, the browser and home screen icons, sitemap.xml and robots.txt.
  • Placeholders: the photos in src/assets/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 client logos of About are sample logos, and the About video plays the original Framer template’s promo from YouTube: replace both (Editing the content).
  • These docs (docs/), the forms guide (Forms reference), the design system’s reference (Compose Digi design system (Astro)), CHANGELOG.md and LICENSE.md.
Terminal window
npm install
npm run dev
  1. Open http://localhost:4321.
  2. Put your name, title, description and domain in src/content/site.json, and your menu, contact details (e-mail, phone, address) and footer in the same file.
  3. Replace the photos in src/assets/images/ (keep the file names and you are done) and write an alt for each in the content (Editing the content); put the id of your own YouTube video in video.youtubeId in src/content/pages/about.json (Editing the content).
  4. Replace the logo (Making it look like your brand), the browser icons in public/ (icon.svg, apple-icon.png) and the share image (public/opengraph-image.png).
  5. Edit the page copy in src/content/pages/, and your services, projects, posts and job openings in src/content/collections/. Search for “example.com”, “cal.com” and “Compose”: the demo’s e-mails, booking link and name are written in several places (Editing the content).
  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/, as JSON. Pages read the collections through src/lib/content.ts, and src/content.config.ts says where each collection comes from, 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.
  • Some blocks repeat. The page header (label, title, lead, social buttons, “Scroll to Explore”) is one section used by About, Services, every service, Projects and Blog, each with its own copy; the invitation box under the project lists and a few other blocks have a copy in each page’s file (Pages and sections).
  • No framework in the browser. The pages are static HTML. Each interactive part has a small TypeScript script in src/design-system/scripts/ (the header’s is in src/components/site/) whose init*() function the component’s <script> calls, and hovers are data-hover / data-motion attributes played by scripts/hover.ts (Making it look like your brand).