Client: {{ item.fields.client }}
``` In a list of the collection, each item is whatever your loop calls it: ```liquid {% for p in collections.portfolio %} {{ p.title }} — {{ p.fields.client }} {% endfor %} ``` A value nobody has filled in prints nothing. So anything that only makes sense when the value exists goes inside a plain `{% if %}` on that same value: ```liquid {% if item.fields.email %} {{ item.fields.email }} {% endif %} ``` Without the guard, an empty value leaves a button that does nothing. The AI writes the guard for you; it is worth knowing why it is there. ## Phone numbers A phone number is the one value a page shows in two shapes: the one a reader reads, and the one a handset dials. You only store the first. ```liquid {% if item.fields.phone %} {{ item.fields.phone }} {% endif %} ``` `| tel` takes whatever you typed and leaves the part a phone can dial — it keeps a leading `+` and the digits, and drops the spaces, brackets and dashes you put in to make it readable. So the number on the page stays exactly as you wrote it. It stops at the first thing that is not part of a number, which is deliberate: `0113 496 0000 ext. 2` dials the switchboard rather than a number with a stray `2` on the end. ## Links A website, a map pin, wherever people book — give each a field of type **link**. A link is the one kind of value that can fill an `href` on its own: `Book`, inside an `{% if item.fields.booking %}` like the email above. That is not fussiness about the others. A link is a value a page hands to the browser as an instruction rather than as words, and the platform only allows that where it can promise the value really is an address — which a link field can, because it checks what you type. A web address kept in a *text* field can be printed but never clicked, and using one as a link will stop your publish. A link fills an ``. It cannot load a script, embed a frame or send a form somewhere — a publish will say so if a page tries. ## More than one of something A gallery, the questions on one product, the people on one project: anything an item could have more of is a **repeater**. Each row has the same fields, and a short **key** that names it. A page loops over the rows: ```liquid {% for q in item.fields.faqs %}{{ q.answer }}
{% endfor %} ``` Never by position. "The first question" changes the moment somebody drags the rows into a different order, so publishing refuses it: ```liquid-invalid{{ item.fields.faqs[0].answer }}
``` Some values are made of parts — an address has a `city`, a picture has a `url` — and you print the part you want: `{{ item.fields.address.city }}`. A picture also has every part a page's own image has (`src`, `width`, `height`, `webp`, `avif`, `alt`), so the same `