Skip to the content.

Admin component relationships

Packages are code boundaries, not microservices. Database selection affects blog/messages and CDN sync source directories, not the CDN bucket or DAM backend. The host reuses core/web services through #web-server and public Ui/theme components.

Legend: all drawn relationships are source-verified.

flowchart TB
  UI["Admin pages: token, blog, messages, CDN, media"]
  Session["web-layer-admin session and middleware"]
  Fetch["adminFetch"]
  Layer["Layer post and session handlers"]
  Host["Host message and CDN handlers"]
  Hook["Nitro admin-blog request hook"]
  Services["core/web post and message services"]
  Stores["Cached BlogPostStore and MessageStore per backend"]
  DB["SQLite / PostgreSQL / DynamoDB adapters"]
  Minio["MinIO helper / S3Client"]
  Media["media-client and admin media-service"]
  DAM["MediaLibrary or forwarded web media API"]
  UI -->|useAdminSession and route guard| Session
  UI -->|blog, messages, CDN requests| Fetch
  Session -->|current token and database| Fetch
  Fetch -->|Bearer plus database header| Layer
  Fetch -->|Bearer plus database header| Host
  Hook -->|attach adminBlog facade| Layer
  Hook -->|select cached blog store| Stores
  Layer -->|facade closures| Services
  Host -->|message operations| Services
  Host -->|select cached message store| Stores
  Services -->|store methods| Stores
  Stores -->|factory selection| DB
  Host -->|CDN operations| Minio
  UI -->|separate media client| Media
  Media -->|local calls or forwarding| DAM

Source evidence