Manage content once, reuse it everywhere
Manage a set of content one time, then show it anywhere on your site. Edit it in one place and every page that uses it updates.
Instead of copying the same content onto five pages and updating all five by hand, you keep it in one list and connect that list to wherever it should appear.
What is a content list?
A content list is a collection of entries that all share the same shape. Think “Events”, “Team Members”, “Testimonials”, or “Blog Posts”. Each entry has the same fields, so you fill them in once and Mirin shows them consistently across your pages.
The point is reuse. Change the list, and every page that uses it changes with it.
| Name | Role | Photo | Bio |
|---|---|---|---|
| Jane Cooper | Founder | ||
| Marcus Lee | Designer | ||
| Priya Shah | Engineer |
The pieces
The list
The container, e.g. "Events".
Fields
What every entry holds (title, date, location, image, and so on).
Records
The individual entries in the list.
Bindings
The connection from a spot on a page to a field on your records. This is what puts the content on screen.
Publish
Mirin builds your pages with the live values, so visitors always see what is in the list right now.
A worked example: Events
Say you run events and you want them on your homepage and on a dedicated “Upcoming” page. Without a content list you would build each event twice and keep both pages in sync by hand. With a content list you do it once.
Create an Events list with fields like Title, Date, Location, Description, and an Image.
Add a record per event "Summer Tasting, June 14, The Old Mill" and so on.
Bind it in two places point the events section on your homepage at the Events list, and point the "Upcoming" page at the same list.
The payoff. When a venue changes, you edit that one event and both pages update. When next month’s event is confirmed, you add it once and every page that shows events picks it up. You never touch the pages again to keep your events current.
How records show up on pages
In the page editor, any setting that supports binding shows a small chain-link icon in the property panel. Click it, pick a list, pick a record, then pick a field. That setting now reads from your content list. When the page is published, Mirin resolves the binding on the server so visitors get the live value with no extra loading.
When to use one (and when not to)
Use a content list for
anything that repeats or appears in more than one place: events, blog posts, team members, testimonials, FAQs, product highlights.
Skip it for
one-off content that lives on a single page. A regular page is quicker to write and edit.
Glossary
- Content list
- A set of entries that share the same fields.
- Field
- One piece of every entry, like Date or Location.
- Record
- One entry in the list, like a single event.
- Binding
- A connection from a spot on a page to a field on your records.
- Reference field
- A field that links one record to another, so you can say "this event’s host is this team member" without retyping it.