Integration
Your own templates
If your templates render the header themselves, use the ViewHelpers. They work with either site set, also on a site
without fluid_. There are four, and which one you need depends on what you have:
| You have | Use | Why |
|---|---|---|
A record object: {record} in fluid_, {data} in a Content Block, a card of a collection | headliner:headline | It reads the tag, the layout and the mark for the page module from the record |
A row as an array (from a data processor such as database-) | headliner:headline.row | It makes a record of the row, so the heading is the one of a record |
| Values: a partial without a record, a fixed heading | headliner:headline.values | It sets the tag and the class from what you give it; edit says where the tag is edited |
| The rich text of a row as an array (from a data processor) | headliner:text | It names the record and the field in the headings of the text |
Important
Keep {record -> f: for the text. That is how
visual_editor finds the text to edit; with a plain
{data. the heading is still rendered, but visual_ cannot edit it.
The other pages of this chapter:
Records, rows and values
The three ViewHelpers for a heading, with all their arguments: headliner:headline, headliner:headline.row and headliner:headline.values.
Rich text of a row
headliner:text names the record and the field in the headings of the text of a row.
Child records
Themes and fluid_styled_content
Themes and visual_editor (Camino, themes with their own header) and fluid_styled_content, the header partial of the site set.