Skip to content
Sign inJoin waitlist

Making it yours — Metuo AI Prompts

After the last prompt you have the Metuo site with its demo text and grey placeholder photos. Everything a visitor reads lives in src/content/, so most changes are edits to text files — or a sentence to your AI tool.

What Where
Site name (the logo link’s name and the “ | Metuo” ending of the browser titles), the home page’s browser title and description, site address src/content/site.json → site
Menu, “Book a session”, contact details, social links, the footer (its photo, line, columns, copyright and legal links) src/content/site.json (navigation, bookLink, contact, socials, footer)
The copy of each page, with its browser title and description src/content/pages/<page>.json (home.json, about.json, service.json, testimonial.json, blog.json, contact.json, not-found.json)
The words every post page and every legal page shares pages/post.json (“More insights for you.”), pages/legal.json (“Last Updated:” and each legal page’s description)
The founder, her quote, the call to action band, the client ratings and the e-mail line, shown on several pages src/content/pages/shared.json
The plans, the questions and the booking form, shown on several pages pages/pricing.json, pages/faq.json, pages/book.json
Services, client stories, team, posts and legal pages src/content/collections/<name>.json

Change the text between the quotes and keep the field names. Or ask your tool: “Change the practice’s name to Jane Doe Coaching and the contact email to hello@janedoecoaching.com in site.json.” Set site.url to your domain before you publish — the sitemap and share links are built from it. The demo’s e-mail (hello@example.com), phone number and London address are placeholders: replace them; the e-mail also appears in the “send us an email” line (questionLine in pages/shared.json) and the questions’ “Contact support” button (support.cta in pages/faq.json).

The practice’s name, its founder and its city appear in many places: site.json, the copy of every page, the founder (pages/shared.json), the client stories and the legal pages. The logo draws the name too (below). Ask your tool to search src/content/ for “Metuo”, “Amelia” and “London” to find them all.

In the footer note, {year} becomes the current year. The phone link dials the digits of contact.phone ((555) 123-4567 calls tel:5551234567), so write the number the way people should read it. The social links open the networks’ home pages: point them to your own profiles, and remove the ones you don’t use.

Some blocks appear on more than one page from one copy: the founder quote (Home, About, Service), the call to action band (Home, About, Testimonial, Blog), the plans and the questions (Home, Service; the questions also on Contact and every post) and the booking form (Home, Service, Contact). The four figures are written twice: stats in pages/home.json and facts in pages/service.json — change them in both. They are plain text and never count up.

Each service in collections/services.json has slug, name, summary, values (the four dotted points), image and images (the big photo and the two small ones) and imageAlts (their descriptions, in that order). Home shows the first four as rows that open one at a time; the Service page shows all of them as cards, numbered 01, 02 … in their order; the booking form offers every service’s name as a session type.

pages/pricing.json holds the three plans: name, description, monthly and yearly (the prices, any text), includes (the dotted list), perfectFor, the button and featured: true for the dark Green middle card. The switch’s words and “(32% off)” are in billing: change the discount when your prices change. The layout is made for three plans.

  • Client stories (collections/testimonials.json): headline, quote, outcomes (three points), name, role, photo (a small portrait) and image (the big photo) with imageAlt. Home’s pinned card turns through the first four; the Testimonial page stacks all of them.
  • Team (collections/team.json): name, role, photo (2 : 3) and bio (shown by the card’s “+”).
  • Questions (items in pages/faq.json): question and answer; the first starts open. support is the “Still have questions?” card with its person and button.

Each post in collections/posts.json has slug (its address, /blog/<slug>), title, excerpt (its search description), category, date (2026-05-28, shown as “May 28, 2026”), image with imageAlt (the card’s photo and the page’s cover) and body. Home shows the three newest, the Blog page all of them (six at first, six more as you scroll), and a post page up to three others of the same category under “More insights for you.”.

The bodies of posts and legal pages are blocks: { "type": "paragraph", "text": "…" }, { "type": "heading", … } and lists. In any text, **…** is bold and *…* is italic. The legal pages are samples with placeholders (“[Your Company Name]”, “[URL]”): have yours written for your practice. Ask your tool if you prefer: “Add a post called Sleep and stress to posts.json, with the same fields as the others, in the Growth category.”

The pack uses placeholders; each shows the size its photo is designed for (for example 2400 × 1600). Put your photos in public/images/ with the same file names and they replace the placeholders:

Photos Files
Home: the hero, “About us” (the small photo and the founder card), “Why choose us”, “Our process” home-hero.jpg, home-about-1.jpg, home-about-2.jpg, why-1.jpg … why-4.jpg, step.jpg, step-background.jpg
The founder: her portrait and the quote’s background founder.png, founder-background.jpg
About: the photo title, Vision & Mission, the five values about-hero.jpg, about-mission.jpg, about-mission-background.jpg, about-value-1.jpg … about-value-5.jpg
The photo titles of Service, Testimonial and Blog service-hero.jpg, testimonial-hero.jpg, blog-hero.jpg
The client ratings, the questions’ support person, the client stories avatar-1.png … avatar-4.png, client-avatar.png, client-<name>.png, story-<name>.jpg
Services, team, posts service-<slug>.jpg and service-<slug>-1.jpg, -2.jpg; team-<name>.jpg; post-<slug>.jpg
The footer’s background footer.jpg

Photos fill their frame and are cropped, so keep their proportions close to the placeholder’s. A new photo can have any name: refer to it in the content as /images/<file>, with its alt text. In a chat builder, upload the photos and tell the tool which file names to give them.

Home and About each play a muted, looping video that grows into place as you scroll (video.src in pages/home.json and pages/about.json). The demo plays two stock clips from the Pexels website by their address; they are not part of the download and stop working if Pexels moves them, so replace them: put an MP4 in public/videos/ and set "src": "/videos/home.mp4", or use an address of your own. The frame is 16 : 9; export at about 1280 px wide and keep each file small (a few MB).

The logo — the Metuo leaf and wordmark — is drawn from public/images/logo-white.svg (372 × 100, shown 92 × 25) in the colour of the text around it: White over photos, Green on the light header and in the footer. public/images/logo.png is a Green copy for use elsewhere. Ask your tool to replace it with your own SVG: “Use public/my-logo.svg as the Logo, at the same height, in the current text colour.” The social icons are SVG files (public/images/icon-facebook.svg, …) named in socials. The browser tab icons are public/icon-light.svg (Green, for a light browser theme), public/icon-dark.svg (light, for a dark theme) and public/apple-icon.png (180 × 180), and the share image is public/opengraph-image.png (1200 × 630, made by the last prompt): replace them.

Prompt 1 set up the design tokens: colours (--color-green, --color-background, --color-white, --color-grey, --color-soft-grey, --color-orange, --color-brown, the black tints, --color-error …), the font, text styles and spacing. Metuo is dark green on a warm off-white page (--color-background, #FCFBF6), with Orange for hovers: change that set for another mood — “Change –color-green to #23324A.” Keep enough contrast between the text and the page. Keep the text styles’ sizes per breakpoint unless you want a different rhythm.

The font is Manrope, weight 500 for headings, 400 for text and 600 for buttons, with a slightly tight letter spacing (−0.03em). Another font works the same way — ask the tool to load it and use it in --font-sans.

To remove a page, delete it and ask your tool to take it out of the menu (navigation in site.json, which is also the footer’s Quick links), the sitemap and the buttons that lead to it. To add a page, write a prompt in the style of the page prompts — list its sections and reuse the components (“the photo title, then the FAQ section”) — so it matches the rest.

To remove a section, ask the tool to take it out of the page. Shared blocks (the founder quote, the call to action band, the plans, the questions, the booking form) stay on the other pages.