CMS for an ASP.NET website: compare the content workflow

Choose a CMS for an ASP.NET retail website by checking the supported runtime, editorial workflow and ownership of publication and maintenance.

Choose Umbraco as the CMS for an ASP.NET website when you want a .NET content application that also owns page rendering. Choose Contentful when the maintained website must keep its own rendering and consume content from a hosted service. Both choices depend on the application’s actual runtime and the publishing work your team will own.

Identify the application and supported runtime

Identify whether your website uses ASP.NET on .NET Framework or ASP.NET Core on modern .NET before choosing a CMS. An older ASP.NET MVC application and a current ASP.NET Core application are different integration targets, even when both use C#.

Record the application’s target framework, installed packages, hosting environment and authentication arrangement. Give that record to the developer assessing the CMS. A product described as a .NET CMS does not automatically install inside every generation of ASP.NET.

Microsoft’s lifecycle register lists .NET 10 as supported and .NET 8 and 9 as retired. ASP.NET Core follows the .NET lifecycle. Use the Microsoft support register to match the exact runtime to its support status. Older ASP.NET components follow the separate ASP.NET support policy.

A CMS purchase does not migrate an older application. Microsoft describes moving from ASP.NET Framework to ASP.NET Core as a substantial application change. If the site needs that work, give it its own scope and budget before promising an embedded CMS installation.

Compare the CMS approaches

Umbraco and Contentful fit different ownership choices. Umbraco can own the content application and its page templates. Contentful supplies content to the application you maintain. Compare the complete arrangement, including the developer work, instead of treating the two as equivalent licences.

Umbraco for a .NET content application

Umbraco fits a team that wants editors and page publishing inside a .NET CMS application. Developers maintain its content models and templates. The current installation requirements specify .NET 10 or higher, so an existing .NET Framework site needs a separate integration or migration decision.

Umbraco’s Content Delivery API also allows a separate website to retrieve content as JSON. That is an alternative architecture: Umbraco runs as its own content application, while the existing ASP.NET site consumes the responses. It does not make the CMS an embedded module inside that older site.

The Delivery API must be enabled. Its draft preview requests require the configured API credential. Your team owns the receiving site’s preview access and the handling of failed requests. Umbraco is the better fit when your developers want control of both the editorial model and the .NET content application.

Contentful for an API-delivered content service

Contentful fits an ASP.NET application that will keep its existing page rendering and retrieve editorial content from a hosted service. Its documented .NET client targets .NET Standard 2.0. Match that package requirement to the actual application before adopting the client.

An application programming interface (API) connection can also use ordinary HTTP requests. That connection separates the CMS runtime from the website runtime, but the developer must still implement authentication and response handling. The content model must map to the website’s C# types or another explicit rendering contract.

Contentful has separate delivery and preview APIs. The preview API returns unpublished content and uses a separate token. This suits a site with a protected preview route, while public requests use published content. Contentful removes the CMS-server hosting job, but your team still owns the ASP.NET integration and its cache refresh.

Compare the operating arrangements

ArrangementEditorial content lives inWebsite team maintainsPublication reaches the reader through
Umbraco owns the siteUmbraco content recordsCMS application, templates and hostingCMS rendering and the site’s cache rules
Separate Umbraco serviceUmbraco content recordsCMS hosting plus the consuming siteDelivery API and the consuming site’s refresh
Contentful serviceHosted Contentful recordsThe consuming site and content mappingPublished-content API and the site’s refresh

For a maintained ASP.NET Core site, replacing rendering with a CMS is a larger decision than adding a content feed. For an older ASP.NET MVC site, a separately hosted content service can avoid embedding a modern CMS runtime. The old website still needs its own supported hosting and maintenance plan.

Define the retail publishing workflow

Give an editor a structured product-care guide, then route its approved version through preview to public delivery. Keep product facts in the commerce system and reference them by stable product identifiers.

Consider a fictional outdoor retailer’s timber-table care guide. The editor changes the cleaning advice in the CMS. The guide references the relevant table range and a reusable warranty policy. Stock and price still come from the commerce records, and orders remain in the commerce system.

The reviewer compares the draft care advice with the approved supplier instructions. A protected preview shows the guide with the website’s actual typography and product references. A publisher then approves the content revision. Assign the reviewer and publisher permissions explicitly, even if one person holds both roles.

In an Umbraco-rendered site, the approved content must reach the public rendering and any cache in front of it. In a separately consuming ASP.NET site, publication must trigger the agreed refresh or invalidate the cached response. A successful save in the CMS does not establish that an anonymous visitor sees the new version.

Test these outcomes in a non-production environment before editors rely on the workflow:

  1. An editor can view the draft, while a signed-out visitor receives only the approved version.
  2. A user who can edit the care guide cannot approve it unless their role permits publication.
  3. After approval, a previously cached public page changes through the intended refresh path.
  4. If the content service is unavailable, the site displays the retained approved version or an explicit unavailable state.
  5. If the new guide is withdrawn, the team can restore the previous approved revision and refresh the public page.

Protect draft credentials in the application’s server configuration. Keep preview responses outside shared public caches. When restoring content, verify the guide and its referenced policy together, since an older guide can still point to a newer policy.

Customer-facing answers that reuse the care guide also need the approved version. Record which content revision each destination receives and what triggers its update. This prevents the website and another customer channel from giving different care instructions after publication.

Plan maintenance and ownership

Name a developer owner for runtime support and an editorial owner for the content model. Each connection needs a maintainer who can recover after a failed delivery or a schema change.

For Umbraco, budget for the CMS runtime and packages, hosting, database backups and application upgrades. Managed hosting changes who performs infrastructure work. It does not remove responsibility for your templates or custom integration. Keep a supported runtime and the CMS release’s requirements together in the maintenance record.

For Contentful, budget for editor access and the service allowances your publishing volume needs. Your team maintains the .NET client or HTTP connection, content mapping and cache behaviour. Include preview access in that work, since a working public feed does not prove the draft path works.

Require a content export with assets and stable reference identifiers. Keep the schema and the website’s rendering code separately so another developer can reconstruct the published guide. Exercise recovery in an isolated environment before relying on an export as a backup plan.

The Umbraco CMS guide examines that option in more detail. Choose the embedded approach when your team wants to maintain the content application and website together. Choose API delivery when retaining the website’s rendering is the priority, with one named owner for the connection and its public refresh.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup