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...
I love love love builder.io. Just set everything up and I already feel so much more productive than with contentful. The API documentation is amazing. I can't wait to get started with the page builder! For data models, it would be great if one cou...
Control over resizing algorithm when using Image Delivery API
We would like the ability to choose an alternate resizing algorithm (as you might do in photoshop when performing a downscale). Example options would be Nearest Neighbor, Linear, Bicubic, Lanczos etc.. Ideally we would have the ability to opt in t...
When creating a page that is served as a child node of some dynamic parent node.Given a management platform for events, the user may select on one page an event.When the user navigates to another view, say event-details, this will refer to the pre...
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.
