Appearance
Overall Ediky architecture
TODO: One paragraph: the whole system in plain words. What users interact with, what runs where, and how the repositories divide the work.
Existing reference
System Architecture and Ecosystem & Repositories already describe much of this. Link to them or move their content here as the page takes shape.
System overview
TODO: Replace with the real system diagram.
rendering diagram…
drag to pan · ctrl / ⌘ + scroll to zoom
Repositories and their roles
| Repository | Role in the system | Runs on | Docs |
|---|---|---|---|
| ediky-website | TODO | TODO | Overview |
| ediky-desktop | TODO | TODO | Overview |
| ediky-shared | TODO | TODO | Overview |
| ediky_tools | TODO | TODO | Overview |
| Docy | TODO | TODO | Overview |
| ci-infra | TODO | TODO | Overview |
| ediky-core | TODO | TODO | Overview |
Runtime environments
TODO: Every place code runs (browser, desktop, edge functions, workers, self-hosted services, CI) and what runs there.
| Environment | What runs there | Owned by |
|---|---|---|
| TODO | TODO | TODO |
Cross-cutting concerns
Authentication and identity
TODO
Security boundaries
TODO: Where secrets live, which surfaces are public, and where trust changes.
Observability
TODO: Logging, monitoring, alerting.
Deployment
TODO: How each repository reaches production. Link to ci-infra.
Architectural principles
TODO: The rules the system follows, and why.
Known limits and trade-offs
TODO