Use of AI: AudioSilo is developed by me (a human), with assistance from AI, primarily Claude Code, to help me write, clean up, document, and review the code. That doesn't mean the app is generated on autopilot or "vibe coded". Nothing goes out until I've read it, tested it, and decided it belongs. AI is what lets one person keep up this pace, and I think it's important to disclose that.
Website · Docs · Discord · Sponsor
The documentation site for AudioSilo - the self-hosted audiobook server, player app, and desktop manager. Built with Docusaurus.
Two doc sets, one site:
- User Guide (
/users) - install the server, organize a library, invite users, listen on web/iOS/Android, use the desktop manager. No programming assumed. - Developer Docs (
/developers) - architecture, the cross-repo contract, the HTTP API reference, playback internals, contributing and releasing.
npm install
npm start # live dev server
npm run build # strict build: broken links/anchors/images failNode 24 (same as the sibling repos).
All screenshots are generated, not hand-taken: screenshots/run.sh seeds a
public-domain library, runs a local demo-mode server, and captures the real UI
with Playwright. See screenshots/README.md.
Pushes to main publish to GitHub Pages via .github/workflows/deploy.yml.
This repo is part of the AudioSilo workspace (~/dev/audiosilo) alongside
audiosilo-server, audiosilo-frontend, and audiosilo-manager. Their
Definition of Done includes updating these docs - the change→page mapping
lives in Maintaining these docs.