Making it yours — Balancee AI Prompts
After the last prompt you have the Balancee 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 “ | Balancee” ending of the browser titles), the home page’s browser title and description, site address | src/content/site.json → site |
| Menu, “Contact us”, the booking link, contact details, social links, the footer (newsletter, columns, copyright and legal links) | src/content/site.json (navigation, contactLink, bookingLink, 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 for Services and Service, portfolio.json, blog.json, contact.json, legal.json, not-found.json) |
| The call to action band, the four-step process, the contact form and the line under it, shown on several pages | src/content/pages/shared.json |
| Services, case studies, posts and legal pages | src/content/collections/<name>.json (services, portfolio, posts, legal) |
Change the text between the quotes and keep the field names. Or ask your tool: “Change the firm’s name to Jane Doe
Advisory and the contact email to hello@janedoe.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 Brooklyn
address are placeholders: replace them.
The firm’s name appears in many places: site.json, the copy of every page, the service and case study texts, the
posts and the legal pages. The logo draws the name too (below). Ask your tool to search src/content/ for “Balancee”
to find them all.
In the footer note, {year} becomes the current year. The phone link dials the + and the digits of contact.phone,
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. “Let’s talk” and “Book a Free Consultation” open bookingLink
(the demo points to https://cal.com/).
The call to action band (every page except Contact and Services) and the process steps come from one copy
(pages/shared.json), so a change shows everywhere. The legal pages are samples with placeholders (“[Your Company
Name]”, “[URL]”): have yours written for your firm.
Services
Section titled “Services”Each service in collections/services.json has slug (its address, /service/<slug>), name, summary (the card’s
text), image (the cover photo, with alt), intro, whatWeDo (title, text and photo), offered (a title and six
items with a title and a text each — they also become the chips on the page’s top) and process (a title, a text, a
photo and four steps). Home shows the first six services, Services all of them in the collection’s order, and the footer
the first four. The contact form offers each service’s name as a choice (see The forms).
Case studies
Section titled “Case studies”Each item in collections/portfolio.json has slug (/portfolio/<slug>), name, headline, summary, image
(the cover), the four facts client, budget, duration and team, and four blocks — overview, challenges,
solutions and results — each with a title, a body and its images (a block with no photos shows none). The
results also have stats, three figures. Home picks its two cards and its four rows by slug in pages/home.json
(caseStudies), and the footer lists the first five.
Posts and legal pages
Section titled “Posts and legal pages”Each post in collections/posts.json has slug (/blog/<slug>), title, excerpt (its search description),
category, date (2024-02-21, shown as “Feb 21, 2024”), image with its alt text (the card’s photo and the page’s
cover), author (name, role, avatar) and body. Home shows the three newest, the Blog page all of them (four at
first, four more as you scroll), and a post page two others of the same category under “Other blogs”.
The bodies of posts, case studies and legal pages are blocks: { "type": "paragraph", "text": "…" },
{ "type": "heading", … } and lists ({ "type": "list", "ordered": false, "items": [[ …blocks ]] }). In any text,
**…** is bold and *italic* is italic. Ask your tool if you prefer: “Add a post called Pricing strategy to
posts.json, with the same fields as the others, in the Business category.”
Photos
Section titled “Photos”The pack uses placeholders; each shows the size its photo is designed for (for example 1920 × 1080). Put your photos
in public/images/ with the same file names and they replace the placeholders:
| Photos | Files |
|---|---|
| Home: the About photo, the process photo, the call to action band’s photo | home-about.jpg, home-process.jpg, home-cta.jpg (and cta-office.jpg for the band on the other pages) |
| The posters of the three videos | home-hero-poster.png, home-about-video-poster.png, home-review-poster.jpg |
| The clients and authors | client-maya-chen.jpg, client-kareem-alvi.jpg, avatar-1.jpg … avatar-3.jpg; a post’s author uses a team member’s photo (team-<name>.jpg) |
| About: the hero figure cards, Who We Are | about-hero-1.jpg, about-hero-2.jpg, about-who-1.jpg … about-who-4.jpg |
| The team | the photo of each member in pages/about.json → team.members |
| Services | service-<slug>.jpg, service-<slug>-what-we-do.jpg, service-<slug>-process.jpg |
| Case studies | portfolio-<slug>-cover.jpg, -overview-1.jpg … -4.jpg, -challenges-1.jpg, -2.jpg, -solutions.jpg, -results.jpg |
| Posts | post-<slug>.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.
Videos
Section titled “Videos”Home plays three muted clips: the hero (a loop), the About clip (plays while it is on screen) and “Watch a review”
(plays on a click) — video.src in pages/home.json (hero, about and the video card of testimonials). The demo
plays 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, and set the poster picture next to it. Keep each file small (a few MB).
Client logos
Section titled “Client logos”The six logos that run past on Home are SVG files, public/images/client-logo-1.svg … client-logo-6.svg, named in
pages/home.json → clients.logos with their names. Replace them with your clients’ logos (SVG, about 144 wide, on a
transparent background).
Logo and icons
Section titled “Logo and icons”The logo is the name drawn as text (Inter, weight 600) in the current text colour, so changing site.name in
site.json and the wordmark text in the Wordmark component changes it. public/images/logo.svg is the same drawing as
a picture for other places. Ask your tool to replace it with your own: “Use public/my-logo.svg as the Logo, at the
same height.” The browser tab icons are public/icon-light.svg (for a light browser theme), public/icon-dark.svg
(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.
Colours, fonts and sizes
Section titled “Colours, fonts and sizes”Prompt 1 set up the design tokens: colours (--color-ink, --color-grey, --color-soft, --color-line,
--color-white, --color-black, --color-error …), the font, text styles and spacing. Balancee is near-black ink on
white and light grey, with black bands for the footer, the testimonial and the timeline: change that set for another
mood — “Change –color-ink to #12263A.” 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 Inter, weight 500 for headings and buttons and 400 for text. 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
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 page title, then the CTA band”) — so it matches the rest.
To remove a section, ask the tool to take it out of the page. Shared blocks (the call to action band, the process steps, the contact form) stay on the other pages.