Skip to main content
Question

CMS Improvement suggestions

  • February 4, 2026
  • 0 replies
  • 15 views

Den22

I use Figma Sites to build websites for companies. Overall, I like it a lot. Pages are easy to create, and links and effects work well with very little effort. However, there are some essential things that I currently miss.

1. Usability for non-designers

I build websites for clients or colleagues who need to manage the finished website but are not familiar with design tools like Figma.

There is currently a CMS feature, which allows text and images to be edited in a table. However, this does not work for all pages. I cannot find a way to make the homepage editable for other users.

Ideally, every element that should be editable could be connected to the CMS in such a way that other users can manage the site exclusively through tables, without interacting with the design canvas at all.

2. Quality of Life improvements

When I create multiple CMS collections, things quickly become confusing. There is no way to reorder collections, and I also miss the ability to create a folder structure.

It would be very helpful to:

  • Organize collections into folders

  • Assign different access rights per folder

Example:

  • Person A can access Folder A (e.g. Homepage, “About Us”)

  • Person B can access Folder B (e.g. Product pages)

  • Person C can access both

This would greatly improve collaboration with larger teams or clients.

3. Technical product pages are hard to build

Example scenario:

I have a table with 50 products, which should be split across 5 category pages. All pages share the same layout, but each product has different technical specifications that should be shown in a list next to the product.

Currently, as soon as categories differ, I need to create separate collections for each category. This becomes hard to manage.

Possible improvements:

  • Being able to duplicate an existing collection and simply rename fields

  • Even better: having one large product collection, where I can define

    • which category a product belongs to

    • which technical fields are shown per category (different number and names of fields)

    • If a field stays empty it should not be shown - right now it is shown empty

This would make complex, technical product pages much more scalable and maintainable.