SplatDev.Umbraco.Themes.Blog 1.0.5

UmbracoCms.Themes.Blog

Blog theme for Umbraco CMS. Provides a complete blogging experience: post listing with pagination, individual post pages with author bio, comment section, related posts, category/tag archive, and a configurable sidebar.

Requirements

• Umbraco CMS 13.x (net8.0) or 17.x (net10.0)
• UmbracoCms.Themes.Base 1.0.0
• SplatDev.Umbraco.Plugins.Yaml2Schema 1.0.35

Installation

Install via NuGet:

dotnet add package UmbracoCms.Themes.Blog

The BlogThemeComposer runs automatically on first application start. It:

1. Extracts the embedded Config/umbraco.yml to {ContentRoot}/config/themes/blog/umbraco.yml
2. Creates all required data types, document types, and templates
3. Writes a .done file so the install step is skipped on subsequent starts

Document Types

Templates

CSS

Include wwwroot/css/blog-theme.css in your layout. Custom properties are declared on :root and can be overridden to match your brand:

:root {
  --blog-color-primary: #2563eb;
  --blog-font-serif: Georgia, serif;
  --blog-content-width: 720px;
}

Content Tree Example

Blog Root (blogRoot)
└── All Posts (blogListing)
    ├── My First Post (blogPost)
    ├── Categories (blogCategory)
    │   ├── Technology
    │   └── Design
    ├── Tags (blogTag)
    │   ├── umbraco
    │   └── dotnet
    └── Authors (blogAuthor)
        └── Jane Doe

Changelog

1.0.5 — 2026-08-24

Removes a dashboard screenshot that showed an error toast. It was captured against a site where this plugin's API was unreachable, so it advertised a broken dashboard. No screenshot is better than a misleading one; a replacement will be taken against a working install.

1.0.4 — 2026-08-24

Package metadata only: the listing now carries an icon and search tags, and the project and repository links point at the organisation that actually hosts this code. No code changes.

1.0.2 — 2026-08-22

• This package's README now reaches NuGet. The publish workflow discovered packages by a list of name patterns, and this one matched none of them, so it was never built or pushed by CI — the version on NuGet was placed there by hand before the README was wired up, and no release could refresh it. Discovery is now by prefix, so the package ships whenever the repo is tagged.