Umbraco CMS customization

What this bullet means

The employer is looking for CMS experience, especially the ability to adapt content management features to real customer needs.

Sample app idea

Umbraco Content Workflow Mockup with document types, content request records, preview status, publishing notes, and reusable content blocks.

Main build outline

1. Model CMS document types for landing pages, support articles, alerts, reusable blocks, and navigation links.
2. Create a content workflow with draft, needs review, approved, published, and rollback states.
3. Add fields for customer request, implementation note, affected page, and publishing instructions.
4. Document how the mockup maps to Umbraco concepts without requiring a live production CMS.
5. Include screenshots of content editing, workflow status, and page preview behavior.

Portfolio proof

• Screenshot of CMS-style document types and content workflow states.
• README mapping content types, reusable blocks, preview, and publishing notes to Umbraco concepts.
• Sample content records that use fictional data only.

Minimal documentation

• README with the business problem, screenshots, setup notes, and technology stack.
• One requirements note that maps the job bullet to the sample feature.
• One test plan note with happy path, validation, and edge case checks.
• One honest portfolio note that says this is self-directed practice, not employer work.

Modern .NET stack

• Blazor Server or ASP.NET Core Razor Pages.
• C# services with validation and dependency injection.
• SQL Server locally, then SmarterASP SQL Server or Azure SQL.
• Optional Azure App Service, GitHub Actions, Docker, and AI helper feature.