Wayfinder.Rendering.GovUk
0.3.4
dotnet add package Wayfinder.Rendering.GovUk --version 0.3.4
NuGet\Install-Package Wayfinder.Rendering.GovUk -Version 0.3.4
<PackageReference Include="Wayfinder.Rendering.GovUk" Version="0.3.4" />
<PackageVersion Include="Wayfinder.Rendering.GovUk" Version="0.3.4" />
<PackageReference Include="Wayfinder.Rendering.GovUk" />
paket add Wayfinder.Rendering.GovUk --version 0.3.4
#r "nuget: Wayfinder.Rendering.GovUk, 0.3.4"
#:package Wayfinder.Rendering.GovUk@0.3.4
#addin nuget:?package=Wayfinder.Rendering.GovUk&version=0.3.4
#tool nuget:?package=Wayfinder.Rendering.GovUk&version=0.3.4
<picture> <source media="(prefers-color-scheme: dark)" srcset="assets/wordmark-dark.png"> <img src="assets/wordmark-light.png" alt="Wayfinder" height="56"> </picture>
A GDS-style service blueprint / service-design engine — domain model, calculation engine, state-machine engine, and a compiled visual editor web component. Framework-agnostic: no Umbraco, no ASP.NET Core MVC, no hosting assumptions baked in.
Wayfinder was extracted from Umbraco Prism,
which is now a consumer of these packages rather than their owner. A host application —
Umbraco-based or otherwise — layers its own tenancy, auth, and rendering opinions on top.
Wayfinder.Umbraco is the Umbraco-hosted
implementation Prism itself uses.
See it running
Wayfinder.AppHost + Wayfinder.ReferenceApp is a small, self-contained .NET Aspire host in
this repo — every package wired together, real GOV.UK Design System rendering, a demo login,
and a seeded "apply for a licence to hold a juggling event" journey. It's the fastest way to
see what a working Wayfinder host actually looks like, and exactly how little wiring a real
host (like Wayfinder.Umbraco) collapses into. Run it with
dotnet run --project Wayfinder.AppHost, or the "C#: Aspire (Full Stack)" launch config in
VS Code. See docs/guides/reference-app.md for what it
implements, how the demo blueprint is seeded from JSON and only saved in memory, and what a
real host does differently.
Packages
| Package | Purpose |
|---|---|
Wayfinder |
Core domain models (ServiceBlueprint, ServiceRequestResponseEnvelope, etc.), the declarative calculation engine, and the sanitizer interface. Zero framework dependency. |
Wayfinder.Engine |
The service blueprint state-machine engine — queue routing, gateway evaluation, request persistence. |
Wayfinder.Engine.Api |
REST toolkit (MapServiceBlueprintAuthoringApi()) exposing service blueprint authoring — list/read/validate/save/simulate — over HTTP for any ASP.NET Core host. |
Wayfinder.Engine.Mcp |
MCP-over-HTTP toolkit (MapServiceBlueprintAuthoringMcp()) — the same authoring surface as MCP tools for AI agents. |
The service blueprint model
A ServiceBlueprint describes a journey as queues (named work queues), stages (each
owning its own routes), and gateways (first-class Split/Join routing nodes — a stage's
routes must always target a gateway, never another stage directly). See
docs/guides/reference-service-blueprint-contract.md
for the full authoring schema, and
docs/guides/calculation-language.md for the
declarative expression language used in calculations and showWhen.
AI-ready authoring
Service blueprint authoring is exposed to AI agents (Claude Code or any MCP client) the
same way it's exposed to a human editor: as a toolkit a host app wires into its own
pipeline. Wayfinder.Engine.Api and Wayfinder.Engine.Mcp map the same
list/read/validate/save/simulate operations as REST and MCP-over-HTTP respectively, both
calling straight into a host's live Wayfinder.Engine in-process. See
docs/guides/ai-service-blueprint-authoring.md.
Building
dotnet build Wayfinder.slnx
dotnet pack Wayfinder.slnx
License
MIT — see LICENSE.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Wayfinder (>= 0.7.5)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on Wayfinder.Rendering.GovUk:
| Package | Downloads |
|---|---|
|
Wayfinder.Umbraco
Umbraco-hosted implementation of Wayfinder service design — a DB-backed, uSync-portable service blueprint store, a backoffice authoring API, and two Block Grid-composable building blocks (a citizen-facing stage journey and a caseworker-facing worklist) for any Umbraco v17+ site. An authoritative in-process engine, real multi-queue support, no multi-tenancy or auth opinions of its own; a host wires its own identity/tenant resolution on top. |
|
|
Wayfinder.Engine.Worklist
A default, optional caseworker worklist surface — server-rendered GOV.UK markup for the filter/sort/search/paginated list (see docs/guides/queue-worklist-filtering.md), an item review page, advance, and per-cursor pickup/putback (see docs/guides/work-allocation.md). A host wires it up with AddWorklist()/MapWorklist(prefix), supplying only tenant/actor resolution and its own page chrome — or ignores this package entirely and hand-writes the same routes itself, as Wayfinder.ReferenceApp originally did. |
|
|
Wayfinder.Engine.Journey
A default, optional single-actor journey surface — server-rendered GOV.UK markup for "get my current stage, advance it" against one blueprint (the applicant/citizen shape, as opposed to Wayfinder.Engine.Worklist's multi-item caseworker queue). A host wires it up with AddJourney()/MapJourney(prefix, blueprintKey, pageTitle) — once per blueprint it wants a self-service journey for — or ignores this package entirely and hand-writes the same routes itself. |
GitHub repositories
This package is not used by any popular GitHub repositories.