Diem CMF .NET 11: Product📋

Status: Public design proposal and product vision. This series presents Diem CMF .NET’s intended architecture and capabilities. Proposed features remain subject to implementation and validation; existing components are identified separately.

This reading path starts with the people using the product. It introduces Diem's frontend, administration and Lab through a catalogue application, then explains extension distribution and the planned Diem product site.

For .NET product teams📋

Begin with Vision and Diem Heritage, then Modeling and Generating the Admin. Follow one model into an administration interface, public views and custom business actions. Continue into Module Generation and Derived Products when the same capabilities need to be reused.

For web agencies📋

Begin with Building and Editing the Front. Follow the creation of a client catalogue, review a change in a branch workspace, and package reusable components for another client. The Integrated Lab explains the addresses and development workflow behind that experience.

Chapters📋

1. Vision and Diem Heritage — the product promise and its source-backed origins.
2. Building and Editing the Front — inline composition and renderer choice.
3. Modeling and Generating the Admin — model-driven administration and customization.
4. The Integrated Lab — instances, workspaces, branches and releases.
5. Module Generation and Derived Products — reusable generation and extension packages.
6. Extensions and Marketplace — discovering, composing and activating capabilities.
7. Diem Presenting and Developing Itself — the proposed first-party instance.

The architecture path translates these experiences into responsibilities and data flow. The specification path defines how an implementation would demonstrate them.

Previous: Diem CMF .NET 11: Public Design Proposal and Product Vision · Next: Vision and Diem Heritage · Series index