Editing the content — Brickfolio Next.js
All the words and images of this Next.js template live in src/content/ and public/, in plain TypeScript files you edit while npm run dev shows the result.
No CMS is needed: text goes between quotes and items are separated by commas. If you would rather manage content in Sanity, Payload, Strapi or Directus, see Using a headless CMS.
src/content/ site.ts name, title, description, domain, e-mail, logo, header, social links, newsletter, copyright pages/home.ts every section of Home pages/project.ts the labels of a project page pages/post.ts the labels of a post page pages/not-found.ts the 404 page collections/*.ts projects, services and posts routes.ts the URL of every page types.ts the fields each kind of item hasNot sure which file holds a piece of text? The page maps label every section of every page with the file that renders it.
Your details first
Section titled “Your details first”src/content/site.ts holds what appears on every page:
| Export | Shown where |
|---|---|
site.name |
The browser title suffix (“EcoShop - Sustainable E-commerce Platform | Brickfolio”) and the share cards |
site.title |
Home’s browser title, used whole, and the default of any page without its own |
site.description |
Search results and share cards for Home. It describes the template: write yours. |
site.url |
Set this to your domain before publishing. Canonical links, share links, sitemap.xml and robots.txt are built from it. |
site.email |
Your contact address, kept here for reference; no page reads it. The address visitors see is the “Email me” button’s mailto:hello@example.com in home.ts (below): change both. |
logo |
The logo in the header (Making it look like your brand) |
navigation |
The header’s five links (and the phone menu): Portfolio, Services, Resume, Blog and Contact, each an anchor of a Home section (#project, #service, #resume, #blog, #contact) |
button |
The header’s “Hire Me” pill (to #contact) |
menu |
The phone menu button’s two labels (“Menu”, “Close”) |
social |
The four social links under the profile card: label is the two-letter chip (“FB”), name the network (read by screen readers, and it picks the mark shown on hover), href the address (the demo’s open the networks’ home pages) |
footer |
The newsletter box’s texts (newsletter) and the copyright line (copyright) |
A social link’s name must be one of Facebook, Twitter, Dribbble and Behance to show a mark on hover (the marks
are public/icons/social-*.svg, named in src/lib/to-ui.ts); another network works as a link and a chip, without the
mark. Point the links to your own profiles and remove the ones you don’t use.
The demo’s person and name appear in many places: “Javier Martinez” in the profile card, the testimonials and the CV,
“Brickfolio” in site, the logo and the copyright line (“Copyright © Brickfolio | Designed by Framebrick”). Search src/ for “Javier” and “Brickfolio” to find them all.
Home, section by section
Section titled “Home, section by section”Home is one page; src/content/pages/home.ts holds every section’s copy, in the order they appear. Change the text
between the quotes, keeping the field names: the sections read them by name. Apostrophes are safe inside double quotes,
and the demo uses both ’ and the typographic ’.
| Field | Section | What it holds |
|---|---|---|
profile |
The profile card (the sidebar) | photo, name, greeting (“Hey, I’m Javier Martinez”), roles (the words that step every four seconds under the greeting), headline (the page’s <h1>) and text |
projects |
My Latest Work | id (the anchor, project), title and accent (the bold italic word: “My Latest Work”), text, pageSize (how many cards show before “More Projects”: 4) and the button’s label |
services |
Work with Me | id, title, accent, text, price (“Starting at {price} per project”: {price} becomes the service’s price), more (the link’s label, “More Details”) and cta: the line “Can’t decide or custom request?”, its text and the two buttons (“Email me” → mailto:hello@example.com, “Contact” → #contact) |
testimonials |
Trusted by Professionals | title, accent, text and items: eight quotes, each with a name, a role, a photo, a rating (stars out of 5) and the quote |
experience |
My Experiences | id (resume), title, text, items (each a role, company, period and text) and cta: the line “Let’s work together…”, “Download CV” (→ /cv.pdf) and “Contact Me” |
clients |
My Awesome Clients | title, text and logos (each { src, alt }) |
blog |
Latest Articles & Publications | id, title, text, pageSize (4) and the “More Posts” label |
contact |
Let’s Connect | id, title, text, the form’s fields, the button’s label and its two messages (Forms) |
faq |
Questions? Answers | title, accent, text and items (each a question and its answer) |
The id of a section is the anchor the header’s links point to: if you change one, change the link in navigation too.
Testimonials, experience, client logos and questions are lists in home.ts, not collections: add, remove or reorder
items there.
The other page files:
| File | What it holds |
|---|---|
project.ts |
The labels of a project page (“Date”, “Service”, “Client”, “Project Overview”, “Key Highlights”), “More Projects” with count (how many other projects show: 3; countCompact: 2 of them below 1000 px) and the close button’s link and screen-reader label (“Back to projects”, to /#project) |
post.ts |
The labels of a post page (“Date”, “Category”), “More Posts” with count and countCompact, and the close button (“Back to articles”, to /#blog) |
not-found.ts |
The 404 page: “404”, the message (also its browser title), the line under it and “Back to Homepage” |
Your CV
Section titled “Your CV”“Download CV” opens public/cv.pdf, a one-page sample made for the template. Replace the file with your own CV and keep
the name, or put another file in public/ and change experience.cta.download.href in home.ts.
Collections
Section titled “Collections”src/content/collections/ holds the lists the site builds pages and sections from:
| File | What it feeds |
|---|---|
projects.ts |
My Latest Work on Home, one page per project at /project/<slug>, and “More Projects” under a project |
services.ts |
Work with Me on Home (services have no page) |
posts.ts |
Latest Articles & Publications on Home, one page per post at /blog/<slug>, and “More Posts” under a post |
Projects and services keep the order of their files. Posts are sorted by date, newest first, on Home and under a
post; two posts of the same date keep the order of the file.
Home shows the first four projects and the four newest posts; “More Projects” and “More Posts” show four more per click and go once everything is shown. Every card is in the page from the start (hidden until its turn), so search engines find them all.
Adding a project
Section titled “Adding a project”Copy an existing entry, paste it in projects.ts, and change the values:
{ "slug": "northwind-brand-refresh", // the URL: /project/northwind-brand-refresh "title": "Northwind - Brand Refresh", // the card, the page's title and its browser title "service": "Branding", // the kind of work, on the card and the page "date": "2026-09-01", // shown as "September 2026" "client": "Northwind Ltd.", // on the page "summary": "A new identity and website for a coffee roaster.", // on the card; the page's search description "cover": { "src": "/images/project-northwind-cover.jpg", "alt": "…" }, // the card and the top of the page "description": [ // rich text under "Project Overview" { "type": "paragraph", "text": "What the project was about." } ], "highlights": [ // rich text under "Key Highlights" { "type": "list", "ordered": false, "items": ["**Strategy**: …", "**Design**: …"] } ], "gallery": [ // three images: two side by side, then one full width { "src": "/images/project-northwind-1.jpg", "alt": "…", "visible": true }, { "src": "/images/project-northwind-2.jpg", "alt": "…", "visible": true }, { "src": "/images/project-northwind-3.jpg", "alt": "…", "visible": true } ]}The quotes around the field names come from the way the files are generated; they are optional in TypeScript, so keep them or leave them out.
A project page shows the title, the date, the service and the client, the cover, “Project Overview”, the first two gallery
images side by side, “Key Highlights”, the third image full width, then “More Projects”: the first three other projects
of the file (two below 1000 px). Set "visible": false to hide a gallery image; with both of the first two hidden, their
row goes. A project’s search description is its summary (followed by the start of the description when the summary is
shorter than 80 characters), cut at 160 characters.
Adding a service
Section titled “Adding a service”{ "slug": "brand-identity", // a name for the item (services have no page) "title": "Brand Identity", "description": "…", "price": "$2,000", // "Starting at $2,000 per project" "href": "#contact", // "More Details" "images": [ // the two columns of small photos at the right of the card { "src": "/images/service-brand-identity-1.jpg", "alt": "…", "visible": true }, { "src": "/images/service-brand-identity-2.jpg", "alt": "…", "visible": true }, { "src": "/images/service-brand-identity-3.jpg", "alt": "…", "visible": true }, { "src": "/images/service-brand-identity-4.jpg", "alt": "…", "visible": true } ]}The first column shows the images in order, the second in reverse; on hover they brighten and move. “More Details” leads to the contact form in the demo: point it at a page of yours if you have one.
Adding a post
Section titled “Adding a post”{ "slug": "designing-calm-interfaces", // the URL: /blog/designing-calm-interfaces "title": "Designing Calm Interfaces", // the card, the page's title and its browser title "category": "UX/UI", // its name, shown on the card and the page "date": "2026-11-02", // shown as "Nov 2, 2026"; the lists sort by it "image": { "src": "/images/post-designing-calm-interfaces.jpg", "alt": "…" }, // the card and the page's cover "body": [ // the article: rich text, below { "type": "paragraph", "text": "First paragraph." }, { "type": "heading", "level": 3, "text": "A heading" }, { "type": "paragraph", "text": "Another paragraph." } ]}category is plain text, not a reference: “More Posts” under a post lists up to three other posts with exactly the same
category, newest first (two below 1000 px), and is left out when there is none. There are no category pages. A post’s
search description is its first paragraph, cut at 160 characters, and it shares its own cover photo.
Removing an item
Section titled “Removing an item”Delete the entry. Its own page and its sitemap entry disappear on the next build. Nothing else names a project, a service or a post, so nothing breaks.
What each field means
Section titled “What each field means”src/content/types.ts is the reference: it lists every field and a comment for the ones that are not obvious. Your
editor shows the same information while you type.
Rich text: projects and posts
Section titled “Rich text: projects and posts”A post’s body and a project’s description and highlights are lists of blocks:
body: [ { "type": "paragraph", "text": "Prototyping is a crucial step in **product design** …" }, { "type": "heading", "level": 3, "text": "1. Validating Ideas" }, { "type": "list", "ordered": false, "items": [ "**Early Feedback**: Prototypes allow designers to …", "**Iterative Testing**: …" ] }, { "type": "list", "ordered": true, "items": [ { "text": "**Define the problem**", "blocks": [ { "type": "paragraph", "text": "Start with …" }, { "type": "list", "ordered": false, "items": ["…", "…"] } ] } ] }]- Paragraphs are plain text; words between double asterisks are bold (
**…**), words between backticks are code (`flex-wrap`, drawn in Fragment Mono on a faint box). - Headings take a
levelfrom 2 to 6; every level is drawn in the same heading style (24 px on desktops). - Lists are bulleted (
"ordered": false) or numbered ("ordered": true). An item is a line of text; or an object with itstextand a list nested under it (orderedanditems); or an object with itstextfollowed by more blocks (blocks: paragraphs and lists, as in the demo’s numbered steps).
There are no italics, links or images inside the text.
Images
Section titled “Images”- Put the file in
public/images/. - Refer to it in the content as
/images/<file>(the path starts atpublic).
Sizes and formats are handled for you: pages use next/image, which serves a scaled, modern format per device. The
download’s placeholders show the size of each demo photo; use photos at least as large:
| Photos | Demo size | Frame |
|---|---|---|
A project’s cover |
1600 × 1066 | 3 : 2 on its page; 380 px tall on the cards |
A project’s gallery |
1000 wide for the first two, 1600 for the third | 3 : 2 |
A post’s image |
1600 wide (some taller) | 3 : 2 on its page; 250 px tall on the cards |
A service’s images |
300 wide (200 to 375 tall) | 100 × 150 tiles |
A testimonial’s photo |
70 to 150 px square | 50 px round |
The profile photo |
240 × 240 (PNG) | 80 px round |
The client logos |
SVG | 30 px tall |
Photos in a fixed frame are cropped to fill it, so a photo of other proportions works, but you lose the edges the frame cuts. The cards are drawn in half grey and take their colours on hover.
Every photo comes with a short description for screen readers and search engines: alt in { src, alt }. Write one for
each photo you change. The client logos say “Client logo”: write your clients’ names there.
The profile photo is also the logo’s photo (logo.photo in site.ts), and the browser icons, src/app/icon.png and
src/app/apple-icon.png, are the same face in a circle: when you change your photo, change those too
(Making it look like your brand).
Text that is not in content/
Section titled “Text that is not in content/”Almost every word is content, including the forms’ messages. The few interface words that never change per site live in the code:
- “Main” (the menu’s name for screen readers) in
src/components/site/Header.tsx; - “{rating} out of 5” (the stars, for screen readers) in
src/components/sections/Testimonials.tsx; - the date formats (“Jul 8, 2024” for posts, “July 2024” for projects) in
src/lib/format.ts; - the page’s language,
lang="en", insrc/app/layout.tsx.
Search for the word and you will find it.
After editing
Section titled “After editing”npm run buildA successful build means every content file has the fields it needs and every page still renders. It doesn’t check that
the images exist or that links written as text ("#contact", "/cv.pdf") lead somewhere: click through the site once
with npm start after big changes. See Going live for the rest of the checklist.