All ideas

Currently there are options to link/unlink and sync content in bulk. This ability doesn't exist for models. We just started using builder.io and we already have 3 environments and 15+ models and growing. Performing this action manually one-by-one ...

Similar to a database, it would be nice to have a UUID field for CMS data models

Renaming inputs is currently a painfully awkward process since it takes quite some time for caches to update before those new names become available for use in the UI which is needed to have confidence that you're doing the right thing when updati...

For CMS data models on Builder, you can currently only manually change the order. There's also the ability to filter by field type, but you can't sort by field types

If you have filters set (or not), you can only see 25-300 pages at a time, it would be really useful to know what the total number ise.g. `viewing 1-25 of 532`

Right now assets can only be categorized in the Asset Library in Production (Main). We stage all of our content on a Staging branches, so it's more work to go to production to categorize assets and then go back into Staging to use the assets

Similar to Strapi, it would be nice to be able to self-host the data models.

Currently you can support standard non typed versions of defineProps, such as defineProps(['prop1', 'prop2']) <-- supported in builder sdk in typescript, you would define them as defineProps<{ prop1: string, prop2: number }>() <-- not ...

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

Block publishing pages with the same target attributes. If there is already a page with exact same target attributes editor shouldn't let content editors publish the page. For example only if only Url target attribute is present and another page w...