There are times where we would like to modify the order of tags in a tag field, where we rely on the order it is given by Builder's content API. Right now, you need to delete and re-add in the correct order to achieve this. Drag-and-drop reorderin...
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...
Multiple previews for structured data models, without the visual editor
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...
Easier way for non-developer to create category/tag pages for blog posts on the Builder visual editor
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.
Have Tailwind CSS built into the Builder visual editor
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.
Ability to require a publish message, much like a git commit
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.
Ability to have branches, much like with git version control
It would be much easier to collaborate if something like git version control were added to Builder. This way, there would be less of a fear of overwriting someone's work or accidentally publishing something that isn't ready. It would be nice to th...
Ability to have conditional values based off of environment (QA or production), like a .env file in code
Similar to how you might have a .env in code to differentiate between the QA and production environments, it would be useful for the Builder editor to have the ability to do conditional values based off of the environment. For example, you might h...
Asset library should have the ability to be separated by environment
Similar to how I might have both a QA and production bucket in S3. Currently, assets are shared across environments. It would be useful to allow them to be separated by environment.
0
0