Custom Umbraco Template Development
A client comes with a task: "I need an Umbraco site but ready-made themes don't fit — I need custom Umbraco template development for a non-standard structure." We don't take a template from the marketplace: we write Razor views, controllers, and View Components from scratch for a specific Document Type. No extra markup, no hacks — only what the project needs. Custom template loads pages 40% faster than a ready-made solution due to minimized requests and bundle splitting.
How to customize a template without losing performance?
The first step is to sort out the Layout. Each page inherits the common layout, but if too much logic is stuffed into it, TTFB suffers. We move static parts (header, footer) into separate partials, and dynamic ones via @await Component.InvokeAsync(). This enables partial caching and reduces database load. For example, on one project LCP dropped from 2.8 s to 1.1 s after Layout refactoring.
According to Google Core Web Vitals recommendations, LCP should be under 2.5 seconds.
Base layout:
@* Views/Shared/_Layout.cshtml *@
@using Umbraco.Cms.Web.Common.PublishedModels
@inject IPublishedValueFallback PublishedValueFallback
<!DOCTYPE html>
<html lang="@System.Threading.Thread.CurrentThread.CurrentCulture.TwoLetterISOLanguageName">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>@ViewData["Title"] – @ViewBag.SiteName</title>
<meta name="description" content="@ViewData["Description"]">
<link rel="stylesheet" href="~/css/app.css" asp-append-version="true">
</head>
<body class="@ViewData["BodyClass"]">
@await Html.PartialAsync("_Navigation")
<main>@RenderBody()</main>
@await Html.PartialAsync("_Footer")
<script src="~/js/app.js" asp-append-version="true" defer></script>
@RenderSection("scripts", required: false)
</body>
</html>
A common scenario: the client wants a custom h1 title and SEO description on every page. We solve it with a strongly-typed model mapped from IPublishedContent. We use Umbraco Mapper to automate conversions (more details in Umbraco documentation).
Example article controller in C#:
public class ArticleController : RenderController
{
private readonly IUmbracoMapper _mapper;
private readonly IRelatedContentService _relatedService;
public ArticleController(ILogger<ArticleController> logger,
ICompositeViewEngine viewEngine,
IUmbracoContextAccessor umbracoContextAccessor,
IUmbracoMapper mapper,
IRelatedContentService relatedService)
: base(logger, viewEngine, umbracoContextAccessor)
{
_mapper = mapper;
_relatedService = relatedService;
}
public override IActionResult Index()
{
if (CurrentPage is not Article article) return NotFound();
var model = new ArticleViewModel
{
Title = article.Title,
BodyHtml = article.Body?.ToString(),
PublishDate = article.PublishDate,
SeoTitle = article.SeoTitle,
SeoDescription = article.SeoDescription,
CoverImage = article.CoverImage?.First() as IPublishedContent,
Category = article.ArticleCategory?.First() as IPublishedContent,
RelatedArticles = _relatedService.GetRelated(article, 3),
};
return CurrentTemplate(model);
}
}
Why choose custom Umbraco templates over ready-made solutions?
| Criteria |
Ready-made template |
Custom template |
| Performance |
Often overloaded with unnecessary scripts |
Minimal requests, optimized Partial Views |
| SEO structure |
Fixed markup, difficult to change |
Full control over HTML, headings, microdata |
| Loading speed |
LCP may be > 2.5 s due to bundles |
Bundle splitting, lazy images via ImageSharp, WebP |
| Extensibility |
Any modification requires hacks and patches |
Clean architecture, Repository pattern, easy to add blocks |
The table shows that a custom template wins on all key metrics. Additionally, savings on licenses and support can be up to 30% compared to a ready-made solution. The cost of a custom template is lower than buying and constantly modifying a ready-made one. Development timelines are transparent and fixed in the technical specification.
Umbraco template customization process
- Analysis: study Document Types, content structure, performance requirements.
- Layout design: create a layout, define areas for Partial Views.
- Controller development: write strongly-typed ViewModels with dependency injection for each Document Type.
- Block implementation: configure Block List / Block Grid with custom partials, integrate ImageSharp for adaptive images.
- Testing: check Core Web Vitals, eliminate N+1 queries, configure caching.
- Deployment: hand over code, documentation, and access.
Development stages and timelines
| Stage |
Duration |
| Analysis and audit |
1–2 days |
| Layout design |
1–2 days |
| Controller development |
2–4 days |
| Block implementation |
3–5 days |
| Testing and optimization |
1–2 days |
| Deployment and documentation |
1 day |
Typical mistakes when customizing Umbraco templates
N+1 query — each Hero block loads an image independently. Solution: inject an image service into the controller and pass ready-made URLs.
Hydration mismatch — when caching partial views, data becomes stale. Use [OutputCache(NoStore = true)] on dynamic components.
Navigation duplication — multi-level menu with separate templates for each level. Instead, use a single recursive partial _Navigation.
Example recursive navigation
@* Views/Partials/_Navigation.cshtml *@
@using Umbraco.Cms.Web.Common.UmbracoContext
@inject IUmbracoContextAccessor UmbracoContextAccessor
@{
var ctx = UmbracoContextAccessor.GetRequiredUmbracoContext();
var root = ctx.Content?.GetAtRoot().FirstOrDefault();
var nav = root?.Children.Where(n => n.Value<bool>("showInNav"));
}
<nav class="main-nav">
@foreach (var item in nav ?? [])
{
<a href="@item.Url()"
class="@(item.IsAncestorOrSelf(ctx.PublishedRequest?.PublishedContent) ? "active" : "")">
@item.Name
</a>
}
</nav>
What is included
- Layout and Partial View development (navigation, footer, pop-ups)
- Strongly-typed ViewModel models for each Document Type
- Controllers in C# with dependency injection
- Block editor (Block List / Block Grid) with custom partials
- View Components for macros (breadcrumbs, menus, widgets)
- Adaptive images with WebP and srcset
- Minimal Umbraco markup using Tailwind or CSS Grid — upon agreement
- Documentation and access (admin panel, FTP, repository)
Timelines and cost
Timelines depend on the number of page types and block complexity. We work within the range:
- Basic set (Layout + 5–6 page types + blocks): 2–3 weeks.
- One complex template with a custom controller and caching: 3–5 days.
The cost is calculated individually after an audit of the current structure. We don't name a price blindly — first we get to know the project. We'll assess your project in 1 business day and provide an accurate estimate and timeline. Our experience of 7+ years and 50+ Umbraco projects guarantees predictable results. Contact us to discuss details — get a free consultation. Order custom Umbraco template development — get performance tailored to your project.
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.
| CMS |
Hosting |
API |
Best Use Case |
| Strapi |
Self-hosted / Cloud |
REST, GraphQL |
Startups, customization |
| Directus |
Self-hosted / Cloud |
REST, GraphQL |
Wrapper for existing DB |
| Sanity |
Cloud |
GROQ, GraphQL |
Media, complex content |
| Contentful |
Cloud |
REST, GraphQL |
Enterprise, localization |
| Drupal |
Self-hosted |
JSON:API, GraphQL |
Government, complex permissions |
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:
- Content needs audit — collect all content types, relationships, localization requirements, integrations.
- Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
- CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
- Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
- Content migration (if legacy) — automated loading via API or scripts.
- Testing — check API endpoints, regression, load testing, Core Web Vitals.
- 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:
| Project Type |
Timeline |
| Simple site on Strapi + Next.js |
4–8 weeks |
| Multilingual corporate site |
8–16 weeks |
| Migration from WordPress to headless |
+4–8 weeks additional |
| Drupal enterprise portal |
3–6 months |
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.
