How 8t4/c4sharp works
Project type and purpose
• It provides:
• A command-line tool (src/C4Sharp.Tools) exposing build and export commands.
File structure
• Top-level folders:
• .github / CI workflows & funding
• docs / C4 definitions, images, UML templates
• src / two modules:
– C4Sharp (core library)
– C4Sharp.Tools (CLI entrypoint)
• Within C4Sharp:
• Commons / extensions & file-system helpers
• Elements / domain abstractions (Person, Container, SoftwareSystem, Relationship)
• Plantuml / PlantUML DSL generation, resources, exceptions
• Themes / default and customizable styling
• There is a .sln, NuGet package references, Java requirement (PlantUML JAR), and build scripts in GitHub Actions.
README for additional insights
• Confirms .NET 5+ and Java prerequisites.
• Describes two build approaches: self-compile via code or using the c4scli tool (ideal for CI).
Elements
• Clear labels: e.g., “C4Sharp.Core”, “C4SCLI”, “ModelDiagrams Sample”, “PlantUML (Java)”.
• Developer → (consumes) → NuGet packages
• CLI → (calls) → Core Library API
• Core Library → (executes) → PlantUML JAR
• Core Library → (reads/writes) → Resource files & output folder
Detailed capture of essential architectural elements
• Don’t omit the Java/PlantUML dependency—they are critical for output.
• How theming ties into the builder before export.
• Configuration sources: sample code overrides default styles.