ideas
ideas copied to clipboard
Published
20 hours ago •
statamic
statamic
Allow for managing non-content blueprints in the CP
Say I create a bacon blueprint in resources/blueprints with all the fields etc. Inside an addon, or anywhere else, I can get that blueprint by doing Blueprint::find('bacon').
However, if I wanted to go and update that blueprint with a new field or whatnot from within the Control Panel, I can't. My new blueprint doesn't show up at all.
Ideally the bacon blueprint would show under the 'Other' heading and you'd be able to edit it like any of the other blueprints.
I believe this was how it used to work in v3 prior to blueprints being refactored a while back. I'm happy to have a go implementing this if it's something the gents would be interested in.
Related: #644
