This documentation is also published as Markdown for efficient machine reading: the whole site is indexed at /llms.txt, and every page has a clean Markdown copy under /_llms/. These are generated from the same source and cost far fewer tokens to read than this rendered HTML.

Skip to main content Skip to navigation

BlogContentResolver Pennington.BlogSite.Services

Resolves the site's not-found body from a content-root 404.md, rendered through the markdown pipeline. Post listings, single-post rendering, browse-by-tag, and RSS are served by the shared BlogPostQuery and the registered taxonomy axis.

Constructors

BlogContentResolver

#
public BlogContentResolver(FrontMatterParser parser, IContentRenderer renderer, BlogSiteOptions options)

Creates a new resolver with the supplied front-matter parser, renderer, and options.

Parameters

parser FrontMatterParser
renderer IContentRenderer
options BlogSiteOptions

Methods

GetNotFoundContentAsync

#
public Task<RenderedNotFound> GetNotFoundContentAsync()

Resolves the site's not-found body from a content-root 404.md, rendered through the markdown pipeline. Returns null when no 404.md exists — the catch-all then tries a NotFound component, then the built-in message. The file is reserved out of discovery (ReserveNotFoundPage), so it is never a post route.

Returns

Task<RenderedNotFound>

Pennington.BlogSite.Services.BlogContentResolver

namespace Pennington.BlogSite.Services;

/// Resolves the site's not-found body from a content-root 404.md, rendered through the markdown pipeline. Post listings, single-post rendering, browse-by-tag, and RSS are served by the shared BlogPostQuery and the registered taxonomy axis.
public class BlogContentResolver
{
    /// Creates a new resolver with the supplied front-matter parser, renderer, and options.
    
public BlogContentResolver(FrontMatterParser parser, IContentRenderer renderer, BlogSiteOptions options)
; /// Resolves the site's not-found body from a content-root 404.md, rendered through the markdown pipeline. Returns null when no 404.md exists — the catch-all then tries a NotFound component, then the built-in message. The file is reserved out of discovery (ReserveNotFoundPage), so it is never a post route.
public Task<RenderedNotFound> GetNotFoundContentAsync()
; }