Osirion.Blazor.Cms.Domain 2.1.3

Osirion.Blazor.Cms.Domain

Domain layer for the Osirion.Blazor CMS ecosystem, containing core entity definitions, value objects, enums, and domain services.

Overview

The Domain project implements the Domain layer in the Clean Architecture pattern, providing the core business entities and logic for the CMS system. This project has minimal dependencies and serves as the foundation for the entire CMS ecosystem.

Key Components

Entities

Core business objects defined by their identity:

public class ContentItem : Entity<Guid>
{
    public string Path { get; set; } = string.Empty;
    public string Title { get; set; } = string.Empty;
    public string Content { get; set; } = string.Empty;
    public IReadOnlyDictionary<string, object> Metadata { get; set; } 
        = new Dictionary<string, object>();
    // Additional properties
}

Value Objects

Immutable objects defined by their properties:

public class ContentMetadata : ValueObject
{
    public string? Title { get; }
    public string? Description { get; }
    public DateTime? PublishedDate { get; }
    public string? Author { get; }
    public IReadOnlyList<string> Tags { get; } 
    public IReadOnlyList<string> Categories { get; }
    public bool IsFeatured { get; }
    
    // Constructor, Equals, GetHashCode implementations
}

Enumerations

Strong typing for domain concepts:

public enum ContentStatus
{
    Draft,
    Published,
    Archived
}

public enum SortField
{
    Title,
    Date,
    Author,
    Path
}

public enum SortDirection
{
    Ascending,
    Descending
}

Domain Services

Core business logic not naturally fitting into entities:

public interface IContentService
{
    Task<IReadOnlyList<ContentItem>> GetContentItemsAsync(ContentQuery query);
    Task<ContentItem?> GetContentItemByPathAsync(string path);
    Task<IReadOnlyList<string>> GetAvailableTagsAsync();
    Task<IReadOnlyList<string>> GetAvailableCategoriesAsync();
}

Design Principles

This project follows these design principles:

1. Persistence Ignorance: Domain entities know nothing about how they are stored
2. Rich Domain Model: Domain entities contain both data and behavior
3. Immutability: Value objects are immutable
4. Encapsulation: Internal state is protected
5. Domain-Driven Design: Modeling based on the ubiquitous language of the domain

Dependencies

The domain layer has minimal dependencies:

• .NET 8.0/.NET 9.0: Target frameworks
• Microsoft.Extensions.DependencyInjection: For dependency injection
• Microsoft.Extensions.Logging.Abstractions: For logging abstractions

License

This project is licensed under the MIT License - see the LICENSE file for details.