Storyblok
StoryblokReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
525 reviews
from
External reviews are not included in the AWS star rating for the product.
Amazing value for money, however content reusability is a major issue
What do you like best about the product?
Great Pricing! It is actually affordable for small businesses
Components are generally quick and easy to put together
Compiling content is simple and intuitive for the most part but not very reusable (the biggest issue for me)
Components are generally quick and easy to put together
Compiling content is simple and intuitive for the most part but not very reusable (the biggest issue for me)
What do you dislike about the product?
Reusable components in content desperately need to be implemented, and the current nestable/global types that need to be added to related key through API sucks.
Currently I need to manually copy content across multiple pages, which is a nightmare when it needs to be updated...
Presets are cool, but only when creating; why can't I update the preset to all instances where I used that preset???
API documentation could be better.
Currently I need to manually copy content across multiple pages, which is a nightmare when it needs to be updated...
Presets are cool, but only when creating; why can't I update the preset to all instances where I used that preset???
API documentation could be better.
What problems is the product solving and how is that benefiting you?
We are replacing Statamic with Storyblock as our CMS for our frontend and with ALMOST EVERYTHING it does a good job as a simple, easy-to-use CMS for the marketing team to interact with.
However I currently end up needing to manually copy content across multiple pages, which is a nightmare when it needs to be updated...
Presets are cool, but only when creating; why can't I update the preset to all instances where I used that preset???
However I currently end up needing to manually copy content across multiple pages, which is a nightmare when it needs to be updated...
Presets are cool, but only when creating; why can't I update the preset to all instances where I used that preset???
User and Developer Experience is delicious.
What do you like best about the product?
A Headless CMS with a visual editor experience for your custom built components.
What do you dislike about the product?
Storyblok does not yet offer a module preview. When you have a large amount of useable modules you are not able to remember all of them. (How the look/feel). This of course is fixed in Storyblok V2 with "Module Preview Images".
What problems is the product solving and how is that benefiting you?
With Storyblok it is possible to quickly create/model a JSON Storage/Content and provide it seamless to every technology either frontend or backend applications.
Recommendations to others considering the product:
Among the headless CMS market, Storyblok is the best choice if you want developer and user (non technical) experience at the same time.
Storyblok changed how I look at CMSs
What do you like best about the product?
Storyblok's visual editor is revolutionary. Never it has been easier for developers and content editors to use a CMS.
What do you dislike about the product?
Storyblok works well. However, the documentation could be better sometimes. I know Storyblok is working to improve this.
What problems is the product solving and how is that benefiting you?
Creating a website + CMS that works for both developers and content editors.
Storyblok is the final piece of the Jamstack puzzle!
What do you like best about the product?
It's live preview and customisable Bloks have allowed us to present editors with their content in real-time. The custom field plugin allows developers to create their own integrations in the CMS! Storyblok also compliments Next.js perfectly well and we have the choice to either pull data at build or fetch in real-time giving us the choice of SSG, SSR or ISR.
What do you dislike about the product?
Documentation could be more in depth and contain more examples.
What problems is the product solving and how is that benefiting you?
The live preview has helped Content Editors deliver reusable content more efficiently and has solved the last issue around which CMS to use with Jamstack. Custom Fields allows us to integrate data from other API's into our content and it
Recommendations to others considering the product:
If you are looking at JAMStack then Storyblok will provide a fast, reliable and scalable solution for your web build.
Storyblok enables us to use the perfect process to publish content to our potential customers
What do you like best about the product?
Content Editors will not only create the content, they will model the content before. That way they take away a lot of work from the developer and you will build your content "model first", together. Your model is immediately validated from content editors and business people, before you even begin to implement it.
Completing the process is just a matter of shoving the model into a nice looking template.
Completing the process is just a matter of shoving the model into a nice looking template.
What do you dislike about the product?
Sometimes you got to start on a blank slate, and this can lead to a little bit of writers block. At least in the begining, you need to teach story blok to your editors and work together with devs on modelling and the process. But this pays of 1000% !
I can't find much more negative then this.
The php SDK could have higher quality. The richtext-resolver-SDK (php) could have higher quality.
I can't find much more negative then this.
The php SDK could have higher quality. The richtext-resolver-SDK (php) could have higher quality.
What problems is the product solving and how is that benefiting you?
Before we had to: a) create a model, b) create the template, c) create forms for the model to be filled by the content editor) e) actual fill it, f) use the filled model to show the completed page.
This process had major drawbacks: the model needed to be created by the developer, before the content editor could start to fill it. Large chunks of work had to be done before the model was validated by the content editor - and was so often wrong.
History repeats, when changes need to be made. This made a-e so slow.
With storyblok you combine a-e to a collab between editor and dev and you will find your model - already filled with content/data! so quick...
Last step - implementation - is then only a piece of cake
This process had major drawbacks: the model needed to be created by the developer, before the content editor could start to fill it. Large chunks of work had to be done before the model was validated by the content editor - and was so often wrong.
History repeats, when changes need to be made. This made a-e so slow.
With storyblok you combine a-e to a collab between editor and dev and you will find your model - already filled with content/data! so quick...
Last step - implementation - is then only a piece of cake
The only headless CMS you will ever need
What do you like best about the product?
The product is super easy to use, and the simplicity of connecting your own components to the platform is incredible. You can give the marketing / management / design teams super powers to create and manage pages.
What do you dislike about the product?
The approval flow needs rework, it takes a while to understand how it works.
What problems is the product solving and how is that benefiting you?
We used them for two things:
- Manage a bank application in multiple languages
- Launch several landing pages (also in multiple languages)
Storyblok solved our issue with the management team that wanted to have full control over the content and also the page.
- Manage a bank application in multiple languages
- Launch several landing pages (also in multiple languages)
Storyblok solved our issue with the management team that wanted to have full control over the content and also the page.
Recommendations to others considering the product:
If you are looking to have a platform that will offer you full control over what your application looks like, that's what you need. In ou main website, for example, is a simple Next.js application, consisting of two files: an index file and a generic file ("[...page.tsx]"). We have a design system in place where we connect to Storyblok, after all the website application is nearly 300kb in the end.
An easy-to-customise headless CMS for start-ups
What do you like best about the product?
Storyblok makes it easy to quickly build sites with completely custom UIs, and allows you to define customisation at whatever level of granularity you want. It is very cost effective relative to alternatives such as Contentful and is better geared towards design rather than data entry (as Sanity is, for example).
What do you dislike about the product?
Internationalisation is not trivial and the APIs for handling multi-lingual content aren't ideal. The UI is also not really designed with translation in mind and it is hard to do an external round trip as well.
What problems is the product solving and how is that benefiting you?
Storyblok allows us to have a completely custom static site, built in house, but that is easy for marketing to make changes to. We've designed our own content structure of sections and blocks to allow them a lot of flexibility while still providing a look that feels like it has been coded from scratch.
Built for developers and editors alike
What do you like best about the product?
The editor's user experience with Storyblok is flawless. Integration was easy for our developers to achieve.
What do you dislike about the product?
Nothing in particular, some minor features are missing, like rich links (allowing for javascript attributes).
What problems is the product solving and how is that benefiting you?
Help create SEO-relevant content that can be integrated into our eCommerce store. The headless, API-based approach makes for reusable content and easy integration.
Recommendations to others considering the product:
Use a component library like storybook.js for your frontend components.
Storyblok does everything correct!
What do you like best about the product?
it has a large FAQ section and the high customizability is a big pro
What do you dislike about the product?
none so far that I have explored in my interactions
What problems is the product solving and how is that benefiting you?
Using it for Nuxtjs frontend in my work and personal projects.
A product that makes both marketing and developers happy
What do you like best about the product?
- It's ridiculously easy to structure your content logically
- Content types and hierarchies
- easy to use for non techy types
- super extensible
- supports multiple content formats
- will make your marketing team happy
- developers enjoy it too
- great built in security
- Content types and hierarchies
- easy to use for non techy types
- super extensible
- supports multiple content formats
- will make your marketing team happy
- developers enjoy it too
- great built in security
What do you dislike about the product?
As a developer I do wish certain features for power users were more readily available, or that we could perhaps set up more powerful content rules and have the tools in the app to enforce them.
What problems is the product solving and how is that benefiting you?
Delivering top-quality content to various different channels in a unified manner.
Using it as a headless CMS for my clients(Freelance web developer/designer)
Using it as a headless CMS for my clients(Freelance web developer/designer)
showing 391 - 400