
I like the new History-Compare feature. Review collected by and hosted on G2.com.
Handling global elements and internationalization: Storyblok is increasingly being sold to customers with high demands. Customers primarily choose Storyblok because of its intuitive user interface, which is an excellent development. The problem is: Storyblok is extremely strong for simple pages, creating folder-based pages and filling them with content. Intuitive and simple. For this type of customer, Storyblok is becoming too expensive, as there are often very tight budgets behind it. Other customers with high budgets bring other challenges: creating and managing content centrally in one place, translating it based on field level, but otherwise continuing to maintain pages on a folder basis. We can build solutions for this, no question.
1. In the long term, I would like to see a more visible difference in the user interface between globally reusable content and page-based content.
2. Abolish the "default" locale. If no translation is maintained in a field, no content should be displayed. Field level translation is therefore almost unusable.
3. Introduce translations for block elements to be able to maintain different blocks (compare Contentful).
4. Create a simple history feature for the Growth Plus Plan as well. It doesn't have to be with comparison options right away, but for example, for campaigns - quickly restore the state of a page from day XY without maintaining the same content.
5. Feature request: Page versions, the aforementioned campaign example: The season is regularly changed on a page (Easter, summer, winter), the assets and settings are always the same. Currently, this is only possible with annoying copying of pages into archive folders. Review collected by and hosted on G2.com.