delivery-sdk-net VS boilerplate-net

Delivery SDK

AppVeyor offers features such as .csproj files patching and AssemblyInfo patching. These features are not available in GitHub Actions and the easiest way to overcome this is to use parameters that the .NET CLI offers dotnet build -p:Version=1.2.3 and dotnet pack -p:PackageVersion=1.2.3 or dotnet pack -p:NuspecProperties="Version=1.2.3" if you use a .nuspec file.

To see the whole workflow in action, head to some of our SDK repos. You can also explore how we do releases using GitHub Actions. All code is in the workflows folder.

If you're using Kontent by Kentico as a content source for your Gatsby site, you're probably using both of these packages:

Kentico Kontent is an option: https://kontent.ai/

Let's create a content report using the Kentico Kontent headless CMS, the open source Kontent Python SDK, and Dash.

Kentico Kontent delivers all the benefits of a headless CMS while empowering your marketing team to manage the experience across your digital channels.

Provides industrial-grade security of the content data and allows expansion through its scalable optimization, making it flawless for extensive data management. Examples include Kontent that functions as a Cloud-based SaaS and offers outstanding performance.

Kontent is a headless CMS platform that allows enterprises to reach more customers, unify content across the business, and structure content for future content needs, all in one place. As a headless CMS, all content delivery is API-driven, so the same content can show up on any device or channel. 🧠

Working with a headless CMS provides a number of benefits, one of which is the freedom to choose the technology stack that suits you. You might be making a choice based on your channel or perhaps based upon your in-house team's skillset. If you're heading into a new Kentico Kontent project with a .NET team, where do you start?