complete codex docs
This commit is contained in:
parent
b5dcf01a8c
commit
3cefad183d
62 changed files with 2730 additions and 50 deletions
26
docs/decisions/0004-workshop-system.md
Normal file
26
docs/decisions/0004-workshop-system.md
Normal file
|
|
@ -0,0 +1,26 @@
|
|||
# Decision 0004: Server Content Manager Is The Workshop Layer
|
||||
|
||||
## Status
|
||||
|
||||
Accepted
|
||||
|
||||
## Decision
|
||||
|
||||
`Panel/modules/addonsmanager` should remain the primary future home for Workshop items, mods, add-ons, and server content. `steam_workshop` should remain a deprecated compatibility layer only.
|
||||
|
||||
## Reasoning
|
||||
|
||||
- `addonsmanager` already has the richer schema and more complete product direction.
|
||||
- It supports content types beyond Steam Workshop.
|
||||
- It is a better fit for load order, enable/disable, install history, and metadata.
|
||||
|
||||
## Alternatives Considered
|
||||
|
||||
- keep `steam_workshop` as the main module
|
||||
- split mods, add-ons, and Workshop into separate modules
|
||||
|
||||
## Why Those Were Not Chosen
|
||||
|
||||
- `steam_workshop` is explicitly deprecated in the codebase.
|
||||
- Separate modules would fragment user workflows and duplicate install logic.
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue