Making it yours — Catchup AI Prompts
After the last prompt you have the Catchup 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 “ | Catchup” ending of the browser titles), the default title and description, site address | src/content/site.json → site |
| Menu, the header’s Contact button, e-mail and phone, social links, booking link, the footer (its text, button, columns and note) | src/content/site.json (navigation, headerAction, contact, socials, bookingHref, footer) |
| The copy of each page, with its browser title and description | src/content/pages/<page>.json (home.json, about.json, blog.json, contact.json, not-found.json, …) |
| The words every project page shares (“Introduction”, “Details”, “The Challenge” …) | workItemPage in pages/work.json |
| The words every service page shares (“What We Offer”, “Pricing Options”, “Per Project”, “Per Month” …) | serviceItemPage in pages/services.json |
| The words every post shares (“Posted at”, “More Blog”) and every legal page (“Last updated:”) | pages/post.json, pages/legal.json |
| The contact page (address, hours) and its form | pages/contact.json |
| Works, services, testimonials, 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 e-mail to
hello@mystudio.com and the phone to +1 555 010 2030 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) and phone number are
placeholders: replace them. “Book a 15-min call” in the footer and on every service page opens https://cal.com/
(footer.action and bookingHref in site.json): put your own booking page there (Cal.com, Calendly) or /contact.
In the footer note, {year} becomes the current year. The phone link dials the digits of contact.phone
(+1 (347) 555-0123 calls tel:+13475550123), so write the number the way people should read it. The social links,
the team’s Instagram handles and the award links open the networks’ or the awards’ home pages: point them to your own.
The numbers that count up appear twice: on Home (about in pages/home.json) and on About (philosophy.stats in
pages/about.json). Each has a start, a value and a suffix; change them in both places.
Each work in collections/work.json has:
slug— its address (/work/liva-beauty-skincare), unique;title,client(its name in the footer’s Recent Works) andsummary— on its card, in Home’s hero and at the top of its page (the summary is also the page’s search description);image— the main photo;logo— the client’s logo (/images/logo-liva.svg), in Home’s logo ticker and on the project page’s photo;services— the slugs of its services (["branding", "photography"]), shown as tags and links;year,timelineandcredits(role and name) — the tables at the top of its page;challenge,solutionandoutcome— a title, a text and agalleryeach (two photos, three photos, none).
The client’s words under The Outcome come from the testimonial whose work is this work’s slug. The order of the
file is the order on the site: Home’s hero, the Work page and the footer show them all, and a project page shows the
first two others under “Other works”. To add a work, copy one, give it a new slug and change the fields; it gets its
own page and appears in the lists and the sitemap.
Services and their prices
Section titled “Services and their prices”Each service in collections/services.json has slug (/service/branding), name, summary (on its card),
thumbnail (the square card photo) and image (the wide photo of the Services page and its own page), then:
overview— the title and text at the top of its page (the text is also its search description);offer— the “What We Offer” title and text andincludes, the deliverables (the Services page shows the first four);pricing— atitleand two plans,projectandmonthly, each with aprice(text, such as"$2,500+"), fourincludes, threenotesand atestimonial: theslugof the client shown beside that plan.
Every service page lists the other services under “More Services”, and the footer lists them all.
Testimonials, posts and legal pages
Section titled “Testimonials, posts and legal pages”- Testimonials (
collections/testimonials.json):slug,name,role,photo(a small square portrait),rating(out of 5),quoteand, for a work’s client,work. Home shows all ten (the faces in the About block and the quotes in two moving rows, or a carousel on tablets and phones); About shows the first four faces. - Posts (
collections/posts.json):slug,title,category,date(2025-05-30, shown as “May 30, 2025”),excerpt,imageandcontent. Keep them newest first: Home shows the first three, the Blog page all of them (more as you scroll), and a post shows up to two others of the same category. - Legal pages (
collections/legal.json):slug,title,dateandcontent; the footer and the contact form’s note link to them. Replace the demo’s Privacy Policy and Terms of Service with your own texts.
A post’s and a legal page’s content is a list of blocks: { "type": "paragraph", "text": "…" },
{ "type": "heading", "level": 3, "text": "…" } and lists. In any text, **…** is bold, *…* is italic,
[label](/address) is a link and \n starts a new line. Ask your tool if you prefer: “Add a post called Our New
Studio to posts.json, with the same fields as the others, in the Branding category.”
Photos
Section titled “Photos”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 numbers cards, the services call to action, the closing photo | home-stat-brands.jpg, home-stat-engagement.jpg, home-stat-projects.jpg, home-services-cta.jpg, home-services-cta-side.jpg, home-cta.jpg |
| About: the title photo, the philosophy photos, the awards and the team | about-hero.jpg, about-side.jpg, about-wide.png, about-awards-1.jpg, about-awards-2.jpg, team-<name>.jpg |
| Testimonials: the client portraits | client-<name>.jpg |
| Works | work-<client>.jpg and work-<client>-challenge-1.jpg … -solution-3.jpg |
| Services | service-<slug>.jpg, service-<slug>-thumb.jpg and service-offer.png (the square on every service page) |
| Posts | post-<start of the title>.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.
Logo and icons
Section titled “Logo and icons”The Catchup logo is drawn inline by the Logo component (prompt 2 has its drawing) in the header, the footer, Home’s
intro, the years card and the closing photo, and on About’s wide photo. Ask your tool to replace it with your own SVG:
“Use public/my-logo.svg in the Logo component, at the same sizes.” The client logos are public/images/logo-*.svg.
The browser tab icons are public/icon-light.png (black, for a light browser theme), public/icon-dark.png (white,
for a dark theme), both 180 × 180, and public/apple-icon.png (200 × 200); the share image is
public/opengraph-image.png (1200 × 630, made by the last prompt): replace them.
Colours, fonts and sizes
Section titled “Colours, fonts and sizes”Prompt 1 set up the design tokens: colours (--color-ink, --color-body, --color-accent — the mint of the buttons
and discs —, --color-orange, --color-page, --color-white and the black and white tints), the font, text styles
and spacing. Change the accent for another mood — “Change –color-accent to #C9F25B.” — and keep enough contrast
with the black text on it. Keep the text styles’ sizes per breakpoint unless you want a different rhythm.
The font is Manrope: 400 for text, 500 for the smaller headings, the numbers and the buttons, 600 for the big titles.
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), the footer’s
Sitemap, 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 page-title block, then Service cards in three columns”) — so it
matches the rest.
To remove a section, ask the tool to take it out of the page.