[devaryakjha]

Requested by Arya · project thread

Before

The pages describe Chek server 0.3.0. They set up a server with curl only, say the app can't manage libraries, and describe the web app as a settings page.

After

The pages describe 0.5.0, where the server serves the web app at / and the admin panel at /admin.

• The quick start sets up the server in the admin panel and reads the folder in the browser and in the app.
• "Set up a new server" walks through the admin panel, and keeps the API steps in their own section at the end.
• A new page, "Read in a browser", covers the web app on the server, app.chek.page for HTTPS servers, and a source build with CHEK_WEB_DIR.
• Configuration lists CHEK_WEB_DIR. Troubleshooting covers /admin answering 404 and the "older than the admin panel" message.
• The API reference builds from openapi.yaml at 0.5.0, so it gains GET /api/v1/server, GET /api/v1/server/folders, and PATCH and DELETE /api/v1/libraries/{libraryId}.
• Example tags move from 0.3.0 to 0.5.0, and the tag table lists the minor series, such as 0.5.

How

I checked each label against readchek/app's web/src/admin and web/src/app at 685a275, the commit that the 0.5.0 image bundles. I checked each setting and endpoint against chek at the 0.5.0 tag. The pages follow the technical-writing and unslop skills.

Checks

• bun run check, bun run lint, bun run format:check and bun run build pass
• Pages describe what the linked release does, not what's planned

---

Generated by Claude Code