All ideas

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

Do you have any plans to support light boxes on pages? This is something that would be helpful when designing landing pages.

I feel like the side panel is a poor place to put Options/Fields. There are some scenarios where I have deeply nested fields (see attachment). The UI becomes progressively more difficult to use since the real estate for fields shrinks. Two solutio...

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

Would be great to be able to download a PDF or image file of heatmaps for various pages to share with stakeholders across the company

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.