Appearance
Repository dependencies
TODO: One paragraph summarizing the dependency shape of the organization. Each repository's own dependencies.md covers its details. This page is the map.
Dependency graph
TODO: Replace with the real graph. Solid arrows are build-time or code dependencies. Dashed arrows are runtime dependencies.
rendering diagram…
drag to pan · ctrl / ⌘ + scroll to zoom
Dependency matrix
Read across: the row repository depends on the column repository.
| Depends on → | website | desktop | shared | tools | Docy | ci-infra | core |
|---|---|---|---|---|---|---|---|
| ediky-website | — | TODO | TODO | TODO | TODO | TODO | TODO |
| ediky-desktop | TODO | — | TODO | TODO | TODO | TODO | TODO |
| ediky-shared | TODO | TODO | — | TODO | TODO | TODO | TODO |
| ediky_tools | TODO | TODO | TODO | — | TODO | TODO | TODO |
| Docy | TODO | TODO | TODO | TODO | — | TODO | TODO |
| ci-infra | TODO | TODO | TODO | TODO | TODO | — | TODO |
| ediky-core | TODO | TODO | TODO | TODO | TODO | TODO | — |
Dependency details
One entry per edge in the graph.
TODO: repository A → repository B
| Field | Value |
|---|---|
| Kind | TODO: package / files written into / runtime fetch / API / CI |
| Contract | TODO: what A relies on from B |
| Versioning | TODO: how changes are coordinated |
| If B changes | TODO: what breaks, and how it's caught |
Change coordination
TODO: How to make a change that touches several repositories: ordering, compatibility windows, and who to tell.