An ASP.NET CMS was a requirement in order to work with the .NET API and commerce system, and it had to be usable by non-technical
content editors.
I defined and developed the infrastructure for managing content within Umbraco, with the flexibility to use re-usable components: a document/template/page structure covering four layers of page hierarchy while supporting the course catalog through API-driven pages.
Umbraco proved an excellent choice, allowing development to center on API services consumed by both JavaScript and Razor views. CMS content was woven into the API-managed content to provide editorial customization on top of the data-specific API content.
I defined and developed the infrastructure for managing content within Umbraco, with the flexibility to use re-usable components: a document/template/page structure covering four layers of page hierarchy while supporting the course catalog through API-driven pages.
Umbraco proved an excellent choice, allowing development to center on API services consumed by both JavaScript and Razor views. CMS content was woven into the API-managed content to provide editorial customization on top of the data-specific API content.