Hybrid Headless CMS
Frequently asked questions about Sitefinity's decoupled frontend frameworks and hybrid headless approach that combines the acclaimed ease-of-use for business users and a rich set of modern tools for developers.
Sitefinity Decoupled CMS
- Traditional, Headless or Hybrid Headless CMS. What’s the difference?
- What are the benefits of separating content management from presentation?
- Do I need Sitefinity development skills to create different client-side applications?
- What FE frameworks can Sitefinity work with?
- How does Sitefinity enable use of content across platforms and devices?
- What’s an API-first approach? API-driven content management?
- What Is Enterprise Headless CMS?
- How do we personalize decoupled experiences in Sitefinity CMS?
Sitefinity Net Core
- What are the benefits of the ASP.NET Core renderer and the decoupled Sitefinity architecture?
- What is the deployment model of the new architecture?
- Which version of ASP.NET Core is supported?
- What makes ASP.NET Core the preferred choice of the Progress Sitefinity team?
- I have a new project. Should I start implementing it with ASP.NET Core?
- Will existing MVC projects/pages continue running, for a phased transition to ASP.NET Core?
- Are the Sitefinity ASP.NET Core widgets open sourced and can I override their default behavior?
- What’s the best way to migrate to ASP.NET Core?
- Can I get training in Sitefinity and ASP.NET Core development?