I intend to use this blog (http://deliverystack.net) to describe my experiences using .NET Core and ASP.NET Core with SaaS headless Content Management Systems (CMS). I hope to present an unbiased assessment of the products specifically from the perspective of a .NET developer and to a lesser extent in the general context of CMS and web CMS, primarily focussed on Content Delivery.
From the outset I intend to focus on the following systems:
- Contentful: because it is probably best-known in the market (and because it was relatively easy to get free access). .NET SDKs: https://www.contentful.com/developers/docs/net/
- Contentstack: because I started this process with Contentstack and its Modular Blocks feature differentiates it from the others in significant ways; also (full disclosure): because they pay me when I am not blogging. .NET SDK: https://www.contentstack.com/docs/platforms/dot-net/api-reference/api/index.html
- Kentico Content: because of the company’s .NET heritage (and because it was relatively easy to get free access). .NET SDK: https://github.com/Kentico/kontent-delivery-sdk-net
While the volume can be a little overwhelming, the technical information can be light, and the sales slant can be steep, you can parse some useful information about SaaS headless CMS from various materials available from the vendors.
CMS Selection Resources:
I will try to update existing blog posts when I can. I always recommend reading an comments, which often point out defects and alternatives. Coding on a blog is like wearing underwear in public: both items are not meant to be exposed and deteriorate with age.
I recommend that you focus especially on the most important aspect of CMS: content modeling.
If you think that I should consider additional vendors or have any other feedback or suggestions, please comment on this blog post.
P.S. I have not taken the time to configure navigation in WordPress; I’m just dumping content here. I recommend that you start from the first/front/home page at https://deliverystack.net and use the links in the footer to navigate forwards through the posts.