Unwilling to expose ourselves to unnecessary risks - we decided to pass on Keystone.js as well. Unfortunately, we saw that the active maintenance was at a stand-still, with version 2 being in sort of limbo, waiting for active maintainers, and version 3 is still nowhere in sight. You had more control over writing your RESTful API endpoints, and the community around it seemed to be bigger. It was just as easy to create content types in Keystone.js, as it was in Strapi. The biggest issue, however, was that writing in this framework proved to be unstable on Windows platforms.Īfter we hit a wall with Strapi, we gave Keystone.js a try. Building content types took only a couple of minutes (that is, of course, if you know your way around the toolset). The developer experience was not bad either. We gave both of these frameworks a try and decided to proceed with Strapi because it had a smoother and more user-friendly admin interface. SolutionĪ few choices seemed to stand out, most notably Keystone.js and Strapi. And since we decided to build the complete front-end with JavaScript, the easiest solution seemed to go ahead with Node. On our previous website, we used WordPress which wasn’t sufficient enough for our needs. What we didn’t think would prove to be so difficult was the selection of the right CMS for our back-end. Since we mostly do Microsoft-related development, we decided to use Azure as our cloud provider. We wanted to use React as a framework for our interface, which also required choosing the correct tools and architecture to go along with it. The idea was to redesign our website and expand our portfolio with bleeding-edge technology.
0 Comments
Leave a Reply. |