All ideas

When migrating thousands of blog pages from another platform into Builder, it would be helpful if we could Select and Publish more than one page at a time.

It would be very useful to have access to queryParams in the toUrl function when building custom plugins. We are building a plugin that uses personalization that usually we include as queryParams so that users can change their state in the UI to t...

It is frustrating navigating the developer documentation. In our case, specifically for React custom components. Generally, the docs are hard to navigate and seem to change depending on the page. This is definitely one of the biggest frustrations ...

The idea would be to have a tool that can automatically extract all component prop types (React project) and convert them to valid builder inputs. It could be even a cli app, where you can go through each prop. Or just try to convert the most it c...

a working integration with sylius to visualise products on pages

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

When a collection page is targeted to a specific collection, the preview collection in the editor should match whatever collection the entry is being targeted to (similar to how this is done for product pages).

Some options for Builder blocks (columns, carousel, tabs, text, etc) are hidden behind advanced in the options tab. It would be great to surface these and remove the advanced section so options can be easily accessed.

When pasting text into a text block, the styles from where it is copied from are also transferred over. For those who don't want text styling copied over into Builder, it would be great if there was a setting to disable this.

Custom fields can be used to handle environments nicely, but a more first class and prescriptive workflow could be valuable