Default blueprint

[wm-simon]

It would be nice, to mark a blueprint as default, which will be loaded, when a new blueprint gets added. I often have a default blueprint with several tabs and imports. The other blueprints have the same fields like the default with additional fields.

[jesseleite]

What about using fieldsets for those reusable default fields?

[wm-simon]

I use fieldsets for nearly all. But our websites are mostly a little complex and we use normally about 4-6 tabs. Right now, that's what you have to do for every tab:

1. Add tab
2. Name tab
3. Click link fieldset
4. Chose fieldset
5. Confirm fieldset

This is just with 1 fieldset per tab. So you are about 20-30 clicks plus renaming, what could be handled with a default blueprint. My pages have about 8-20 blueprints, so in my case, it would save a lot of time.

[jasonvarga]

You could create a starting point blueprint yaml file, then whenever you want to create a new blueprint, duplicate that file.

[j3ll3yfi5h]

Similar issue here. Splitted one huge Collection in 26 smaller ones, but they should all use the same blueprint (which has different sections). There seems currently no solution, to just use the blueprint from the parent folder... Is that right?

[andjsch]

If it is the same blueprint, you could probably work around it by using symlinks if it's the same blueprint every time.

[j3ll3yfi5h]

Working with symlinks could work, you're right. Went for copy and paste for now... 🫣