3 ms·
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
by jacobr 6y ago
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.
- robertlagrant 6y agoIt's headless, so what're you going to train editors on? The API?
- aliswe 6y agoThe UI?
- pedrogpimenta 6y agoYou would train editors on... editing. It does have an interface so people would need to learn how to use it.
- thelittleone 6y agoTrue. Depending on the deployment scenario there could be some additional factors. For example, take a static site that runs on netlify. There is a hook on headless CMS save that triggers a build. The build is usually quick, but its not instant (like Wordpress for example).
- mweibel 6y agoUsually headless means that serving the content is done only through an API while creating content (and -types) is done using an admin interface. If you look at the docs of Strapi you see that this is the case for Strapi as well.
- dgb23 6y agoFrom my experience you have to do that anyway if you have a custom data model. Usually the administrators who are defining a CMS model are also the developers consuming it. Editors need to get trained in the CRUD interface of that model: the UI and the implications for the frontend. This is completely orthogonal to the CMS or whether it is headless or not. Strapi has an interface and semantics that are very clean and conservative, I assume for this reason. It being headless removes complexity and allows it to be more minimal and focused than a vanilla Wordpress installation, which can definitely help in that regard.