I’m using Strapi + VueJs for making a static website more dynamic for a NGO and it works like a charm !
The only issue I had so far is that the admin form customizations seem to be stored in the database instead of application files, so it’s not possible to replicate them easily between environments
I think a lot of people are missing the point of a tool like Strapi.<p>1. CMS experience for non-technical teams: marketing, product, content, etc.
2. Graphql api to avoid lock-in. Tomorrow you can take your data to AWS Appsync, etc
3. Ownership of the data: Contentful, Prismic, etc are great - but Strapi allows you to own the data. Even in its simplest form, its a sqlite file you can check in to git.
To summarise what makes this nice:<p>1. Define a schema in an admin panel.<p>2. Get a free REST or GraphQL API for CRUD operations and a nice role based UI to manage the data.
We evaluated Strapi (contentful snd others) for a headless CMS to power a web and mobile app.<p>In the end we rolled our own in Rails was much quicker and simpler than these off the shelf tools.
I'm surprised by the number of non-dev people that can create and edit YAML files on Github/Gitlab once you guide them around the interface.<p>Sometimes, they mess up the indentation, or insert a quote in a non quoted value, but the PR turns red and someone more expert can correct the issue in a few seconds.<p>They can even be impressed by some functionalities (whoa, reviews ! whoa, I can make a draft PR !)<p>Github is the cheapest headless CMS, try it first.
I gave this a spin a while back and the experience was really really not great. I created a new content type and tried to name one of the fields "ID," not knowing that an ID field is automatically added to any content type. Instead of throwing a helpful error, that not only crashed the running server but also made it impossible to restart the server until I manually deleted the offending auto-generated JS file for the type. A minor quibble, perhaps, but the first impression stuck and I haven't touched it since.
I've been looking at Webiny recently as I wanted a headless CMS that could be hosted as a serverless lambda to reduce costs.<p><a href="https://headlesscms.org/projects/webiny" rel="nofollow">https://headlesscms.org/projects/webiny</a><p>EDIT: there's also other headless cms solutions like Netlify CMS, see the list: <a href="https://headlesscms.org" rel="nofollow">https://headlesscms.org</a>
It's difficult to differentiate the products in CMS market. I use Contentful (which launched in HN 7-8 years ago) currently. Developer productivity is a solved problem already. Hitting a few buttons and getting an API is nice. Every other CMS has Rest and GraphQL APIs, nice docs for devs, etc.<p>What most CMS products miss is; in real world, a company spends a lot of energy on not just building software, but also operating with the tools they build. I haven't heard any love story about people who write content. Developers build their stuff quicker, editorial teams look at a screen that look completely irrelevant to their work. People hate their jobs and may quite because of the horrible UX experience CMS products deliver.<p>This is my feedback. As a developer, I'm not looking for another Schema-to-GraphQL generator. There are too many of those. Good ones and shady ones. Nobody would miss anything if somebody decided not to build another CMS competing with the existing ones today with slight differences.<p>The bigger challenge is to build something not just developers, but non-technical teams love.
So, it's like parse.com ( if anyone remembers it) but for content.<p>I would probably try if they have localisation support, CDN integration and search functionality.<p>It may be very trivial for developers to host static content but for non-tech guys who might want to change the content frequently, this is good.<p>Few years back I worked on a mobile app which will show some training material ( basically text ) to user but the content is updated every week, along with other functionalities. Content team used to share Excel sheets to organise content that needs to be shown that week. It was "fastest and clean" way at that time. If they had to change something, they would share another sheet with corrections. It created a big rift when we asked them to add another field in that excel sheet for additional content. Having something like this would have solved those issues.<p>Decoupling content with presentation is always a good idea
We tried strapi late last year but found some big deficiencies that made the editing experience subpar. Simple things like being able to order a list of foreign keys, you cannot do and makes it hard for using this for content management - not sure if this has been fixed yet. The editor was very buggy too.<p>Ended up just using wagtail.
Tried this out. It's a GUI tool for creating CRUD apis with authentication and authorization. It does the job but it's pretty clunky and heavy for what it is. You could probably get similar or better results with Postgres, PostgREST, and some GUI tool for Postgres like Postico.
We switched from Ghost to Strapi + Gatsby.js when we were facing limitations regarding i18n in Ghost. It works pretty well! Spinning up Strapi is a breeze when using a PaaS like Heroku.
is this a completely new version? I remember ghost and strapi blowing up in the node.js community couple of years ago with the promise of replacing WordPress, but haven't really heard of strapi since then. Now i see it supports not only Mongo DB, but postgres, mysql/mariadb and sqlite and that's very interesting. Did you replace the traditional node.js orm with a graphql server?<p>Am i missing something else? Why should i still use strapi today?
Strapi is a very promising piece of tech that enables great productivity and helps us with the data required for building sites using static website generators.
I've been testing it foir the past weeks, for my own portfolio. It has been an nice experience but the docs are not updated. I've been running into several walls because of this and my resources are searching for solution on the internet, which very often are described in issues on the Github repo. That's my only negative until now.
I've been using airtable to give a bit of dynamic content to an otherwise static site. The API has some limitations, though, like not being able to directly upload images.<p>As I prefer to self host anyway, might this be a viable alternative?
How are the training resources for editors using Strapi? One selling point of the more commonly used CMSs is that you can hire editors that already know it and there are companies that can help you train editors.
I have painful memories of building my own admin portal for a web site I built, and contained nothing that you don't get with strapi out of the box.
why so negative? what's wrong about quickly bootstraping simple api (hence the name "strapi", duh) for a mobile app or something you're working on?
Didn’t Python zope did it in 1990’s era. Looks like we are going back where we define content type (archetypes in zope/plone) and generate forms and content based on it.<p>Still plone does it much better than any of this headless CMS, why don’t people look at it for design inspiration rather than reinvent the wheels and do much worse job.