Item Style
Per-field display treatments — chips, currency, ratings, images, links, HTML templates — applied consistently everywhere a field appears.
#One renderer, every surface
A item style turns a stored value into display HTML. Assign one once and it applies everywhere that field appears: lens tables, cards, kanban meta, record pages, and the app's own collection tables.
Precedence, highest first:
- a per-column override in a specific block,
- the field's Display setting (Schema → field → Display tab),
- the project default for that field type (Lens → Display defaults),
- the built-in default.
Tip: set renderers at level 2 or 3 and leave block columns unconfigured — one change then updates every view.
#The renderers
| Renderer | Highlights |
|---|---|
| Text | Case transform (UPPER/lower/Title), truncation with ellipsis, prefix/suffix. |
| Number | Locale separators, fixed decimals, prefix/suffix (91 min). |
| Currency | ISO code formatting ($1,234.50). |
| Date | Short, long, relative ("3 days ago"), time, or date+time. |
| Badge | A pill; optionally colour it with the same rules as Chip. The enum default. |
| Chip | Value-driven colours: ordered rules (equals, contains, >, <, empty…) pick colour, label, and icon; first match wins. Multi-value aware — an array (or a JSON-array string like ["Drama","Crime"]) renders one chip per value. |
| Boolean | Check/cross with label. |
| Link | Clickable, with an optional fixed label ("Website") and same-tab option. |
| Image / Avatar | Renders the value as an image / round avatar. |
| Rating | Stars out of a configurable max. |
| Progress / Bar / Percentage / Sparkline | Numeric visualisations. |
| JSON / JSON tree | Pretty-printed structures. |
| HTML template | Author HTML with {{value}} and {{record.field}} placeholders — the one renderer that can compose other fields of the same record: <strong>{{value}}</strong> ({{record.status}}, {{record.views}} views). Values are escaped and the output sanitised. |
#Live previews
Wherever you pick a renderer (the field's Display tab, Display defaults, a table column) a preview renders against sample values — enum fields preview their real values, so chip rules can be checked before saving. Invalid configs are rejected at save time with the exact problem named.