Skip to content

Content management and publishing

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Vertical Content
Prototype reference Content prototype (ConnectSoft.DesignPrototypes)
Managed edition SelfOperated (D33, D34)
Data residency tenant-region (D31)
Catalog Examples catalog · Vision-to-Production path for this vertical

Business problem

Marketing content lives in a legacy CMS that cannot serve multiple brands or localize at scale.

Product intent

A headless content platform with authoring, review and publishing workflows, localization and delivery APIs.

What the Factory makes different here: review and publishing as approval-bound commands; localization from the Localization Blueprint.

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Product Manager Agent, Frontend Developer Agent vision
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent frontend, localization
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Product Manager Agent, Frontend Developer Agent, Backend Developer Agent, Documentation Writer Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent documentation, test
Delivery and provisioning DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) DevOps Agent, Infrastructure Architect Agent —
Operations Product Fleet Operations (BC-35..37) — handover, objectives, rollouts, incidents, off-boarding

Delivery workflows exercised: growth-and-marketing-workflows, documentation-and-knowledge-management-workflows.

Generated product shape

C4Context
    title Content management and publishing system context
    Person(user, "Users", "Content users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Content management and publishing") {
        System(ctx_Authoring, "Authoring", "documents, versions, assets")
        System(ctx_Review, "Review", "review assignments, decisions")
        System(ctx_Publishing, "Publishing", "channels, schedules, delivery")
    }
    Rel(user, ctx_Authoring, "uses through the product gateway GW-07")
    Rel(factory, ctx_Authoring, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Authoring documents, versions, assets DraftSaved
Review review assignments, decisions ContentApproved
Publishing channels, schedules, delivery ContentPublished

Modules and templates

Module Template Notes
Microservice ×3 connectsoft-microservice
Authoring shell connectsoft-blazor-shell
Marketing site connectsoft-marketing-site
Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product.

Prototype reference

Content prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.

Operations as a managed product

Self-operated by the customer's team; inventoried for upgrade offers.