Custom Field types reference
Every Custom Field type Acrosite offers — Text, Long Text, Number, Boolean, Date, URL, Email, Select, Multi-select, and Image — what each captures and how it is stored.
Acrosite offers ten Custom Field types. Each one captures a particular kind of value and is written into a content item's frontmatter under the field's key. This reference explains what each type is for and how its value is stored. To add a field, see Add Custom Fields.
The field types
- Text — a short, single line of text for names, labels, summaries, or callouts.
- Long Text — a multi-line text area for longer descriptions.
- Number — a numeric value, such as an order, rating, or count.
- Boolean — an on/off value (yes or no).
- Date — a calendar date.
- URL — a web address.
- Email — an email address.
- Select — one option chosen from a list you define.
- Multi-select — several options chosen from a list you define.
- Image — an image chosen from the project Media Library.
How values are stored
When a content item publishes, each Custom Field value is written into the frontmatter under the field's key. The shape depends on the type:
fields:
rating: 5 # Number
is_featured: true # Boolean
published_on: "2026-06-01" # Date
category: "guides" # Select (one option value)
tags: ["news", "product"] # Multi-select (a list of option values)For Select and Multi-select, Acrosite stores a stable value for each option you defined, not the display label — so renaming a label later does not break saved items. See Generated Markdown and frontmatter for the full file shape.
Choosing a type
Pick the most specific type that fits the value. A Date field gives editors a date picker and a consistent format; a Select keeps values from a fixed list; Image ties the field to your Media Library so the image is committed when the item publishes. The right type makes the editor clearer and your published frontmatter easier for templates to read.
Field keys and required fields
Each field has a Field Key generated from its label, used as the frontmatter key. The label and key are protected after creation so existing content keeps publishing safely. A field can also be marked Required, which gates review and publishing readiness until it is filled in.