You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm evaluating Sanity as a headless CMS at my current job, and one of the first things the marketing department gave as feedback was the risk of drowning in all the individual schemas, which currently are listed all below each other (and we're just getting started on a not-even-that-big-project).
Sanity could take inspiration from what e.g. Nuxt/NextJS do and provide file-based routing inside the schemas/ folder, at least by default or as configuration option? IIRC there is a way of building this yourself using React, but akin to #3871 this feels like a dearly needed improvement to make Sanity a feasible choice for medium/large projects 😎
Also not sure whether this brings implication akin to #1358
Here's two screenshots of the current small-scale setup which potentially makes the problematic more understandable:
The text was updated successfully, but these errors were encountered:
This is possible @pascalwengerter but requires fiddling around with the structure builder which is tedious and not a very user-friendly syntax - I often have to do this to group things like global settings and sitewide structures like the below screenshot. So although possible, your suggestion of using a 'nuxt like' directory structure approach is a great idea and would make doing so much easier!
I'm evaluating Sanity as a headless CMS at my current job, and one of the first things the marketing department gave as feedback was the risk of drowning in all the individual schemas, which currently are listed all below each other (and we're just getting started on a not-even-that-big-project).
Sanity could take inspiration from what e.g. Nuxt/NextJS do and provide file-based routing inside the
schemas/
folder, at least by default or as configuration option? IIRC there is a way of building this yourself using React, but akin to #3871 this feels like a dearly needed improvement to make Sanity a feasible choice for medium/large projects 😎Also not sure whether this brings implication akin to #1358
Here's two screenshots of the current small-scale setup which potentially makes the problematic more understandable:
The text was updated successfully, but these errors were encountered: