Metuo documentation — Astro
Everything you need to take Metuo 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, videos, services, stories, 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 booking 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 |
What is in the package
Section titled “What is in the package”- 9 kinds of page, 20 addresses:
- Home, About, Services, Client Stories, Journal, Contact and the 404 page;
- a page for each of the 12 journal posts and the 2 legal pages, built from the collections (Pages and sections).
- 5 collections in
src/content/collections/: the services (6), the client stories (6), the team (6), the posts (12) and the legal pages (2). - 1 form: the booking form (“Tell us about you.”) on Home, Services and Contact. 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).
- Coaching plans with a Monthly / Yearly switch, six questions that open one by one, numbered steps, service rows that open one at a time and team cards with a bio behind a “+”.
- A fixed header that runs transparent over the big photo of five pages and turns solid as you scroll, and a menu that grows from the bar on phones.
- Motion in the components (the Home hero’s photo and words on load, the parallax of the page photos, the pinned client
stories, the points that light up, the videos growing into place, 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, icons for light and
dark browser themes,
sitemap.xmlandrobots.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 two videos play from the Pexels website: replace them (Editing the content). The logo is drawn for the template. - These docs (
docs/), the forms guide (Forms reference), the design system’s reference (Metuo design system),CHANGELOG.mdandLICENSE.md.
In a hurry: the first 15 minutes
Section titled “In a hurry: the first 15 minutes”npm installnpm run dev- Open http://localhost:4321.
- 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. - Replace the photos in
src/assets/images/(keep the file names and you are done) and write analtfor each in the content (Editing the content); put your own videos inpublic/and their paths invideo.src(Editing the content). - Replace the logo (Making it look like your brand), the browser icons in
public/(icon-light.svg,icon-dark.svg,apple-icon.png) and the share image (public/opengraph-image.png). - Edit the page copy in
src/content/pages/, and your services, stories, team, posts and legal pages insrc/content/collections/. Search for “Amelia” and “hello@example.com”: the demo’s founder and e-mail are named in several places (Editing the content). - Point the booking form at your inbox: Forms.
- Deploy: Going live.
Nothing else is required: the site has no database, no account to create and no paid service to run.
How this template is put together
Section titled “How this template is put together”- Content is data. All text and every collection item live in
src/content/, as JSON. Pages read the collections throughsrc/lib/content.ts, andsrc/content.config.tssays 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 insrc/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/orsrc/components/, and is shown at/style-guideon your own site. - Many blocks repeat. The founder quote, the call to action band, the plans, the questions and the booking section
appear on several pages, each from one file in
src/content/pages/; 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 insrc/components/site/) whoseinit*()function the component’s<script>calls, and hovers aredata-hover/data-motionattributes played byscripts/hover.ts(Making it look like your brand).
Getting help
Section titled “Getting help”- Your licence terms: License.
- What changed in each release: Changelog.
- Support and updates: https://framebrick.co/support.
- Want it done for you? Marcframe, the studio behind this template, updates templates to your needs, builds custom templates and designs new sites. It’s also on Contra.