docs(readme): point at the wiki, and say which audience it is for
The wiki is now the user-facing set — Getting Started, Troubleshooting, FAQ, AI Disclosure — and docs/ is for people reading the code. Saying which is which up front saves a reader opening ARCHITECTURE.md to find out how to install the thing. The CLI guide deliberately stays in docs/ and is linked from the wiki rather than copied into it: it describes the behaviour of a specific version, goes through branch protection like the code, and a wiki page does neither. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
ba6f19722e
commit
0a31700f7f
1 file changed
+6
@@ -100,6 +100,12 @@ pipdock snapshot rollback latest
|
||||
|
||||
## Documentation
|
||||
|
||||
**Using PipDock?** The [wiki](https://github.com/poli0981/pipdock/wiki) is the user-facing set —
|
||||
[Getting Started](https://github.com/poli0981/pipdock/wiki/Getting-Started),
|
||||
[Troubleshooting](https://github.com/poli0981/pipdock/wiki/Troubleshooting) and an
|
||||
[FAQ](https://github.com/poli0981/pipdock/wiki/FAQ) that explains the design decisions rather than
|
||||
just stating them. Everything below is for reading the code.
|
||||
|
||||
| Doc | Purpose |
|
||||
|---|---|
|
||||
| [docs/PRD.md](docs/PRD.md) | Product goals, personas, feature matrix P0–P2, non-goals |
|
||||
|
||||
Reference in new issue
Block a user