Hood.Admin 7.0.0

Hood CMS

👁 GitHub release (latest by date incl. pre-releases)
👁 CI

A fully customisable content management system for ASP.NET Core, built on .NET 10 and EF Core 10.

Clone the demo project

Clone the demo Hood web project from Hood.Demo. Or enter the following command in Git Bash or your command prompt.

$ git clone https://github.com/HoodDigital/Hood.Demo

Create a new project via the dotnet CLI

Coming soon.

NuGet installation

👁 NuGet stable
👁 NuGet prerelease

Install Hood CMS via Package Manager.

> Install-Package Hood

or via .NET CLI

> dotnet add package Hood

Client Side Code

👁 npm stable
👁 npm prerelease

The client side code is not required to run Hood CMS as all required JS/CSS are served via jsdelivr. However, if you want to extend or modify the client side code, you can download this npm package, which contains the required distribution CSS and JavaScript, as well as source SCSS and TypeScript files.

https://www.npmjs.com/package/hoodcms

To install Hood CMS client side code via NPM.

> npm install hoodcms

or

> yarn add hoodcms

To use your own client side code, you will also need to update script/link references in your theme's HTML or Razor C# files to use your own version of the code, rather than the CDN.

Build preset

Building your own frontend on Hood's toolchain? Don't clone the configs — extend them. The hoodcms package exports Hood's audited build process:

// rollup.config.mjs
import { hoodRollup } from 'hoodcms/build';
export default hoodRollup({ entries: { site: 'src/ts/site.ts' }, externals: ['owl.carousel'] });

// gulpfile.js
const { registerHoodTasks } = require('hoodcms/build/gulp');
registerHoodTasks(require('gulp'), { less: true });

Your tsconfigs "extends": "hoodcms/tsconfig.base.json" (declare your own rootDir/outDir — path options don't inherit across packages). The toolchain versions are published as optional peer dependencies — install the ones you use at Hood's audited versions.

Database Installation/Update

Hood's schema ships as plain, idempotent, forward-only SQL scripts. EF Core migrations are only an authoring tool; nothing applies them at runtime. Full detail and the regeneration workflow are in .

hood-schema runner (recommended)

hood-schema is a .NET CLI tool that applies the schema with one command — fresh installs and v6→v7 upgrades alike. It journals applied scripts in its own dbo.SchemaVersions table, so it's idempotent and figures out what's needed for you (no per-version chain to run by hand).

dotnet tool install --global Hood.SchemaTool
hood-schema upgrade --connection "Server=…;Database=…;User Id=…;Password=…;TrustServerCertificate=True"

Your own project SQL rides the same path via --scripts <folder> (applied after Hood's core). See for the full runner reference.

By hand (alternative)

Fresh install — create the database, then execute /sql/latest.sql (standard ASP.NET Identity backend).

Upgrade — run the upgrade-delta scripts for each tier above your current version, in folder-then-filename order (the MM.mm.pp/SS key is the apply order):

The deltas are small and drop no data-bearing columns — see for exactly what each tier changes.

Full documentation

Documentation is a work in progress. The most useful references today:

• — database schema, the hood-schema runner, upgrade tiers, and how to regenerate the SQL.
• — the containerised local dev rig (docker compose up).

Also, feel free to add your issues or pull requests to our GitHub — we always welcome contributions!