While dividers are somewhat nice, could you explain why Figma chose that approach to solving a problem which is well described here (with visuals and with proposed solutions) ended up with dividers rather than grouping of pages in folders?
Yes, dividers makes pages a bit more distinguishable, but we could already achieve that with ---------- even though it was less pretty than actual dividers.
What is the reason to not give us what we’re asking for in terms of grouping pages in folders?
We hear you. Ultimately, it came down to the fact that dividers were a relatively lower lift to build and launch. As I mentioned, grouping pages and folders are still on our radar, but to be transparent, it’ll take longer for our team to launch.
@dvaliao thank you for taking your time to monitor our feedback and responding to it quickly 🙂 Very much appreciated.
This is something that the community have been rather vocal about for many years though, and I would question why such a fundamental feature has not been prioritized in the product roadmap for all of the years the community has been asking for this…
I completely understand. This request has been a popular one in our community since 6 months before I even joined Figma!
While my team here on the forum continuously hands off these popular feature requests, product teams have final control over what they want to prioritize and build. We have the most eyes on anything +750 votes, so considering that this feature is among the top 5 in the community - there is hope! 🤞
The new page dividers are nice… much better looking than the empty page approach many of us have been using. However, a simple horizontal rule lacks the context our former approach offered us. I would love to see nested pages in addition to these dividers to allow for cleaner file organization to communicate the context for the items in a given group of pages.
Figma doesn’t prioritize this feature not because they can’t provide this functionality of course, I assume they doing this to not encourage users to created nested treeeeees in files because they are not able to handle a good performance)) They can’t handle a good performance even now, not speaking of trees of pages with this potential feature
A better solution is to allow users to create another level of folders inside a project, that’s a good alternative
In large design systems like ours, managing hundreds of components is becoming increasingly difficult. The ability to group components by purpose or category and make them collapsible would be a game-changer, significantly improving organisation and usability.
Figma, we urgently need this feature. It was first raised back in 2021, and it’s crucial for supporting designers effectively. Please prioritise this enhancement to help streamline our workflows.