All ideas

Presently it is very easy to accidentally create typo variants of tags. Seeing a dynamic suggestion of exiting tags within the field as you type would help to alleviate that. I imagine that the candidates would be pulled from all of the tag conten...

Some content is best handlend as a structured data collection with no corresponding visual editor as there may not be a dedicated page, or the components are hardcoded if they do. It would still be useful to be able to see how that content will be...

It would be useful to be able to hide a set of fields based on the content of another field within models defined through builder's dashboard. This is possible with custom components by writing some code, but not for fields defined in the dashboar...

It's very disruptive to have to reapply pagination state when making mass edits to a structured data model for example.

As the title says. It is handy especially for structured data models to see the content of a few fields (say tags for example) directly in the listing in the content section. Even better if it is dynamically configurable like (or as part of) filters.

Creating categories/tags for blog posts is no easy task for a non-developer. There should be a simple way to do it on the Builder visual editor directly.

Creating pagination for blog posts is no easy task for a non-developer. There should be a simple way to do it on the Builder visual editor directly.

To prevent accidentally leaving unpublished edits to catch the next editor unawares, it would be helpful from a content editing experience point of view to prompt the user if they want to discard unpublished edits when navigating away from the edi...

Tailwind CSS is an amazing tool used for consistent styling. It would be really cool for non-developers to be able to use such a powerful tool like Tailwind directly on the Builder visual editor.

It could be useful to require a publish message, much like a git commit, to help understand why a publish was done. This way, it would be easier to understand the commit history, much like in git.