I’m sorry if this is a silly question. When setting up sites, I find myself often creating a series of section and page blueprints just to group/enforce child templates so the client doesn’t mistakenly select the wrong templates when adding subpages.
Say, for example I have a site with:
events
↳ event
podcasts
↳ podcast
articles
↳ article
...
Thus I create:
pages/events.yml and a corresponding Events page
title: Events
sections:
pages: true
templates:
- event
pages/event.yml
title: Event
fields:
...
and repeat accordingly for all types of content.
Is this the best way to go about this? Sorry if this is painfully obvious, it’s just something I find myself doing repeatedly and wanted to check if there was any better way as I often find myself with a blueprint/pages folder full of parent blueprints solely for restricting child blueprint selection.