After logging in to Scrivito, the user is presented with a dashboard for setting up one or more tenants to start projects – it’s as simple as creating a GMail account. All required parameters are preset with default values down to a complete example application. So it’s really easy to get started.
Introducing a new Content Management System to an enterprise used to be somewhat nerve racking. Decommissioning a legacy CMS usually cannot be done in one step. This is due to the strong vendor lock-in underlying traditional CMSs: The means by which content is delivered to the front-end and the website or web application are deeply integrated. Replacing them means having to reinvent the front-end and often the complete application. A CMS also hosts content for many systems all of which require reconnection to a new system. Migrating the content is not easy in practice due to hidden database structures. Sometimes, the only way to transfer content from system A to system B is to copy/paste it.
Decommissioning a legacy CMS is often a step-by- step project over a long period of time, requiring the old CMS to be held active and maintained.
While starting is really easy with Scrivito, one objection to replacing a CMS might be that starting is just a small proportion of the project. This is true. Other aspects are the deployment process, the development of the application or website, setting up integrations or the migration of data from other systems. Scrivito provides a complete pre-configured deployment process with well-known providers like AWS, GitHub and Netlify. It can be adapted, if required, but it runs out of the box. And because of its headless approach, transferring content can be automated with batch scripts. Scrivito also comes pre-configured and with great usage examples and documentation. Of course, it is supported by professionally trained and knowledgeable support staff.
This blogpost is an excerpt from the “Measurable Success” white paper. You can download it for free to learn about the 10 most relevant factors by which the success of a CMS can be measured.