From one of our customers: It would nice to use custom components for the elements created in the rich editor. As example you could take a reference from this Contentful library @contentful/rich-text-react-renderer - npm
DeepL is a great tool to translate your pages into a different language. It would be great if you could use DeepL within builder to auto translate your pages. You would just hit a button translate, choose your language and then DeepL would transla...
In working with pages, it would be nice if there was an indicator on the Entries page to show that there are unpublished (saved) changes per document/symbol. It could be as simple as a little dot, or an asterisk prepended to the page name.
Add canonical URLs for organizations, models, content
URL handling in builder is largely dependant on internal state of the web app. For users that belong to multiple orgs, or frequently edit multiple models it would be very helpful for the current URL to capture that state (the org, the model), and ...
Twice this week i've been asked if Builder can override a site's global style sheet, specifically when they need to change a Heading 1 (for example) globally and they want to do this from Builder. I know we don't offer that yet, but just wanted to...
JSON View - either allow for word wrapping or make the JSON View pane able to expand to full screen.
As I've had to work a little more in the JSON View for editing those things that just can't be edited in the Visual Editor, I've felt a lot of pain in how relatively small the JSON View is. I appreciate that typically you want it to not cover your...
We want to fire a web hook whenever an admin user “Requests to publish” content so that we can build a slack integration to notify the users tagged that a page is ready for review.
Query filters are great, but let's be honest, if someone builds the user facing functionality, it usually means the search bar need to be as "smart" as possible. Having the ability to filter the content in a fuzzy way would imo add a lot of value
Default Map text fields to be longtext (render as textareas)
When working with Map custom inputs, either in Symbols or in Content Models, the default input box is a simple input field. This would probably be fine if the majority of editing on these fields didn't happen in the narrow sidebar, but because tha...
0
0
