Skip to content
Sign inJoin waitlist

Making it yours — Tustel AI Prompts

After the last prompt you have the Tustel 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, owner (the logo link’s name), the home page’s browser title and description, site address src/content/site.json → site
Menu, the “Book a call” and “View my works” links, contact details, social links, the footer note src/content/site.json (navigation, bookCall, viewWorks, contact, socials, footer)
Sections several pages share: the photo band, Let’s work together, From the journal, the four counters src/content/site.json (band, workTogether, journal, facts)
The copy of each page, with its browser title and description src/content/pages/<page>.json (home.json, about.json, …)
Projects, services, testimonials, posts, clients src/content/collections/<name>.json

Change the text between the quotes and keep the field names. Or ask your tool: “Change the owner’s name to Jamie Rowe and the contact email to hello@jamierowe.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 location are placeholders: replace them all. “Book a call” (bookCall.href) opens https://cal.com/: put your own booking page there (Cal.com, Calendly) or /contact.

Your name appears in more places than site.owner: the footer note, the hero name in pages/home.json and pages/about.json, the page descriptions (meta.description in about.json, portfolio.json and blog.json, contactPage.meta.description in contact.json), the descriptions of the two “About me” photos on Home and the testimonial quotes (“Working with Alex…”). The logo draws it too (below). Ask your tool to search src/content/ for “Alex” to find them all.

In the footer note, {year} becomes the current year. The phone link dials the digits of contact.phone (+1 (415) 123-4567 calls tel:+14151234567), so write the number the way people should read it. The browser titles of the other pages end in “ | Tustel”: if yours still do after you rename the site, ask your tool to build them from site.name.

A counter in facts counts up from from to value when it scrolls into view, then shows suffix after it ("+", or "" for none). Write whole numbers, and keep the distance between from and value to a few hundred: the counter steps by one every 5 ms.

Each project in collections/projects.json has:

  • slug — its address (/portfolio/aurora-coffee), unique; title and summary (the List view on Home and the page’s search description);
  • image — the cover: the cards and the wide photo under the title, at the photo’s own proportions;
  • client, category (any words, also on the cards), year and timeline — the details under the title; industry, deliverables, timeline and scope — the “Project Details” list;
  • description and challenge — the paragraphs of “Project Description” and “The Challenge”, one string each;
  • gallery and challengeGallery — the photos after the details and after the challenge: two columns, the first half of the photos on the left, each at its own proportions. The demo’s galleries have three or four photos.

The order of the file is the order on the site. Home shows the first six projects (four on tablets and phones), the Portfolio page shows them all, six at a time as you scroll (four on tablets and phones), and a project page lists the first six others under “Other Projects”. 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. The words every project page shares (“Client”, “Project Description”, “Other Projects” …) are in pages/project.json.

  • Services (collections/services.json): slug (an id: services have no page), name (the numbered row, “01 — Photography”), title and summary (shown for the chosen service) and image (shown 300 × 200). Home lists them all, numbered in the file’s order. When your services change, change the contact form’s Project Type choices too (contactForm.fields.project.options in pages/contact.json).
  • Testimonials (collections/testimonials.json): slug (an id), name, role (“Founder, Aurora Coffee”), photo (a round portrait) and quote. The slideshow on Home shows them all, one at a time.
  • Posts (collections/posts.json): slug, title, excerpt, image, category (any words), date (2025-04-16, shown as “Apr 16, 2025”) and the article body as blocks (see below). The Blog shows six at a time as you scroll (four on tablets and phones); Home shows the first three, and every post the first three others. Posts are listed in the file’s order, not by date: put a new post first to show it first.
  • Clients (collections/clients.json): name and logo (an SVG, shown 25 px tall at its own width). Their logos move across Home under the hero; the name is the logo’s text for screen readers.

Blocks are { "type": "paragraph", "text": "…" }, { "type": "heading", "text": "…" } (one size) and { "type": "list", "items": [[…], …] }: a bulleted list whose items are lists of blocks ("ordered": true numbers it). In any text, *words* are italic and \n starts a new line. Ask your tool if you prefer: “Add a post about lighting a portrait session to posts.json, with the same fields as the others.”

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

  • hero-1.jpg … hero-3.jpg (the Home slideshow), home-about-1.jpg and home-about-2.jpg (About me on Home), band.jpg (the photo band), contact-cta.jpg (Let’s work together), about-process.jpg (How I work) and not-found.jpg;
  • portrait-alex-carter.jpg — your portrait, in the card of the Home hero and in the About hero;
  • project-<slug>.jpg (the cover) and project-<slug>-1.jpg, -2.jpg … (the galleries), service-<slug>.jpg, post-<slug>.jpg and person-<slug>.jpg (the testimonial portraits).

Project covers and gallery photos keep their own proportions: a tall photo makes a tall card, and the cards of a row line up at the top. Other 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>.

The client logos are SVG files in public/images/ (client-liva.svg …): replace them with your clients’ logos, or remove the clients you don’t want.

In a chat builder, upload the photos and tell the tool which file names to give them.

The logo — the AC monogram in a ring, the name and a small ® mark — is public/images/logo.svg (black: the solid header and the footer) and public/images/logo-white.svg (white: over the Home and 404 photos), 104 × 24; depending on your tool, the Logo component shows these files or draws the same paths inline. Ask your tool to replace it with your own SVG: “Use public/my-logo.svg as the Logo, black on the light backgrounds and white over the photos.” The browser tab icon is public/icon.svg (the monogram, white in a dark browser theme) and the share image public/opengraph-image.png (1200 × 630, made by the last prompt): replace both.

Prompt 1 set up the design tokens: colours (--color-ink, --color-soft, --color-orange, --color-background, --color-white and the black tints --color-ink60, --color-ink30, --color-ink10), the font, text styles and spacing. Orange is the accent of every hover — the band that rises in the buttons, the fill behind the menu links, the underline of the social links — and of the chosen service, the active title in the List view and the required-field asterisks, so changing it gives the site your brand colour: “Change –color-orange to #1F6FEB.” It carries white text in the hovers and shows as text on the light background, so pick a colour that reads on both. Keep the text styles’ sizes per breakpoint unless you want a different rhythm.

The font is Inter, weights 400 and 500, with its optical-size axis: the headings use its Display 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 sitemap and the buttons that lead to it (“More about me” goes to About, “View my works” to the Portfolio, “View all articles” to the Blog). To add one, write a prompt in the style of the page prompts — list its sections and reuse the components (“a Page title, then Project cards in three columns”) — so it matches the rest; it gets the solid header that hides as you scroll down.

To remove a section, ask the tool to take it out of the page. On Home, the client logos also tell the solid header when to fade in as you scroll back up: if you remove them, ask the tool to tie it to the section under the hero instead.