Skip to content
Sign inJoin waitlist

Semono documentation — Astro

Everything you need to take Semono 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 two videos, services, testimonials, posts, careers, legal pages, the team and client logos — no CMS needed
Making it look like your brand Colours, the logo, fonts, text styles, spacing, motion and the page change, 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 three 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
  • 13 kinds of page, 33 addresses:
    • Home, About, Team, Careers, Services, Testimonial, Blog, Contact and the 404 page;
    • a page for each of the 5 positions, 6 services, 12 posts and 2 legal pages, built from the collections;
    • Services and Careers live at /service and /career, in the singular (Pages and sections).
  • 7 collections in src/content/collections/: services (6), testimonials (7), posts (12), careers (5), legal pages (2), the team (6) and client logos (10).
  • 3 forms: the inquiry on Contact, a consultation form on every service page and an application form on every career page. They run in demo mode until you give them 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).
  • 2 videos: play-on-click cards on Home and About. The demo’s clips are Pexels stock videos played from Pexels’ servers; the package carries no video.
  • A fixed header that never hides: over the photo on Home, turning light at the “About Semono” block, under a spacer on every other page; and a page change, a slide between pages, that switches itself off for visitors who ask their system for less motion.
  • 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, 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, which can’t be sold with a template). The logo and the sample client logos are drawn for the template.
  • These docs (docs/), the forms guide (Forms reference), the design system’s reference (Semono design system), 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, footer and social links in the same file.
  3. Replace the images in src/assets/images/ (keep the file names and you are done), including the portraits and the client logos, and the two videos (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, testimonials, posts, careers, legal pages, team and clients in src/content/collections/. Search for “Semono”: the demo’s firm is named in many places.
  6. Point the three forms 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 closing call to action, the figures, the process steps and the headings of the client cards appear on several pages; each page’s file holds its own copy, so change it in each (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 src/components/site/header.ts) 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).