Umbraco Site Development: .NET 8, Headless, Multisite

A .NET team gets a task to build a corporate portal with multisite structure, role-based access, and headless API for mobile apps. The choice falls on Umbraco — an open-source CMS on ASP.NET Core. But without proper architecture and performance tuning, the project turns into a swamp with constant N+1 queries and response times over 2 seconds. We've encountered this many times and developed an approach that yields TTFB <200 ms on Umbraco 13.

For example, a company with a multisite structure (5 domains) and headless integrations for mobile apps approached us. After an audit, we found that N+1 queries on the old solution caused lag. We redesigned the architecture, implemented NuCache and the Repository pattern — TTFB dropped from 1.2 s to 180 ms, and database load decreased fourfold.

Why Umbraco for Corporate Sites?

Umbraco is a CMS on .NET 8 with an open-source MIT license. It runs on SQL Server or SQLite and supports clustering. It's well-suited for corporate sites, portals, and multisite infrastructures — especially where the client is tied to the Microsoft stack or needs a headless CMS with enterprise capabilities. Unlike WordPress, Umbraco provides strongly-typed models and a built-in headless Delivery API. License savings compared to proprietary CMS can reach 70%. For instance, Sitecore costs from $100,000 per year, while Umbraco is free (MIT license).

In tests, Umbraco with NuCache delivers TTFB <200 ms, whereas a typical WordPress installation hits 500–800 ms. This is achieved through built-in caching and model generation at compile time.

Comparison of Umbraco with Other CMS: WordPress, Sitecore, Drupal

Umbraco is 2-3 times faster than WordPress on standard hosting and requires no license fees unlike Sitecore.

Architecture and Setup

Typical solution structure:

MyProject/
├── MyProject.Web/
├── MyProject.Core/
└── MyProject.Tests/

The key configuration file is Program.cs, where all components are wired up:

// Program.cs
WebApplicationBuilder builder = WebApplication.CreateBuilder(args);
builder.CreateUmbracoBuilder()
    .AddBackOffice()
    .AddWebsite()
    .AddDeliveryApi()
    .AddComposers()
    .Build();
WebApplication app = builder.Build();
await app.BootUmbracoAsync();
app.UseUmbraco()
    .WithMiddleware(u => { ... })
    .WithEndpoints(u => { ... });
await app.RunAsync();

For adding services, we use Composers. Example service registration and handlers:

public class SiteComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder)
    {
        builder.Services.AddScoped<IArticleService, ArticleService>();
        builder.Services.AddScoped<ISitemapService, SitemapService>();
        builder.AddNotificationHandler<ContentPublishedNotification, SearchIndexHandler>();
    }
}

Strongly-typed Models and Headless API

Umbraco generates models via ModelsBuilder. Usage in a controller:

public class ArticleController : RenderController
{
    [HttpGet]
    public IActionResult Index()
    {
        if (CurrentPage is not ContentModels.Article article)
            return NotFound();
        var viewModel = new ArticleViewModel
        {
            Title = article.Title,
            Body = article.Body,
        };
        return CurrentTemplate(viewModel);
    }
}

For headless, we use the Delivery API, enabled in appsettings.json:

{
  "Umbraco": {
    "CMS": {
      "DeliveryApi": {
        "Enabled": true,
        "PublicAccess": true,
        "ApiKey": "your-api-key"
      }
    }
  }
}

API calls: GET /umbraco/delivery/api/v2/content?contentType=article.

How to Set Up Headless Delivery API? Step-by-Step

1. Enable Delivery API in appsettings.json.
2. Set an API key if authorization is required.
3. In the admin panel, mark content types available through the API.
4. Configure CORS for external clients.
5. (Optional) Enable caching at the CDN level.

Development Process for an Umbraco Site

Timelines and Scope

Cost is calculated individually based on the scope and complexity of integrations. Contact us for a consultation to get an accurate estimate.

What is Included in the Result

• Fully configured Umbraco on your hosting or in the cloud.
• Source code (Git repository) with an architecture ready for scaling.
• Documentation on content types and API.
• Editor training (up to 4 hours).
• 3-month warranty on identified bugs.
• Recommendations for caching and performance optimization.

Our experience: over 5 years of Umbraco development, 15+ projects delivered, average client rating 4.9/5. We use only licensed software and follow best practices. Contact us for a consultation — we'll help you find the optimal solution.

Official Umbraco documentation: Umbraco CMS Documentation

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.