Making it yours — Lookis AI Prompts
After the last prompt you have the Lookis 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 “ | Lookis” ending of the browser titles), the home page’s browser title and description, site address | src/content/site.json → site |
| Menu, the photographer’s name, city and time zone (the header clock), contact details, social links, booking link, the footer (its photo, text, button, columns and note) | src/content/site.json (navigation, owner, contact, socials, bookingHref, footer) |
| The copy of each page, with its browser title and description | src/content/pages/<page>.json (home.json, about.json, …) |
| The words every project page and every service page shares | projectPage in pages/portfolio.json, servicePage in pages/services.json |
| The testimonials and the “See what I do” band with its gallery, shown on several pages | src/content/pages/shared.json |
| The contact page and its form | pages/contact.json |
| Projects and services | src/content/collections/<name>.json |
Change the text between the quotes and keep the field names. Or ask your tool: “Change the photographer’s name to Jane
Doe and the contact email to hello@janedoe.photo 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 session” in the hero, “Schedule a call” in the footer and the button of every service page open
https://cal.com/ (hero.primary in pages/home.json, footer.action and bookingHref in site.json): put your
own booking page there (Cal.com, Calendly) or /contact.
The photographer’s name appears in more places than owner.name: the hero’s ticker and introduction, the About and
Contact pages, the footer note, the testimonials and the gallery’s Instagram button. The logo draws it too (below). Ask
your tool to search src/content/ for “Daniel Mercer” (and “Asheville”) 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, the
gallery’s Instagram link and the award links open the networks’ or the awards’ home pages: point them to your own.
Some blocks appear on more than one page. The testimonials and “See what I do” have one copy in pages/shared.json;
the four numbers have one copy in pages/home.json and one in pages/about.json: change them in both.
The header clock
Section titled “The header clock”On desktops the header shows owner.place (“Asheville, (NC)”) and the local time there, from owner.timeZone
(America/New_York). Write your city and its time zone name from the
list of time zones (Europe/Lisbon,
Asia/Jakarta …).
Projects
Section titled “Projects”Each project in collections/portfolio.json has:
slug— its address (/portfolio/quiet-light), unique;titleandsummary— on its card and at the top of its page (the summary is also the page’s search description);date—2024-03-18, shown as “Mar 18, 2024”;service— theslugof its service (portrait-sessions), which puts it under that tab of the Portfolio page and among the related projects of the same service;details— the story under “Overview”, as blocks (below);image— the main photo (a 4 : 5 portrait works best);gallery— the five photos under “Project Gallery”.
The order of the file is the order on the site: Home shows the first six, the Portfolio page all of them (four at
first, more as you scroll), a project page up to three others of the same service. Projects are listed in the file’s
order, not by date: the demo keeps them newest first, so put a new project first to show it first. To add a project,
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
Section titled “Services”Each service in collections/services.json has slug (/services/portrait-sessions), name, summary (the short
description, the title of its page), price (text, such as "$350 – $600"), image, content (the paragraphs of its
page, as blocks), perfectFor and included (the two numbered lists). Home shows them all as rows with their photo,
the Services page as cards, and every service page lists the others under “Other Services”. The Portfolio page makes a
tab for each service, after “All”.
Blocks are { "type": "paragraph", "text": "…" }. In any text, **…** is bold, *…* is italic and \n starts a new
line. Ask your tool if you prefer: “Add a project called Coastal Light to portfolio.json, with the same fields as the
others, under Travel & Documentary.”
Testimonials, questions and awards
Section titled “Testimonials, questions and awards”- Testimonials (
testimonials.itemsinpages/shared.json):quote,name,roleandphoto(a small square portrait). They move on one at a time on Home, Services and every service page. - Questions (
servicesPage.questions.itemsinpages/services.json):questionandanswer, numbered 01, 02 … in their order. - Awards (
awards.itemsinpages/about.json):year,title,byandhref(opens in a new tab); the photo among them comes after the award thatawards.imageAfternames.
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 hero (also the footer’s background and the Contact portrait), About (four photos, shared with the About page), the numbers | hero.jpg, about-1.jpg … about-4.jpg, facts.jpg (also the Services page photo) |
| About: the portrait and the awards photo | about-avatar.png, about-story.jpg |
| Testimonials: the background and the client portraits | testimonials.jpg, client-elena.jpg, client-mia-jordan.jpg, client-liam.jpg, client-sarah.jpg |
| The “See what I do” gallery | gallery-1.jpg … gallery-5.jpg |
| Contact, 404 | contact.jpg, not-found.jpg |
| Projects and services | portfolio-<slug>.jpg and portfolio-<slug>-1.jpg … -5.jpg, service-<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.
Logo and icons
Section titled “Logo and icons”The logo — the “Daniel Mercer” wordmark on two lines — is public/images/logo.svg (330 × 162, shown 72 × 35 on desktops
and tablets, 62 × 30 on phones); depending on your tool, the Logo component shows this file or draws the same path
inline. Ask your tool to replace it with your own SVG: “Use public/my-logo.svg as the Logo, at the same height.” The
browser tab icons are public/icon-light.png (black, for a light browser theme), public/icon-dark.png (white, for a
dark theme) and public/apple-icon.png, all 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, the black tints --color-ink80 … --color-ink02,
--color-line, --color-paper, --color-spinner, --color-error), the font, text styles and spacing. Lookis is black
on an off-white page (--color-paper, #FAFAFA): change that pair for another mood — “Change –color-paper to #F4F1EA.”
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 400 (500 for the hero’s big name and the clock, 700 for bold text), with its optical-size axis
set to the text cut. Another font works the same way — ask the tool to load it and use it in --font-sans; a font
without an optical-size axis simply ignores that setting.
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 two-column page shell, then a Question list”) — so it matches the
rest.
To remove a section, ask the tool to take it out of the page. “See what I do” and the testimonials are shared: removing them from one page leaves them on the others.