It amazes me what can be done out of the box, I’m from a front end side so routing is not my strong suit, but this helps a lot. Thank you.
Still however, a specific ‘sections’ content type (besides files and pages) with automated routing (folders can start with a #) and specific blueprints/snippets would be a great addition.
Mainly because now the blueprint folder specifically will become somewhat messy* (and sections could use their own default). Also for clients the distinction between inline sections and child pages would become more clear. And if I’m not mistaken, there needs to be a route for each section template.
* I’m talking about several articles - like case studies - which are one pagers, yet part of a larger system which soon ends up with a plethora of blueprints and templates.