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 “FAQs”. 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.
Articles work the same way. Create or open a Blog Posts content list, then manage each article as an entry. Your theme controls the listing and individual article designs.
| 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.
How a list powers a page template
A dynamic page connects one page design to one Content List. For example, Therapist Profile can be powered by Therapists with a record URL such as therapists/{slug}. Page settings show this relationship, the current preview record, and a path to manage the full list.
Page source
Connect Therapists and set one Therapist per URL.
Component source
Use the page therapist, one pinned record, or a list query.
Build inspector
Edit the selected therapist values inside Clinician Profile.
Choose Katie in the toolbar, then select Clinician Profile in Build. Therapist content appears first, with quiet labels such as Page record, Therapists, Name. Component settings such as a back link stay separate. Changes appear on the canvas immediately and are saved only when you choose Save Katie.
Use New Therapist beside the record picker to start a local draft. The canvas previews the draft immediately, but Mirin does not add it to Therapists until you choose Create Therapist. An untouched draft cancels immediately. If you switch after editing, Mirin asks whether to create, discard, or keep editing.
The Therapists list separates Dynamic templates from Used by components. Open template returns to the one record per URL design. Manage all returns from the builder to the complete record and field workspace.
Names and record labels
A list has a display name plus labels for one record and multiple records. For a list named “Therapists”, use “Therapist” and “Therapists”. Mirin uses those labels in search, new record buttons, preview pickers, counts, and confirmations.
List name
Therapists
One record
Therapist
Multiple records
Therapists
Advanced settings also show a fixed technical key for older themes and integrations. You usually do not need it. Renaming a list or its labels does not change the immutable list connection used by page bindings.
Editing long records
Save, Publish or Unpublish, and Delete stay visible while you scroll through a long record. Delete opens a confirmation that names the record and explains that removal is permanent. Closing or cancelling the confirmation leaves the record untouched.
Titles and descriptions for record pages
A page per record can build its browser title, search description, social title, social description, and social image from record fields. In Page Settings, add field names in double braces.
{{name}}, {{credentials}} | {{site.name}}
Katie O’Leary, LPC | Oak Mountain Mental Health
If credentials are empty, Mirin removes the unused comma. A record can also supply an explicit SEO or social override for exceptional cases. Standard profiles remain ordinary web pages. Choose Article only for posts that should receive article metadata and feed discovery.
When to use one (and when not to)
Use a content list for
anything that repeats or appears in more than one place: events, 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.