Forms is used on the vast majority of CMS installations. But using Forms in a headless setup is a bit of pain since the rendering pipeline is based on ASP.NET MVC. We do have an extension to our Content Delivery API that includes the generated for...

Microsoft introduced the TagHelper back in the primordial soup of ASP.NET vNext which became .Net 5, then .NET Core then .Net 5 you know the drill… In the initial release of CMS 12 our focus was to bringing our HTML Helpers with us to make it easi...

Deploying changes to a DXP cloud service is easy [ citation needed ] you can use the deployment API or PowerShell module to push packages through your environments directly, or setup an Azure Devops pipeline or similar CI/CD tool once and for all....

With CMS 12 we introduced long awaited support for .Net 5 not just because it’s faster or adds cross platform support but because .NET Core is the future of .NET . Incidentally, a faster and cross platform CMS is also good news for folks whose...

Maybe you noticed we announced the public preview for CMS 12 a few months ago? CMS 12 natively supports .Net 5 and with it a more portable CMS which no longer requires Windows or IIS. If you like Node.js this is good news, since you can more easil...