ideas
ideas copied to clipboard
š”Discussions on ideas and feature requests for Statamic
It would be nice, if we could use a dynamic folder name with the asset field type: Maybe something like `folder: {slug}`, to keep the asset container tidy and e.g....
There are currently two ways to achieve this: 1. Copy the asset URL from the container and then paste that into a plain nav item 2. Create a Pages >...
As with Statamic V2... it's very important to know how many times a tag or category is being used.
I am building some kind of "administrative" tool, with massive Fieldsets / Blueprints, tons of different Fields, that will have to be "Required". If I make them Required from the...
It would be really useful imho to be able to define if a User gets to be displayed in a User Field, either at the User level, or the Role/Group...
It's quite tricky to drag and order large field sets into in a replicator / grid field. Worse so in a grid because you cannot collapse sets. I had the...
It would be super useful to be able to define a "Blueprint" for a Collection itself (not for the Entries), a bit like Taxonomies That way, a Collection could have...
The Vite tag currently dosen't support Laravel Vite assets as shown here: https://laravel.com/docs/9.x/vite#blade-processing-static-assets. Proposed Usage ``
When specifying action fields it can be useful to know what items you're working with, in order to set default values on the fields. But at the moment the `Action::fieldItems()`...
Taxonomies are broken. There, I said it. I'm rooting for a complete taxonomy overhaul for Statamic 4. There are so many broken pieces, bugs, missing features, and conceptual issues about...