Skip to content
Sign inJoin waitlist

Making it yours — Kendi AI Prompts

After the last prompt you have the Kendi 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
Magazine name (the logo link’s name and the “ | Kendi” ending of the browser titles), the home page’s browser title and description, site address src/content/site.json → site
Menu, the header’s “Contact us”, the Categories menu, contact details, social links, the sidebar’s blocks, the newsletter band, the footer (its text, link columns, copyright and legal links), the screen-reader names of the controls src/content/site.json (navigation, headerAction, categoriesMenu, contact, socials, sidebar, newsletter, footer, controls)
The sponsored ad (Home and every post) src/content/site.json → sponsoredAd
The copy of each page, with its browser title and description src/content/pages/<page>.json (home.json, about.json, …)
The words every post, category, author and legal page shares pages/post.json, pages/category.json, pages/author.json, pages/legal.json
Posts, categories, authors, the About team, the footer’s Instagram photos, the legal pages src/content/collections/<name>.json

Change the text between the quotes and keep the field names. Or ask your tool: “Change the magazine’s name to Northline and the contact email to hello@northline.com in site.json.” Set site.url to your domain before you publish — the sitemap and share links are built from it.

The name appears in more places than site.name: the footer’s copyright, Home’s eyebrow (“Welcome to Kendi”), the copy of About, Contact, the Blog, Categories and Authors, and the legal texts. The logo draws it too (below). Ask your tool to search src/content/ for “kendi”, in any case, to find them all. The sidebar’s About text (“We influence 20 million users…”) is a demo claim: write what is true of your magazine.

In the footer’s copyright, {year} becomes the current year. The social links open the networks’ home pages: point them to your own profiles (socials in site.json, and each author’s socials).

Each post in collections/posts.json has slug (its address, /blog/<slug>), title, excerpt (the card text, the lead under the title and the page’s description), category and author (the slugs of a category and an author), date (2026-02-17, shown as “Feb 17, 2026”), image and the article body as blocks.

The posts are listed in the file’s order, newest first; every list takes them from there: the hero slider shows posts 1–5 and the small cards under it 5–7, Latest posts 8–11, the sidebar’s Spotlight 1–4 and the newsletter band’s photos 1–3. So put a new post first. Two flags pick posts by hand: "editorsPick": true for Editor’s pick (five) and "trending": true for Trending (six) and the header menu’s Spotlight; move the flags to choose others. Inspiration shows the newest post of each category, a post page its category’s six newest other posts.

Blocks are { "type": "paragraph", "text": "…" }, { "type": "heading", "level": 2, "text": "…" } (levels 2 and 3) and, in the legal pages, { "type": "list", "ordered": false, "items": ["…"] }. In a text, **bold** is bold, _italic_ italic and [label](/address) a link. Ask your tool if you prefer: “Add a post about city cycling to posts.json, in the Travel category by Rachel Kim, with the same fields as the others.”

Three demo slugs hold a typographic apostrophe (’). They work — the address encodes it — but plain slugs are simpler for your own posts.

  • Categories (collections/categories.json): slug, name, description (the category page’s lead and description) and image. Their order is the order of the Categories page and of every list that shows a few: the first five in the header menu and the footer, the first six in the sidebar’s Explore Topics.
  • Authors (collections/authors.json): slug, name, role, bio, avatar (the round photo in the meta lines and the author page’s photo) and socials. A post’s author is one of these slugs.
  • The team on About (collections/team.json): name, role, bio and photo. They are separate from the authors.
  • Instagram (collections/instagram.json): the footer’s four photos, each with its href.
  • Legal pages (collections/legal.json): slug (/legal/privacy-policy), title, description (the browser description), updated (a date) and body. The footer links them from footer.legalLinks in site.json, and the newsletter’s consent line links them in its text: change both for a new page. The demo’s legal texts are samples: write your own.

sponsoredAd in site.json is one ad in two looks — wide in Home’s main column, tall at the end of the sidebar — with its label (“- Sponsored Ad -”), the brand’s name, a line of text, a photo, the brand’s logo and a link. “Tenq Tech” is a made-up brand: put a real sponsor there, an ad for your own newsletter, or ask your tool to remove the ad from Home and the sidebar.

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

Photos Files
Posts post-<first words of the slug>.jpg (the image of each post names its file)
Categories, authors, the team category-<slug>.jpg, author-<slug>.jpg, team-<slug>.jpg
About, the ad, the footer about-1.jpg … about-3.jpg, ad-tenq-tech.jpg, instagram-1.jpg … instagram-4.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 an alt that describes it. In a chat builder, upload the photos and tell the tool which file names to give them.

The logo — the Kendi “K” mark and wordmark in black — is public/images/logo.svg; the header and the sidebar show it at 85 × 25, the footer at 102 × 30. Ask your tool to replace it with your own SVG: “Use public/my-logo.svg as the Logo in the header, the sidebar and the footer.” The browser tab icon is public/icon.svg, the home-screen icon public/apple-icon.png (180 × 180) and the share image public/opengraph-image.png (1200 × 630, made by the last prompt): replace all three.

Prompt 1 set up the design tokens: colours (--color-black, --color-grey, --color-white, --color-paper (the page), --color-line and a few more), the two gradients over photos, the font, text styles and spacing. Kendi has no accent colour: the buttons are Black and the photos bring the colour. To give the site a brand colour, ask for it on the buttons only: “Make the Button, the Subscribe button and the black category pill #1D4ED8 instead of Black.” Keep White text on a colour dark enough to read.

The font is Inter (weights 400 to 700, headings 600, text 500), with its optical size held at the text cut on every size. 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 Navigation column, 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 (“a breadcrumb, a page title, then PostCardStacks in three columns”) — so it matches the rest; it sits under the same fixed header.

To remove a section, ask the tool to take it out of the page: the sidebar and the newsletter band are shared, so say whether you mean one page or all of them.