What is Reddit's opinion of
Storyblok?
From 3.5 billion Reddit comments
15 reviews of this app found across Reddit:
I would recommend taking a look at StoryBlok (https://www.storyblok.com/) - their component/live visual editor works really nicely for page building and gives a whole bunch of flexibility that is way harder to achieve with Prismic/Contentful, plugins are also really easy to make and integrate compared to how I found Contentful’s app ecosystem - for more clear structured content though I think Contentful/Prismic probably have an edge.
I generally prefer Blade but have briefly looked at Inertia, mainly as a way to add more reactivity to pages or improve page transitions. I think it really depends on what you’re building.
I prefer the syntax in Blade, still feels odd adding attributes to ‘html’ for loops and logic. I also like idea of rendering once and caching it, rather than every client device rendering.
I make a Laravel package for the Storyblok headless CMS (most people use it render static sites in JS I think). It will resolve Blade files based on their names matching components in the CMS. Sometimes however I want to use the JSON data from Storyblok in a Vue component rather than passing it through my package where it get transformed. For this reason I have started to look at Inertia for rendering - I can either pull data in via Laravel or JS. Sadly not had much time to experiment with it yet.
I concur with what has been said already. The JAMstack approach and implicitly headless CMS is the future. For one, the headless CMS acts like a content repository, you make changes in one place and it applies to all the channels and platforms you are using. Of course, there are a tone more benefits that come with it.
There are some good options on the market, and since everyone is plugging their favorites, here is mine: Storyblok. It has a real-time visual editor, an internal asset manager and integration with Cloudinary, and I believe they handle the content creation, editing, management and publishing in the best way possible (eg. you can edit images by adding parameters to the URL).
Of course, you should do your own research and take an informed decision.
One last thing to take into consideration: Since last year, EU ruled that cloud services hosted in the US are incapable of complying with GDPR and EU privacy laws. Any business operating a website in the EU or has traffic coming from EU visitors, needs to know what data it captures and where that data is stored. (google Schrems II)
Hey, take a look at Storyblok and its visual editor or TinaCMS. Both aim to have a great visual editing experience.
Tina is open source and works best with Next.js but it should be possible to connect it with Gatsby.
Basically a headless CMS is a backend for storing content etc. and you connect to it via API. It has no frontend, so you can use whatever you want for the frontend, react, svelte etc.
Check this out: https://www.storyblok.com/tp/headless-cms-explained
It is not quite clear to me what you mean by they own your content. From storyblok.com/terms
> 5.4: Customer Content. As between the parties, the Customer > Content and Customer Applications will be owned by you (or, if > Customer is an agency, Customer’s client(s)). You hereby grant to > Storyblok a non-exclusive, worldwide license to copy, distribute > and use Customer Content only in connection with providing the > Storyblok Services.
So depending on the Storyblok Services definition it seems that the content is owned by the customer.
> “Storyblok Services” means the SaaS-based content management and > publication services, programs, functions and platform provided by > Storyblok to you (...), and subsequent updates or upgrades of any of > the foregoing made generally available by Storyblok.
The service definition is provided to you (the customer); so this part also sounds to me, that they do not plan to offer the customer content to other parties.
Could you elaborate what you mean they own my content?
It seems like you think that only wordpress has the ability to content edit or add new sections to pages? - This isn't limited to wordpress.
The large custom sites I have been a part of building have used either StoryBlok and Statamic, each have the ability for their content editors to drag and drop components that have been custom created for them with a live ui site.
Most of the time in these large companies the content editor isn't a designer, so can't be trusted to make something that will keep within their branding and design guidelines. So they can pick and choose from custom build components to build their page with.
I’ve used Storyblok (https://www.storyblok.com/) with Gatsby and it’s fantastic. It’s headless, has live preview capabilities, and its entire architecture is built around components, so it’s a great fit for React. They also have starters and solid docs for many frameworks, Next included (https://www.storyblok.com/tc/nextjs).
Used Storyblok for 2 projects this year. Pretty good experience so far.
Works well as a normal headless CMS where youre just calling an API and using the data. Or you can name your "bloks" and components to be the same so your frontend framework can dynamically load the right components https://www.storyblok.com/tp/nuxt-js-multilanguage-website-tutorial
Nested components did feel a bit clunky but it's pretty much the same as WordPress ACF repeater field.
It has an (optional) image compression service which I used with nuxt-img but it did was a bit too aggressive.
All in all, I think I had more problems with Nuxt than Storyblok in my projects.
If you are happy to design/write the components yourself, Storyblok has a really good live page editing experience for a CMS, https://www.storyblok.com also allows for writing plugins for the editing experience which means you can connect the editor with APIs or other data sources for some really cool dynamic editing options!
from storyblok site
> A headless CMS is a back-end only content management system (CMS) built from the ground up as a content repository that makes content accessible via a RESTful API for display on any device.
https://www.storyblok.com/tp/headless-cms-explained
It's basically just a backend app that spits out data. It's up to you to implement the frontend.
> but I realized I'm not after a headless CMS - I actually need a frontend helper to help me structure content on the website visually
So there's multiple conflicting requirements here. Firstly, why don't you want a headless CMS? They are quite literally the future, and will make life much easier for your frontend dev that you are looking for.
When you say "frontend" most people will understand that to mean a dev with that will have (among other things) skills with JS frameworks and of course HTML, CSS etc.
> - I'm not into HTML and I don't want to get in there either
Then you definitely want to leave that to the frontend dev and don't want to hamstring said dev by forcing them to use MVC/Razor crap.
The point of a headless CMS is to isolate the content from how it actually looks and is used on in your app. You essentially get back JSON from it's API (or via your own proxt API) that your frontend then uses to construct the UI.
This is 100% easier then trying to get a frontend dev to instead work with HTML responses from MVC.
> structure content on the website visually
Most decent headless CMS's have an editor that you use to make the content and then that is returned as JSON.
On that note I suggest:
Sorry for the rant but if I see someone picking Umbraco because they haven't been informed of better options I'm going to cry.
You can also look at StoryBlok, it comes with both Vue and Nuxt modules that lets you preview changes to your content in real-time. Have a look here for more info.
This does what you’re asking for. I’ve started using it pretty heavily for a few different projects. You get the visual page builder and can build the components in React or Vue or whatever you like. It’s really affordable and has great documentation and examples as well. It pairs extremely well with both Gatsby and NextJS for react and they have documentation on how to get started with those libraries as well.
I might try Storyblok + Gatsby. Stumbled upon this CMS while watching videos about Vue. Their CMS is supposed to work well with the component approach, they're from Austria (German support if that matters to you or your German clients).