Would love if there was a way to save my preference of having the "viewing # of pages" stay on 300. (or 25, or 50, etc). Right now, every time I click into a Builder page then back to main page overview it goes back to viewing only 25.
By default, there is a master / main branch. A user can create a branch and can select a publish point in the history or just edit the current branch in the editor. During deployment, we can assign a specific branch. If a page does not have that b...
So when youʻd be in Builder, looking at your list of pages, you could see who last edited it (or maybe published). This way you could see it at a glance without having to open the page and go to history. Iʻve attached a screenshot of where I mean.
In the advanced mode allow my templates to appear instead of the default templates. Allow for a default template for a given Model type. So that my users always get our "post" type already pre configured for them to start writing.
Although inheriting state by default can often make it difficult to debug in situations where there are modals, pop-ups, or web components being used, other customers would still find this beneficial and time-saving. Perhaps the option could be av...
Ability to change the significance attribution for A/B tests
If a customer wanted to change the significance attribution for A/B tests to 1 day (vs 30 day), they would be able to control that at either the account and/or entry level
Fsat landing pages imrove your conversion rate and as a result your paid media (FB and TikTok) results. We need to be able to create super fast landing page for paid media campaigns.
pull custom actions from state/context into edit action UI
It would be great if there is a way to allow a UI designer to reference custom actions defined in state data to be passed to a custom component via a binding instead of having to use the custom code action editor. E.G. Using the multi-page funnel ...
When there is a plugin that uses a webhook like Algolia. If you change any part of the configuration, allow the user to see all of the webhooks that exist and delete any of the existing ones. Or place directions on how to access them within a model.