Static item in a fs-list within an fs-list

Description

We have a fs-list with inside another fs-list. The second layer fs-list needs to get a static item on the first position. We have followed the steps, but think the 2 different fs-list items might be a bump in the road for the static item to be placed in the second layer fs-list.
The tag with “opinie” should be placed in front of the white tags inside the image frame.

Site URL

Required: Please provide a staging/production URL where we can see the issue

Expected Behavior

The tag with “opinie” should be placed in front of the white tags inside the image frame.

Actual Behavior

The tag stays where it is in the structure and is not placed inside the second layer fs-list.

NDA Notice: If you’re under an NDA, please feel free to send us a Direct Message/Email with the above information.

Hey @studiopiraat!

There are actually two things working against you in your current setup.

First, the static “Opinie” tag with fs-list-element=“item” is placed inside the nieuws--top div, which is a sibling branch to where your thema-tag--list lives. Since it’s not within or adjacent to the inner list, the library can’t reliably scope it to the correct list.

Second, your inner thema-tag--list has no fs-list-instance at all. Your outer list already has fs-list-instance=“thema”, but when there are multiple elements with fs-list-element=“list” on the page, instances are what tell the library which list is which — and which list a static item belongs to.

Here’s what we’d suggest trying:

  1. Add a unique fs-list-instance to the inner thema-tag--list, for example:
fs-list-instance="[your-unique-identifier]"
  1. Add that same value to the static “Opinie” tag:
fs-list-instance="[your-unique-identifier]"
  1. If Webflow’s structure allows it, try moving the static item so it sits directly inside thema-tag--wrapper, closer to the list it’s targeting.

To be upfront — this specific pattern (a static item targeting a nested inner list inside a parent CMS list) isn’t explicitly covered in the docs. The steps above follow the documented behavior for scoping multiple lists via instances, but your nested setup is quite unique and there may be constraints we’re not fully certain about. :thinking:

If these steps don’t get you there, we’ll loop in a team member who can take a deeper look. :folded_hands: