orchestrated-discussions/diagrams/general-discussion_4.puml

97 lines
1.7 KiB
Plaintext

@startuml
!define RECTANGLE class
title Existing Tool Landscape Architecture
package "Editor-Based Solutions" {
[VS Code + Extensions] as VSCode
[IntelliJ IDEA] as IntelliJ
[Markdown Monster] as MarkdownMonster
}
package "Diagram-as-Code" {
[Mermaid] as Mermaid
[PlantUML] as PlantUML
}
package "Documentation Platforms" {
[Docusaurus] as Docusaurus
[GitBook] as GitBook
[Read the Docs] as RTD
}
package "Knowledge Bases" {
[Obsidian] as Obsidian
[Notion] as Notion
[Confluence] as Confluence
}
actor Developer
actor Team
Developer --> VSCode : "Best for\nIDE-centric\nworkflow"
Developer --> Mermaid : "Inline diagrams\nin markdown"
Developer --> Docusaurus : "Public docs\nsite"
Team --> Notion : "Small team\nflexibility"
Team --> Confluence : "Enterprise\ncollaboration"
note right of VSCode
Pros:
+ Unified editing
+ PlantUML + Markdown
Cons:
- Still need external
SVG editor
- No audience
segmentation
end note
note right of Mermaid
Pros:
+ GitHub native
+ Live preview
+ Multiple types
Cons:
- Different syntax
than PlantUML
- Limited UML support
end note
note right of Confluence
Pros:
+ Best collaboration
+ Enterprise features
+ Rich integrations
Cons:
- Expensive
- Heavy/complex
- Vendor lock-in
end note
note bottom of Obsidian
Pros:
+ Local files
+ Fast
+ Graph view
Cons:
- Weak collaboration
- No unified artifact
management
end note
note as GapAnalysis
**None solve all requirements:**
✗ Unified markdown + PlantUML
+ SVG + images
✗ Audience-based rendering
✗ Scale without fragmentation
✗ Zero context switching
end note
@enduml