With us currently being in the process of evaluating the headless CMSes on the market, a project like neolabs was a golden opportunity to actually try out at least one of them with a real (albeit limited in vision) use case.
In the end, our choice fell on Prismic, because... well, it seemed like a good fit at the time: There are several features that also seemed enticing for some other, bigger projects that we might want to plug Prismic in to as the data source at some time.
Of course, with neolabs being so limited in scope, we did not have an appropriate use case for most of Prismic's data model - which can be used to map much more complex data than what we needed by involving what Prismic calls 'slices'. Still, it was enough to get some first impressions what it's like working with this headless CMS.
Prismic also gives the ability to POST to a specified URL whenever content changes, which was perfect for us and our Netlify webhook integration that was mentioned in the previous chapter.
We did not have a whole lot of touching points with Prismic. All we did was create 'Singleton' content type for neolabs, filling it with the necessary strings (all content on neolabs.io, including the emojis in the headlines 😊, is managed there), and, creating another content type for the open source tools we wanted to display. That second content type of course was a repeatable type because we wanted to be able to add as many tools as we need.
Due to Prismic offering a npm package for integrating their API in Node projects, fetching data from the API during the build process of react-static was also pretty painless.