Headless CMS and Decoupled CMS in .NET Core
summary
Claims that headless .NET Core CMSs split front end from back end and serve structured content over APIs, enabling multi‑channel delivery and reuse; cites a projection of 40 million IoT devices by 2022. Lists concrete .NET Core options and features: Orchard Core (GraphQL/REST, multi‑tenant, Docker), Go Foundry (code‑first, dotnet new, Azure plugin), Piranha Core (NuGet template), Squids (OData/Swagger, Docker) and Braco/Umbraco Heartcore (REST, webhooks, GraphQL, Cloudflare delivery).
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:32Who am I
- 0:47Whats new
- 1:45Headless vs Traditional CMS
- 2:15Headless CMS Architecture
- 3:00Headless CMS Overview
- 4:01API Definition
- 4:34Why go headless
- 5:07Use cases
- 5:21Overview
- 5:44Orchard Core
- 6:10CloudFoundry
- 6:34Piranha
- 6:54Squids
- 7:16Umbraco
- 8:07Million Dollar Question
