Skip to content
Sign inJoin waitlist

Making it yours — Brickfolio AI Prompts

After the last prompt you have the Brickfolio 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 “ | Brickfolio” ending of the browser titles), Home’s browser title and description, site address, e-mail src/content/site.json → site
The logo: its photo, its two lines (“Brick” / “folio”) and its name for screen readers src/content/site.json → logo
Menu, “Hire Me”, the phone menu’s “Menu” / “Close”, the social links, the footer (the newsletter box and the copyright line) src/content/site.json (navigation, button, menu, social, footer)
Home: the profile card, My Latest Work, Work with Me and “Can’t decide”, the testimonials, My Experiences, the client logos, the articles, the contact form and the questions src/content/pages/home.json (profile, projects, services, testimonials, experience, clients, blog, contact, faq)
The labels of the project and post pages (“Date”, “Service”, “Client”, “Project Overview”, “Key Highlights”, “More Projects”, “More Posts”) and their close button src/content/pages/project.json, pages/post.json
The 404 page src/content/pages/not-found.json
Projects, services and posts src/content/collections/<name>.json (projects, services, posts)

Change the text between the quotes and keep the field names. Or ask your tool: “Change the name to Jane Doe and the e-mail to hello@janedoe.com in site.json and home.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) is a placeholder: replace it, also in the “Email me” button of services.cta in pages/home.json (mailto:hello@example.com).

The demo person, Javier Martinez, appears in pages/home.json (profile: the name, the greeting and the text) and in the testimonials’ quotes. The name Brickfolio is in site.json (site, logo, the copyright line). Ask your tool to search src/content/ for “Javier” and “Brickfolio” to find them all. “Designed by Framebrick” in the copyright line can stay or go.

The rotating roles under your name are profile.roles (one shows at a time, the next every four seconds). The social links are social in site.json: each has the two letters on its chip (label), the network’s name (it picks the icon tile, public/icons/social-<name>.svg) and the link. They open the networks’ home pages: point them to your own profiles, and remove the ones you don’t use.

The header links lead to Home’s sections by their anchors (#project, #service, #resume, #blog, #contact); each section’s id in pages/home.json must stay the same as its link. “Hire Me” and “Contact Me” lead to the contact form.

Each project in collections/projects.json has slug (its address, /project/<slug>), title, service (the label on its card and page; it need not match a service), date (2024-07-01, shown as “July 2024”), client, summary (the card’s text and the page’s description for search engines), cover (the photo of its card, the top of its page and its share picture, with alt), description and highlights (the Project Overview and Key Highlights, as rich text) and gallery (three photos: two side by side, then one full width; set visible to false to leave one out).

Home shows the projects in the collection’s order, four at first and the rest with “More Projects” (projects.pageSize in pages/home.json). A project page lists the first three other projects under More Projects (two below 1000 px). Ask your tool: “Add a project called Atlas, with the same fields as the others, at the top of projects.json.”

Each service in collections/services.json has title, description, price (shown in “Starting at {price} per project”, the line in pages/home.json → services.price), href (the “More Details” link; the demo’s lead to the contact form) and images, four small photos that run in two columns on the card (each with visible). Work with Me shows all of them, in order. The block under them, “Can’t decide or custom request?”, is services.cta.

Testimonials, experience, clients and questions

Section titled “Testimonials, experience, clients and questions”

These are page copy, not collections, all in pages/home.json:

  • testimonials.items: each with name, role, photo, rating (1 to 5 stars) and quote. The cards run past from right to left.
  • experience.items: each with role, company, period and text. Under them, experience.cta holds “Download CV” (/cv.pdf) and “Contact Me”.
  • clients.logos: the client logos that run past, each with its file and alt text.
  • faq.items: each with question and answer. One is open at a time, the first on load.

Each post in collections/posts.json has slug (/blog/<slug>), title, category (a text: “Product Design”, “UX/UI”, “Web Design”), date (2024-07-08, shown as “Jul 8, 2024”), image with its alt text (the card’s photo, the page’s cover and its share picture) and body. Home lists them newest first, four at a time (“More Posts”); a post’s More Posts shows the three newest other posts of its category (two below 1000 px). There are no category pages.

The bodies of posts and a project’s description and highlights are blocks: { "type": "paragraph", "text": "…" }, { "type": "heading", "level": 3, "text": "…" } and lists ({ "type": "list", "ordered": false, "items": [ … ] }). In any text, **…** is bold and `…` is code (set in Fragment Mono). Ask your tool if you prefer: “Add a post called Designing for trust to posts.json, with the same fields as the others, in the UX/UI category.”

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

Photos Files Designed size
The profile photo (80 px round; also the logo’s photo) profile-javier-martinez.png 240 × 240
A project’s cover project-<name>-cover.jpg 1600 × 1066
A project’s gallery project-<name>-1.jpg, -2.jpg (side by side), -3.jpg (full width) 1000 wide, 1600 wide
A post’s cover post-<first words of the slug>.jpg 1600 wide
A service’s small photos service-<slug>-1.jpg … -4.jpg 300 wide (200 to 375 tall)
A testimonial’s photo (50 px round) testimonial-<name>.jpg 70 to 150 px square

Photos fill their frame and are cropped, so keep their proportions close to the placeholder’s. The project and post cards show their photo at 50 % grey until it is hovered. 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.

“Download CV” in My Experiences links to /cv.pdf, a one-page sample for a person who doesn’t exist. Put your own PDF in public/ as cv.pdf, or point experience.cta.download.href in pages/home.json to another file.

The five logos that run past on Home are SVG files, public/images/client-logo-1.svg … client-logo-5.svg, named in pages/home.json → clients.logos with their alt text. They are placeholder logos from Logoipsum: replace them with your clients’ logos (SVG in one grey, on a transparent background, about 110 × 25 — the row is 30 tall), and give each its client’s name as alt text.

The logo is the profile photo in a circle beside the name in two lines, “Brick” in orange and “folio” in light grey with an orange dot, drawn as text. Change the photo with logo.photo and the two lines with logo.first and logo.second in site.json, and logo.label for screen readers. Ask your tool to use your own logo instead: “Use public/my-logo.svg as the Logo, at the same height.”

The browser tab icon is public/icon.png (192 × 192) and the home-screen icon public/apple-icon.png (180 × 180); in the pack both are placeholders for the round profile photo: replace them with yours. The site has no share image of its own: a project or a post shares its cover, and Home and the 404 share none. Ask your tool to add one if you want (public/opengraph-image.png, 1200 × 630).

The icons are in public/icons/: the Phosphor icons (the arrow, the plus and minus, the close cross, the star, the calendar and the buildings) and the four social tiles shown over the chips on hover.

Prompt 1 set up the design tokens: colours (--color-ink, --color-light, --color-grey, --color-accent, --color-snow, the translucent whites …), the fonts, text styles and spacing. Brickfolio is light grey text on near-black Ink, with an orange accent for the buttons, the stars 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 font is Inter (400, 500 and 700; the accent word of a section title in 700 italic), with its optical size fixed at 14; Fragment Mono only sets the code in the posts. Another font works the same way — ask the tool to load it and use it in --font-sans.

Brickfolio is one long Home page with a page for each project and each post. To remove a section of Home, ask your tool to take it out of the page and its link out of the menu (navigation in site.json). To add a page — an About or a separate Blog page, for example — write a prompt in the style of the page prompts: list its sections and reuse the components (“the article header, then rich text, then the footer”), so it matches the rest, and add it to the menu and the sitemap.

The header and the footer are shared: a change to them shows on every page.