Fields define what each item in a collection can store. A blog post might have a title, a cover image, a body, a publishing date, and an author.
Last updated
Each field has a type. The type decides the editor, the validation, and how the value can be used on a page.
For short text: titles, names, slugs, labels, and descriptions.
Options include allowing multiple lines, a minimum and maximum length, and a default value.
For formatted content: paragraphs, headings, lists, links, and images.
Choose a toolbar preset:
Basic for text and inline formatting.
Standard for headings and lists.
Full for buttons, media, layouts, accordions, carousels, and components.
The Full preset gives the most freedom, but it also makes it easier for content to look inconsistent. Standard is a good default for articles.
For integers, decimals, prices, and counts.
You can set the number format, minimum and maximum values, and a default.
For a single image or a gallery.
Options include allowing multiple images, a maximum file size, and maximum width and height. Images are stored in the media library.
For event dates, release dates, and deadlines.
You can turn on the time picker and choose whether new items default to the current time.
For a fixed list of choices, such as a category or a status.
You can allow multiple selections and define the options. Each option can have a label and a color.
Option labels can be translated for a multilingual site.
For a true or false flag, such as "Featured" or "In stock".
For connecting items across collections. For example, a post can reference an author, or a product can reference a category.
Choose the target collection and whether an item can reference one entry or many.
References are what make nested lists possible. A blog list can show each post with its author, and an author page can list that author's posts.
Each field also has:
Label, shown in the item editor.
Help text, shown under the field to guide the person filling it in.
Required, so an item cannot be saved without it.
Show in list, so the value appears as a column in the item table.
Use required fields sparingly. A field that is required but often unknown leads to placeholder text.
You can reorder fields and hide them from the item editor without deleting them. Hidden fields keep their values and are useful when a field is no longer collected but still needed for older items.
You can change a field's label, help text, required setting, and configuration after creation.
You cannot change its type. A text field cannot become an image field, because existing values would no longer make sense. If you need a different type, create a new field, move the content, and remove the old one.
Removing a field removes it from the collection's editor and forms. There is no undo for that action, so be sure before you remove one.
For blog posts:
Name (text, required).
Slug (text, required).
Cover image (image).
Excerpt (text, multiline).
Body (rich text, Standard).
Published (date and time).
Author (relation to the Authors collection).
Then turn on collection pages and design the list and item pages.
Read Collection pages for that step.
A website builder that works like a document. CMS, forms and EU hosting included.
© 2026 Remake. All rights reserved.
