A loop means “do this once for every item.” For a blog index, you want “for every blog post, show a title, excerpt, and link.” That’s exactly what a loop does.

Listing all blog posts

Example:

<h1>Blog</h1>

{for each entry in 'blog'}
  <article>
    <h2><a href="/blog/{ slug }">{ title }</a></h2>
    <time>{ date "F j, Y" }</time>
    {if entry has excerpt}<p>{ excerpt }</p>{endif}
    <a href="/blog/{ slug }">Read more</a>
  </article>
{endfor}

• 'blog' is the collection handle (the same one you see in the admin). Use your own, e.g. 'products', 'team', 'pages'.
• Everything between {for each …} and {endfor} is repeated once per entry.
• Inside the loop, { title }, { slug }, { date }, { excerpt } are the current entry’s values.
• The link href="/blog/{ slug }" builds a URL like /blog/my-post-slug so each post links to its detail page.

Listing with a limit (e.g. “latest 5”)

Some setups let you limit how many entries and how they’re sorted. For example:

{from 'blog' get entries limit=5 sort="date:desc"}
{for each entry in entries}
  <article>
    <h2><a href="/blog/{ slug }">{ title }</a></h2>
    <time>{ date "F j, Y" }</time>
  </article>
{endfor}

Or the loop might accept parameters directly, e.g. {for each entry in 'blog' limit=5 sort="date:desc"}. Check your admin Help or templating docs for the exact syntax.

When there are no entries

If the collection is empty, the loop block usually doesn’t run, so you see nothing. To show a friendly message:

{if 'blog' has entries}
  {for each entry in 'blog'}
    …
  {endfor}
{else}
  <p>No posts yet. Check back soon!</p>
{endif}

See Conditionals for more.

Looping over tags

If an entry has a Tags field and you want to show each tag:

{for each tag in tags}
  <span class="tag">{ tag }</span>
{endfor}

Exact syntax may vary (e.g. {for each tag}). Use the same idea: loop over the list, output one element per item.

Looping over a gallery

For a field that holds multiple images (Gallery type):

{for each image in gallery_field}
  <img src="{ image }" alt="">
{endfor}

Again, the exact variable names depend on your version; see Media in templates.

Important

Loops typically show only published entries. Drafts are usually hidden on the public site (and may appear only in preview mode if your setup supports it).

Collection groups

Use the collection_groups tree to build navigation, sitemaps, or sectioned index pages that match the admin Content overview. The client loads the tree from the public API when your template references collection_groups.

Top-level groups

<nav aria-label="Content sections">
  {for each group in collection_groups}
    <section>
      <h2>{if group has icon}<span>{ icon }</span> {endif}{ name }</h2>
      {for each slug in group.collections}
        <a href="/{ slug }/">{ slug }</a>
      {endfor}
    </section>
  {endfor}
</nav>

• collection_groups is the root array from groups.json (max depth 3).
• Inside the loop, { name }, { id }, and { icon } refer to the current group.
• group.collections is an array of collection handles (strings). Loop with {for each slug in group.collections}; { slug } is the handle for link paths and {for each entry in '…'} loops.

Nested subgroups

{for each group in collection_groups}
  <h2>{ name }</h2>
  {for each child in group.children}
    <h3>{ child.name }</h3>
    {for each slug in child.collections}
      <a href="/{ slug }/">{ slug }</a>
    {endfor}
  {endfor}
{endfor}

Use dot paths (group.children, child.name) when you need a parent field inside a nested loop. The special ungrouped group has no children; skip it in public nav with {if group.id != 'ungrouped'} if you only want named sections.

Combining groups with entry loops

List entries under each collection in a group:

{for each group in collection_groups}
  {if group.id != 'ungrouped'}
    <h2>{ name }</h2>
    {for each slug in group.collections}
      <h3>{ slug }</h3>
      {for each entry in slug}
        <a href="/{ slug }/{ entry.slug }">{ entry.title }</a>
      {endfor}
    {endfor}
  {endif}
{endfor}

Exact syntax for looping entries by a variable handle may vary by client version; when supported, {for each entry in slug} uses the current slug value. Otherwise fetch entries per collection via {from 'blog' get entries} style helpers or the public API.

See Collection groups for the data model and API.