Repeater Field and Reordering for CMS fields

It's currently so difficult and messy to create workarounds for dynamic pages with differing items for clients in the CMS. It's so complicated that it's easier to create a new page for each collection page and tweak the template for each individual page.

This is all well and good if the client has budget to pay you to change it every time, however if you're looking to create a solution for your client that makes it easy to update and rearrange their projects, its really not that achievable with Webflow.


I feel a repeater type field, or even reordering of CMS fields would instantly make a huge difference to the quality of product you can create for clients.


This would really go a long way to making Webflow the only solution for a lot of agencies and as a result, more people converted to Webflow.

  • Build Digital Studio
  • Feb 7 2023
CMS
  • Stefanie Traidl commented
    27 Feb 04:38pm

    Yes


  • Martin Schwenzer commented
    27 Feb 04:35pm

    This lack is the major reason whenever we use a classic CMS over webflow.

  • Morten Bessesen commented
    13 Jan 03:31pm

    Yes

  • Brandon commented
    7 Nov, 2024 03:05am

    This would be incredibly helpful.

  • Rob Nichols commented
    6 Jan, 2024 07:52pm

    Please add this feature - it would make webflow the best tool available.

  • Mathieu Preau commented
    10 Nov, 2023 05:37pm

    Yeah I agree. Its a mess to create nested stuff. I'm forced to create several fields that I have to name (item 1 - title, item 1 - image, item 3 - desc). This is a dumb way to work.

  • Ramy commented
    12 Mar, 2023 10:35pm

    Agreed, crazy that this hasn't caught on yet but they're already thinking about making their CMS multilingual while they haven't even addressed the basic needs of a good functioning CMS...


    Repeater Fields are not a nice to have, it's a must-have, almost a necessity. Everybody would gain from Repeater Fields and it would speed up the workflow dramastically of almost all Webflow Users working on a CMS Website, while not everyone would gain from the multilingual CMS necessarily.


    Some food for thought.