-Sanatana.Contents library provides content, attached images, comments and categories management;
-Create, Update, Delete operations based on Sanatana.Patterns.Pipelines library allow reusing and altering predefined sequences of actions. Validation, html sanitizing, permission checks, database access and other steps can be removed or replaced with domain specific;
-Basic role permission system lets control access of users to different content types. Custom roles, permissions and content statuses are supported. Define them as domain specific enums and supply as integers to Sanatana.Contents;
-LINQ to ElasticSearch support for global search queries with easy filtering settings.

-It is a backend set of libraries with no built in UI. It can be wired to existing solution requiring content management;
-NET standard 2.0 version, so it can be used in both .NET frameworks: Full, Core;
-Async await used through all layers.

-Supporting libraries to choose from allow serving content in high volume distributed applications:
EntityFrameworkCore or MongoDb as data access layers;
ElasticSearch as search engine;
Amazon S3 or OS file system as files storage;
Configurable caching layer decorating database queries.

-Everything is extendable and replaceable through dependency injection. Autofac modules are provided out of the box, although not restricted to using them. Any other DI container can be used;
-Possible to have multiple content types in single application. Like posts, support tickets, shop items or something else. Each saved in separate database table. Entities that have free input text as some of their properties are likely candidates;
-Simple way of adding custom content types, not much different from applications from scratch. While still reusing all existing business logic with help of generics.

Wiki pages describing:
-Configuration
-Usage
-Extensibility