Skip to content
Sign inJoin waitlist

Making it yours — Denzel AI Prompts

After the last prompt you have the Denzel 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’s name and the “ | Denzel” ending of the browser titles), the default browser title and description, site address src/content/site.json → site
The logo file and its name for screen readers src/content/site.json → logo
Menu, the search’s words (“Search All”, “Search…”, “No results found”, “Menu”, “Close”), social links, the sidebar, the footer (its text, e-mail, the two Celebration posts, the newsletter box and the copyright line) src/content/site.json (navigation, search, socials, sidebar, footer)
Home’s browser title and description, the slider, Editor’s Pick, Trending and Latest src/content/pages/home.json
The labels of the Blog, category, author and post pages (breadcrumbs, “Articles by:”, “Related Posts”, “More Articles by”, the empty texts and the descriptions) src/content/pages/blog.json
The 404 page src/content/pages/not-found.json
Posts, categories and authors src/content/collections/<name>.json (posts, categories, authors)

Change the text between the quotes and keep the field names. Or ask your tool: “Change the site’s name to The Daily Lantern and the footer e-mail to hello@dailylantern.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) and “Join 89,000 subscribers!” are placeholders: replace them.

The name Denzel appears in several places: site.json (site, logo.alt, the copyright line), Home’s title and description in pages/home.json, and the breadcrumbs (“Denzel”) and the descriptions (“… on Denzel”) in pages/blog.json. The logo is a picture of the name too (below). Ask your tool to search src/content/ for “Denzel” to find them all.

In the copyright line, {year} becomes the current year; “Theme by Marcframe” can stay or go. In the descriptions of pages/blog.json, {name} becomes the category’s or the author’s name. The social links open the networks’ home pages: point them to your own profiles, and remove the ones you don’t use (each author has their own links, below).

The menu names its pages by address: Home, All Post (/blog), the four categories (/category/business …) and Author (/author/anderson). When you add, rename or remove a category or an author, change navigation too.

Home features posts by their slug, in pages/home.json:

Field What it shows
slider.slugs The row of small posts under the header that moves one card every five seconds (six in the demo)
picks.lead, picks.slugs Editor’s Pick: the large post, then the two small ones beside it
trending.columns Trending: two columns, each a large post (lead) with its excerpt over two small ones (slugs)
latest.count Latest is not picked: it shows that many of the newest posts (eight), by date

Keep these slugs in step with posts.json: a slug that matches no post shows nothing. Ask your tool: “Put the post five-ways-to-read-more first in the slider.”

The sidebar sits beside the posts on Home, the category pages, the author pages and the posts (below them on phones and tablets). It has three boxes, set in sidebar of src/content/site.json:

  • About (about): the logo over the dotted world map (widget-background.png), the text and the social icons.
  • Recent (recent): the title, the “View All” link and four posts named by slug (posts), in that order. It does not follow the dates: change the slugs when you publish.
  • Explore Topics (topics): the categories named by slug (categories), each with its round photo and its number of posts followed by countLabel (“8 Post”).

The footer’s Celebration column picks its two posts the same way (footer.posts.slugs).

Each post in collections/posts.json has slug (its address, /blog/<slug>), title, excerpt (the text under the title on the cards that show one, and the search), category and author (a category’s and an author’s slug), date (2023-09-14, shown as “Sep 14, 2023”, in capitals on the cards), image with its alt text (the cards’ photo, the post’s cover and its share picture) and body.

Every list of posts is newest first, by date (posts of the same day keep their order in posts.json): the Blog, a category’s page, an author’s page, and under a post Related Posts (the three newest other posts of its category) and More Articles by (the three newest other posts of its author).

A post’s body is a list of blocks: { "type": "paragraph", "text": "…" }, { "type": "heading", "level": 3, "text": "…" } (levels 3 and 4) and lists ({ "type": "list", "ordered": false, "items": [ … ] }; an item can hold a list of its own). In any text, **…** is bold. Ask your tool if you prefer: “Add a post called Five ways to read more to posts.json, with the same fields as the others, in the Fashion category by Annabella.”

Each category in collections/categories.json has slug (/category/<slug>), title, description (the text under its name on its page) and image (the photo beside the title, and the round photo in Explore Topics; null leaves the page with its text alone). To show a new category in the menu, add it to navigation; in the sidebar, add its slug to sidebar.topics.categories.

Each author in collections/authors.json has slug (/author/<slug>), name, bio, avatar (the round photo; null shows the name alone) and social — facebook, twitter and instagram, each a link or null to hide it.

The default category “Uncategory” (uncategory) and the default author “Admin” (admin) have no photo and no posts in the demo: their pages show “No posts in this category yet.” and “No posts by this author yet.”, and the search leaves them out until they have a post. Keep them for posts you haven’t filed yet, or delete them.

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 Designed size
Posts the file named in each post’s image (post-….jpg) mostly 1600 × 1067
Categories category-business.jpg, category-technology.jpg, category-economy.jpg, category-fashion.jpg 800 × 533
Authors author-anderson.jpg, author-annabella.jpg, author-ceridwen.jpg, author-dostoevsky.jpg, author-melvile.jpg 120 × 120
The 404 illustration not-found.jpg 800 × 600
The sidebar’s About box widget-background.png (the dotted world map — the template’s own image, not a placeholder) 360 × 232

Photos fill their frame and are cropped. A post’s photo appears in many shapes — tall on Editor’s Pick, wide on the grid cards and the cover, square in the lists and the slider, round in Recent — so keep its subject in the middle. 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.

The logo is public/images/logo.svg (118 × 24), shown in the header, the phone menu, the sidebar’s About box and the footer. Replace the file with your own, or ask your tool: “Use public/images/my-logo.svg as the Logo, at the same height.” The browser tab icon is public/icon.svg (it turns white in a dark browser theme), 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 them. Posts share their own cover instead.

Prompt 1 set up the design tokens: colours (--color-ink, --color-body, --color-grey, --color-accent, --color-navy, --color-white …), the two fonts, text styles and spacing. Denzel is near-black ink on white, with an orange accent for the category labels and the hovers: change that set for another mood — “Change –color-accent to #2F6FEB.” Keep enough contrast between the text and the page. Keep the text styles’ sizes per breakpoint unless you want a different rhythm.

The titles, the headings of the post text and the menu are set in Noto Serif JP (--font-serif); everything else in Poppins (--font-sans). Another font works the same way — ask the tool to load it and use it in that variable.

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 links that lead to it (“View All”, “View More”). To add a page — an About or a Contact page, for example — write a prompt in the style of the page prompts: list its sections and reuse the components (“the breadcrumbs, then the layout with the sidebar”), so it matches the rest.

To remove a section, ask the tool to take it out of the page. The sidebar is shared: a change to it shows on every page that has it.