Dignite.Site.EntityFrameworkCore 2.1.0

Dignite Site

Multi-tenant CMS on ABP — build pages and publish content by talking to your AI client via MCP, no admin backend forms.

Dignite Site is the AI-native next generation of Dignite.Cms: it keeps the same proven core (field definitions, multi-tenancy, multi-language, versioning) but replaces the content authoring interface — from a backend form to an MCP server your own AI client talks to — and adds the site-level capabilities Cms never had (SEO metadata, sitemaps, feeds, robots.txt and llms.txt, a primary domain for canonical URLs).

Core ideas

• Everything is a page, and a page is a route. The backend's page collection is the authoritative route table — sitemap, canonical URLs, and hreflang all derive from it.
• AI works through MCP, the platform doesn't ship its own assistant. You describe what you want ("create a page at /blog", "publish a news post") in your own AI client; it calls MCP tools, the platform validates against field definitions and persists it.
• Schema is the contract. Field definitions are both the validation gate for writes and the target shape handed to AI.

Documentation

Read the documentation, or go straight to a topic:

• Getting Started - install Site into an ABP application and build a first page from an AI client
• Pages and Routing, Content Types and Fields, Contents - the content model
• Razor Templates, Scriban Templates, Multilingual Sites, Localizing Template Texts - rendering a site
• Files - the file library for images and attachments
• SEO - head metadata, sitemap, feeds, robots.txt and llms.txt
• MCP Server - the tools an AI client works with, and how to connect one

The design documents for contributors are in dev-docs/; the overall design, 00-总体设计.md, is in Chinese.

Project structure

Getting started

To use Dignite Site in your own ABP application, follow Getting Started in the documentation. The rest of this section is for building this repository.

Install the .NET 10 SDK, then restore and build from the repository root:

dotnet restore Dignite.Site.slnx
dotnet build Dignite.Site.slnx --no-restore --configuration Release

The .NET dependencies from abp-modules (FlexFields, BLOB storage and the MCP server) are NuGet packages from nuget.org, pinned to 10.7.1 by DigniteAbpModulesVersion in common.props. No sibling abp-modules checkout or package registry credentials are needed. Local builds, PR CI and release builds use the same package references. See angular/README.md for the admin UI setup.

This is an ABP Framework solution. See the ABP documentation for general setup, and host/Dignite.Site.Host/migrate-database.ps1 for database migration.

Versioning

Dignite Site follows Semantic Versioning with its own numbers: unlike abp-modules, it does not track ABP's version. The NuGet packages (Dignite.Site.*) and the npm package (@dignite/ng.site) always share one version.

What counts as a major, minor or patch change is spelled out in Versioning. A patch release never carries a database migration.

Pre-releases are x.y.z-preview.N and are published to GitHub Packages only; stable versions go to nuget.org and npmjs. See CHANGELOG.md for each release.

License

MIT