Bring back the ability to nest items
Liberty-Belle Howard
I understand the benefit of folders for some projects, but for website build/maintenance projects, I need to be able to nest items underneath each other so that I can create content for landing pages (can't create content for folders) and show stakeholders an accurate sitemap (creating items for landing pages so that I can add content to them results in the landing page appearing alongside its child pages on the content map view)
Log In
Kristen Brown
I want to follow up on this issue because I think it's still very relevant and a persistent problem. If you're building out a website, the folder system is a huge pain to maintain and reduces access to the pages at a glance like they could when they were nested previously. I understand that some clients find the folder system useful for their needs, but I doubt those clients are using Gather Content to manage website content then. I think there can be a case for having both options. When I go to set up a project it asks what I'm building out and I click on website build. I'd like to see this revert back to the nested view. Articles, Documentation, Emails, etc, sure, those should probably be organized by folders. When we build out 200 - 500+ page websites, the folders are slow to load and hard to navigate to the page we're looking for.
Douglas Malan
Kristen Brown: Agreed. It's an absolutely clunky layout that is neither intuitive nor efficient.
Ed Williamson
We're still on the legacy version of GC and I've been looking today into a good time to upgrade. All our projects are site builds too. Carys Daroy has been really helpful in answering my questions and showing me how to demo the content hub, which I've done, but I've found the use of folders is going to make the experience much worse for us so we'll hold back on the upgrade until this has been addressed.
We will at the very least require the ability to view the whole hierarchy at once to be restored (have upvoted https://gathercontent.canny.io/feature-requests/p/bring-back-a-way-to-see-the-hierarchy-and-all-the-pages-at-a-glance for this) but ideally I'd like to see folders made an option not a requirement. (Even just in site build projects: I can see that for BAU update projects they'd make more sense.)
All of our pages contain content, so the necessity to create a folder for every page that has children, and then include the page itself in that folder, will be really counterintuitive and a backwards step I'm afraid. Sure I'd get used to it quickly enough but for my non-techy stakeholders it's going to be confusing and harder to use.
K
K Bates
Hi Liberty-Belle Howard,
Thanks for raising this.
With the folder sidebar, items are no longer nested on the page body. Folders can be nested in the sidebar though, to represent nesting in your sitemap.
We are also working on a way to see all of your sitemap (structure and content) on one page, which hopefully should help with this. Here's the suggestion that we're working on.
I do understand though that with folders and items having the same name (one has content and other doesn't), poses a challenge for getting an accurate sitemap. That's something for us to consider 👍
Thanks,
Kay