Visual Editor

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.

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.

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...

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...

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.

It would be extremely useful to have the ability for the asset manager to define permissions per file in order to restrict who can and can't view a file

We get quite a few requests from our clients to hide the option for "Inline text editing" provided by Builder.

It would be great to have a way to ensure that symbols on a page are all published before the page itself can be published, so that the page isn’t missing anything when it goes live. This could appear as a warning message ("This page has unpublish...

Most numeric custom css rules that we apply are `font-weight`, `order`, etc. We want a way to prevent the editor from adding the “px” suffix to these on every change.