Jerome Chauveau is leading a team of passionate people that decided to try out Strapi. We had the opportunity to ask him a few questions about his experience with our solution. He tells us all about the project he’s working on within the IT department and how Strapi fits in. Find out more about his feedbacks and advice below!
We had to develop a fully functional training site in a 3 months-time (including alpha and beta-testing phases), dedicated to the IT department staff members, with a lot of content to produce and expose. Therefore, we wanted to spend as little time as possible to build the site backbone and the use of a headless CMS was quickly viewed as a necessity.
Our strategy was to let the people who have the technical knowledge decide, that is to say our developer teams. After testing the main headless CMS in the market and drafting POCs, the developers fancied Strapi’s ease of use, customization abilities and interface, so we decided to keep going with this solution for our new training site. The Node.js codebase was also a plus, for our backend is 100% Node.js. We knew it would be a real accelerator and we had to take that into account. The simple and uncluttered interface was in favor for Strapi as well, since we needed to have all site content contributors use it easily.
Strapi has turned out to be a great choice so far: technical setup was really quick, and in a few days we were able to have a drafted site up & running, leveraging Strapi main functionalities. Strapi simple stack (Node.js, MongoDB) made it easy to build CI/CD automation and infrastructure setup in AWS.
Just give it a try! It is simple to install and integrate with your site, so you can quickly see if it feeds your functional needs.
Strapi has turned out to be a great choice so far: technical setup was really quick, and in a few days we were able to have a drafted site up & running, leveraging Strapi main functionalities.
Sign up for the Strapi newsletter to keep up with the latest from the Strapi community!