Anything your site repeats belongs in a collection: blog posts, recipes, team members, events, listings or case studies. You write each item once, as a row of fields, and the site turns every item into a card on a list page and a page of its own.
In this tutorial you start from the Blog or magazine template, look at how its Journal is built, add a new collection of your own, and publish. The same steps work for any collection on any site.
What you need
- A Buildan.app account. Collections work on every plan. The Free plan holds 100 CMS items, Pro holds 5,000 and Business 50,000 (see Pricing).
- A site. If you do not have one yet, start from a template. The Blog or magazine template comes with a Journal, categories, tags and authors already set up.
Find your way around the CMS
Step 1: Open the CMS tab of your site
From your dashboard, open the site and choose the CMS tab. The left column lists every collection with the number of items in it. Pick one to see its items in a table with the title, status, slug and the date it was last changed.
The Blog or magazine template has four collections: Authors, Categories, Journal and Tags. Items that came with a template carry a Sample badge, so you always know which content you still need to replace.
Step 2: Check the fields with Fields
Choose Fields above the table. Each row is one field with a label, a key and a type. The Journal has a title, an excerpt, a cover image, a rich text body, a category, tags, an author, a publish date, a reading time and a Featured switch.
There are 15 field types: text, long text, rich text, number, yes or no (boolean), date, image, gallery, link, email, single and multiple choice (select and multiselect), a reference to another collection, several references, and colour. Tick Required when an item cannot be saved without a value, and Translate when the field should have a version per language.
At the bottom of the dialog, Title field decides which field names each item, and Main image field decides which image shows on cards and when the page is shared.
Step 3: Edit an item and publish it
Click a row to open the item. Sample items show a reminder at the top: replace the text and photos with your own. Fill in the fields, then choose Publish, or Save draft to keep working on it later.
The Slug field near the bottom is the item's address. Leave it empty and it is made from the title. Under Schedule publishing you can pick a date and time and choose Schedule: the item goes live on its own at that time. Older versions of an item are kept under Revisions, each with a Restore button.
See what is set up for a collection
Step 4: Open the collection's Settings
Choose Settings above the table. This checklist shows everything Buildan.app set up on your site for this collection, each with a switch:
- List page: a page with every item, with filters, sort, search and pages.
- Item page: one page per item, with breadcrumbs, related items and previous and next links.
- Nav link: a link to the list page in the site menu.
- SEO and structured data: titles like "Item | Site", descriptions from the excerpt, the cover as share image, and structured data for search engines.
- Sitemap: item pages are listed in
sitemap.xml. - RSS feed: a feed of the newest items, linked from every page.
- Site search: items are added to the site's search index.
The page addresses are links: click one to open that page in the editor. Changes go into your draft, and you publish to make them live.
![The Journal settings dialog listing List page at /journal, Item page at /journal/[slug], Nav link, SEO and structured data, Sitemap, RSS feed at /journal/feed.xml and Site search, each switched on](cms-settings "1: the list page. 2: one page per item. 3: the RSS feed.")
Turning off the list page, the item page or the nav link removes something from your site, so Buildan.app first shows exactly what will go and waits for you to confirm. To rename a collection or change its address, use Name and address at the bottom of the same dialog and choose Rename: you see every change first, including a redirect from the old address to the new one.
Add a collection of your own
Step 5: Create it with New collection
Choose New collection under the list of collections. Give it a Name, such as Workshops, and say what One item is called, such as Workshop. New collections start with a title and a body. Choose Add field for anything else, give each field a label and pick its type.
Choose Save. Buildan.app creates the collection together with a list page, an item page and a nav link, the same way the Journal was set up.
Design the list and the item pages
Step 6: Change the list in the editor
Choose Open editor, then open the list page from the page menu at the top of the editor (for the Journal it is Journal). Click the grid of cards, and press Esc until the inspector on the right says Journal list. Its Collection list settings choose:
- Collection: which collection the list shows.
- Items shown: how many items per page, up to 100.
- Sort by and Order: for example the publish date, newest first.
- Pages (pagination) and Search box: switch them on for long lists.
- Filter buttons: a row of buttons from a choice or text field, such as the category.
- Empty text: what visitors see when there is nothing to show.
The first card is the template for every item. Style it like any other element and every card follows.
Step 7: Bind the item page to fields
Open the item page (for the Journal it is Post page). It is one page that shows every post. Click the headline: under CMS field in the inspector you can see it shows the Title of whichever post is open.
Any text, rich text, image, button or link can be bound this way. Pick a field from the CMS field menu, or Item link, Slug or Created date. Choose Not bound (fixed text) to type the same words on every item page.
Publish and check the live site
Step 8: Publish and visit the list and an item
Choose Publish in the editor. If the site still has sample items, Buildan.app lists them and asks you to confirm first.
Open the list page on your live site. Visitors can filter by category with the buttons, sort, and open any post. Each post has its own address, breadcrumbs and links to related and nearby posts, and it works the same on a phone.
The RSS feed is at the address shown in the collection's settings, for example /journal/feed.xml, and every page links to it so feed readers find it on their own. Item pages are added to your sitemap, and search engines get a title, a description and a share image for each post.
Tips and pitfalls
- Replace sample content before you go live. The Sample badge stays until you edit an item. Sample text is there to show the layout, not to be published.
- Write a good excerpt. It is used on cards, in search results and when a post is shared, so one or two clear sentences pay off.
- Keep slugs short and stable. A slug is part of the address. If you change it after publishing, links that people saved will point to the old address.
- Use references for shared details. Authors and categories are their own collections, so you change an author's bio once and every post shows the new version.
- Choose a field type that fits. A date field sorts by date and a number field sorts by value; the same data in a text field sorts like words.
- Publish the site after publishing items. Published items reach visitors on the next site publish.
Summary
A collection is a list of items with the same fields. Open the CMS tab to add and publish items, use Fields to shape them and Settings to see and switch the list page, item page, nav link, SEO, sitemap, RSS feed and search. In the editor, the list's Collection list settings control how many items show and how they sort and filter, and CMS field binds the item page to each item's content. Publish, and every item has its own page.
Next, learn how to collect form submissions and automate emails, or show rows from your own database.


