The README drifted back toward dev-doc density. Rework:
TONE/LENGTH: brief and barely technical. Cut sections like the Admin walkthrough (sessionStorage details, X-Admin-Key header mechanics, --reset-admin-key command) and the full API curl example block down to one-liners. The admin section should just say: an /admin page exists for runtime settings, protected by a key set at install (PALETTE_ADMIN_KEY env var), resettable locally. The API section should just say: full REST API documented in docs/API.md, with ONE minimal example or none. Details belong in docs/API.md and docs/design/, not the front page.
KEEP: the Configuration table (env vars, flags), features list, Get Started, links to docs.
SCREENSHOTS: retake all screenshots against the CURRENT UI (they are stale after the many changes) and use DIFFERENT themes per screenshot to show off the palette system: e.g. editor in midnight, history in pastel-lavender, paste view in pastel-peach, saved in pastel-cloud. Use the ?theme= query param or the settings switcher when capturing. Update docs/palette-previews/ and the README image links.
The README drifted back toward dev-doc density. Rework:
1. TONE/LENGTH: brief and barely technical. Cut sections like the Admin walkthrough (sessionStorage details, X-Admin-Key header mechanics, --reset-admin-key command) and the full API curl example block down to one-liners. The admin section should just say: an /admin page exists for runtime settings, protected by a key set at install (PALETTE_ADMIN_KEY env var), resettable locally. The API section should just say: full REST API documented in docs/API.md, with ONE minimal example or none. Details belong in docs/API.md and docs/design/, not the front page.
2. KEEP: the Configuration table (env vars, flags), features list, Get Started, links to docs.
3. SCREENSHOTS: retake all screenshots against the CURRENT UI (they are stale after the many changes) and use DIFFERENT themes per screenshot to show off the palette system: e.g. editor in midnight, history in pastel-lavender, paste view in pastel-peach, saved in pastel-cloud. Use the ?theme= query param or the settings switcher when capturing. Update docs/palette-previews/ and the README image links.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The README drifted back toward dev-doc density. Rework:
TONE/LENGTH: brief and barely technical. Cut sections like the Admin walkthrough (sessionStorage details, X-Admin-Key header mechanics, --reset-admin-key command) and the full API curl example block down to one-liners. The admin section should just say: an /admin page exists for runtime settings, protected by a key set at install (PALETTE_ADMIN_KEY env var), resettable locally. The API section should just say: full REST API documented in docs/API.md, with ONE minimal example or none. Details belong in docs/API.md and docs/design/, not the front page.
KEEP: the Configuration table (env vars, flags), features list, Get Started, links to docs.
SCREENSHOTS: retake all screenshots against the CURRENT UI (they are stale after the many changes) and use DIFFERENT themes per screenshot to show off the palette system: e.g. editor in midnight, history in pastel-lavender, paste view in pastel-peach, saved in pastel-cloud. Use the ?theme= query param or the settings switcher when capturing. Update docs/palette-previews/ and the README image links.