Skip to content
Sign inJoin waitlist

Editing the content — Brickfolio Astro

All the words and images of this Astro template live in src/content/ and src/assets/images/, in plain JSON files you edit while npm run dev shows the result.

No CMS is needed: text goes between double 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.json name, title, description, domain, e-mail, logo, header, social links, newsletter, copyright
pages/home.json every section of Home
pages/project.json the labels of a project page
pages/post.json the labels of a post page
pages/not-found.json the 404 page
collections/*.json projects, services and posts
routes.ts the URL of every page
schemas.ts the fields each kind of item has, and which are required

Not sure which file holds a piece of text? The page maps label every section of every page with the file that renders it.

src/content/site.json holds what appears on every page:

Field 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 (astro.config.mjs reads it as Astro’s site).
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.json (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 is one page; src/content/pages/home.json 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. A double quote inside a text is written \"; apostrophes need nothing, 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.json, not collections: add, remove or reorder items there.

The other page files:

File What it holds
project.json 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.json 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.json The 404 page: “404”, the message (also its browser title), the line under it and “Back to Homepage”

“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.json.

src/content/collections/ holds the lists the site builds pages and sections from, one JSON array each:

File What it feeds
projects.json My Latest Work on Home, one page per project at /project/<slug>, and “More Projects” under a project
services.json Work with Me on Home (services have no page)
posts.json 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.

Copy an existing entry, paste it into the list (mind the comma between entries), and change the values:

{
"slug": "northwind-brand-refresh",
"title": "Northwind - Brand Refresh",
"service": "Branding",
"date": "2026-09-01",
"client": "Northwind Ltd.",
"summary": "A new identity and website for a coffee roaster.",
"cover": { "src": "/images/project-northwind-cover.jpg", "alt": "A bag of coffee beside a laptop showing the new site" },
"description": [
{ "type": "paragraph", "text": "What the project was about." }
],
"highlights": [
{ "type": "list", "ordered": false, "items": ["**Strategy**: its text.", "**Design**: its text."] }
],
"gallery": [
{ "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 }
]
}
  • slug is the URL: /project/northwind-brand-refresh.
  • title is the card’s title, the page’s <h1> and its browser title.
  • service (the kind of work) and date (shown as “September 2026”) are on the card and the page; client on the page.
  • summary is the card’s text and the page’s search description (followed by the start of the description when it is shorter than 80 characters, cut at 160).
  • cover is the card’s photo, the top of the page and the picture shown when the project is shared.
  • description (under “Project Overview”) and highlights (under “Key Highlights”) are rich text.
  • gallery holds three images: the first two side by side under the overview, the third full width under the highlights. "visible": false hides one; with both of the first two hidden, their row goes.

A project page ends with “More Projects”: the first three other projects of the file (two below 1000 px).

{
"slug": "brand-identity",
"title": "Brand Identity",
"description": "Logos, colours and type that make your product recognisable.",
"price": "$2,000",
"href": "#contact",
"images": [
{ "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 }
]
}

Services have no page, so slug only names the item. price shows as “Starting at $2,000 per project”; href is “More Details”, which leads to the contact form in the demo. The four images are the two columns of small photos at the right of the card: the first column shows them in order, the second in reverse; on hover they brighten and move.

{
"slug": "designing-calm-interfaces",
"title": "Designing Calm Interfaces",
"category": "UX/UI",
"date": "2026-11-02",
"image": { "src": "/images/post-designing-calm-interfaces.jpg", "alt": "A tidy desk with a sketchbook and a tablet" },
"body": [
{ "type": "paragraph", "text": "First paragraph, with a **bold** phrase." },
{ "type": "heading", "level": 3, "text": "A heading" },
{ "type": "paragraph", "text": "Another paragraph." }
]
}
  • slug is the URL: /blog/designing-calm-interfaces; title the card’s title, the page’s <h1> and its browser title.
  • 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.
  • date ("2026-11-02") is shown as “Nov 2, 2026”, and sorts the lists.
  • image is the card’s photo, the cover of the post and the picture shown when it is shared.
  • body is the article. Its first paragraph, cut at 160 characters, is the post’s search description.

Delete the entry (and the comma before it, if it was the last). 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.

src/content/schemas.ts is the reference: it lists every field, which are required, and what kind of value each takes. npm run check and npm run build check every entry against it and name the collection, the item and the field that is wrong.

A post’s body and a project’s description and highlights are lists of blocks:

[
{ "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 level from 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 its text and a list nested under it (ordered and items); or an object with its text followed by more blocks (blocks: paragraphs and lists, as in the demo’s numbered steps).

There are no italics, links or images inside the text.

  1. Put the file in src/assets/images/.
  2. Refer to it in the content as /images/<file>, with an alt.

Astro resizes, compresses and converts the photos when the site builds, so each device gets a size that fits. A content path that points to a missing file stops the build with its name. 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.json), and the browser icons, public/icon.png and public/apple-icon.png, are the same face in a circle: when you change your photo, change those too (Making it look like your brand).

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.astro;
  • “{rating} out of 5” (the stars, for screen readers) in src/components/sections/Testimonials.astro;
  • the date formats (“Jul 8, 2024” for posts, “July 2024” for projects) in src/lib/format.ts;
  • the page’s language, lang="en", and og:locale in src/layouts/Layout.astro.

Search for the word and you will find it.

Terminal window
npm run check
npm run build

check reads every content file against its schema; a successful build means every page still renders and every image exists. Neither checks that links written as text ("#contact", "/cv.pdf") lead somewhere: click through the site once with npm run preview after big changes. See Going live for the rest of the checklist.