evenement collection drives a single agenda block reused on the home page and the programme page.(auto) so an editor opening the block sees at a glance which fields they fill and which the engine fills.{{ "Nothing coming up right now. Check back soon." | _ }}
{% endif %} ``` Two details worth copying. `c.maxItems | times: 1` coerces the number field to an integer so the comparison is numeric. And an empty agenda gets a real sentence: for a venue between seasons, that is the normal state of the page, not an error. ## 5. Show the date in the reader's language ```liquid ``` The `date` filter formats according to the current locale, so the same template prints `12 mars 2027` and `12 March 2027` with no branching. ## Pitfalls - **`limit` in the query is not the editor's cap.** The query's `limit` bounds how much data is fetched (100 here); the block's `maxItems` field is an editorial choice applied while rendering. Keep both. - **Filtering on `now` in the template does not work.** You would have to fetch everything and discard most of it, and pagination would be meaningless. The comparison belongs in the query. - **A `date` field cannot be split this way.** If you started with `date` and now need an upcoming/past split, change the field type to `calendar` before writing template logic around it. ## Serve the agenda as a JSON feed A template can answer with something other than HTML, and it takes one key. A page-type declares its response `headers`, and the template writes the body: ```yaml agendaFeed: name: Feed agenda (JSON) template: 'agendaFeed.liquid' headers: content-type: 'application/json; charset=utf-8' sections: main: tabsets: config: name: Source fields: upcoming: type: query label: (auto) Upcoming config: itemSet: evenement limit: 100 where: and: - '>=': '_occurrence.start': '{{now.datetime}}' sort: - '_occurrence.start': asc ``` Then one hidden page on that type — `state: active`, `visible: false` — and a template with **no `{% layout %}`**: a single line of chrome would break the document. ```liquid {%- assign origine = 'https://' | append: request.host -%} { "site": {{ globals.siteName | default: '' | json }}, "generated": {{ now.datetime | default: '' | json }}, "count": {{ page.custom.upcoming.size | default: 0 }}, "events": [ {%- for ev in page.custom.upcoming %} { "title": {{ ev.title | default: '' | json }}, "url": {{ 'evenement' | url: evenement: ev | prepend: origine | json }}, "start": {{ ev.date.start | default: '' | json }}, "end": {{ ev.date.end | default: '' | json }}, "summary": {{ ev.excerpt | default: '' | json }} }{%- unless forloop.last -%},{%- endunless -%} {%- endfor %} ] } ``` Two rules hold the whole file together. **Every value goes through `| json`.** The filter writes the quotes *and* escapes the content, so never type `"{{ ev.title }}"` by hand — one apostrophe in a title and the document is broken. Verified on Le Cinquième: a summary containing `s'invite` round-trips correctly. **Every value that might be absent goes through `| default:` first.** This is the sharp edge. A missing value renders as *nothing at all*, so `"key": {{ absent | json }}` emits `"key": ,` — invalid JSON, served with a 200 and an `application/json` content type. Nothing warns you; the consumer's parser is what finally complains. ### Three constraints worth knowing before you start **`sections` is required, even with no HTML.** A page-type without it fails validation. Declare one and let the template ignore it. **A slug cannot contain a dot,** so the feed cannot live at `/agenda.json` — that request is rejected at page creation with a slug validation error. Ours is at `/agenda-feed`. The `content-type` header is what identifies the response, not an extension, and every consumer that matters reads the header. It does mean a URL that looks less like a feed than people expect. **There is no site-origin variable.** `site.url` is empty, so an absolute URL is built from `request.host`, which is what the snippet above does. Feeds need absolute URLs — a relative one is meaningless the moment the document leaves the site./fr/agenda-feed and /en/agenda-feed return the same events with their translated titles — "Piano sous la lune" and "Piano Under the Moon". Two feeds, one template, nothing to declare. Publish the one that matches the audience, or both.