All ideas

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

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

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.

Currently, you can only achieve this via custom roles and this is would be a cumbersome process to achieve this idea, as you would need to essentially do the reverse and select all user roles that can have access to specific models. It would be ex...