on February 8th, 2020
I spent many months using the create collection wizard and something about it always felt awkward to me. It always looked nice, I couldn't ever decide on which fields should be part of the multi-step flow and which could be deferred until later. Each use-case I came at it with had a different combination of relevant and important settings.
By the time each use-case was accounted for, more than 80% of all possible settings lived in the wizard. Hardly "simpler".
If this was the only time you ever interacted with the settings, perhaps the wizard would be fine, but that's not the case. Each subsequent time you revise your collection's settings you see the manage collection screen, not the wizard. So what is the wizard doing, really?
So we ripped it out.
Part of the pre-launch process is making hard decisions. What makes the cut? It's much like the editing room of a Hollywood movie studio. Even good scenes hit the cutting room floor because they get in the way.
So we trimmed the create collection workflow down to the absolute bare minimum — the
handle — and then added two new things: a more useful "empty state" and a resource scaffolder.
Every time I create a collection I usually need to make a blueprint and a couple of frontend templates. I thought to myself "Self — what if that could be done for me automatically?" So now does. Or can. Or whatever the proper grammar is for an external/internal monologue.
As you can see, scaffolding will use the name of your collection to seed the name of your blueprint and frontend index and show templates. If you want to rename them, feel free, but either way click the button and you're ahead of the game.
I'm off to go fix other things that bug me or aren't quite finished yet before we launch. See you real soon.
Copyright 2020 Statamic