I’m evaluating Strapi for a pretty large site and can’t seem to find a good answer for this. Most of the content team is non-technical, so a good UX here is critical.
I know this has been discussed a few times (like here), and that this an old thread, but I’d like to interrogate this a little. I’ve read how I might be able to solve the slug problem thanks to this guide) and recognize you can handle the parent/child data modeling using a relation field.
While I understand how I can get this to work when querying from the frontend, I still find it difficult to understand the relationship of content from the “list view” in the Strapi admin.
Taking some concepts from the issue linked above, Wordpress, for example, displays parent/child relationships right in the list view (image attached). This makes it easy to see the relationship of content from a top level view and make adjustments informed by that structure. Being able to modify that structure directly from the list view (via “Quick Edit”) is also much easier and makes a lot of sense in that context.
All that to say, I do think there is some value to being able to control the slug structure from the CMS by using parent/child relationships. I understand that the routing won’t always match 1:1, but IME non-developers are the ones who tend to control the site structure and rely on that control for things like logically grouping content and SEO.
Curious if there are any suggestions or examples of how folks with large sites have approached this. Thanks!