Roadmap

Where ZajLibrary is heading. Have an idea or a gap? Use the Feedback button on any page (or the submit_feedback MCP tool) — good suggestions get promoted here during triage.

This roadmap is hand-maintained. The Changelog records what has already shipped.

Now (in progress)

The reusable-platform build — turning ZajLibrary into a fork-and-swap template (one config + database + content folder per future library).

• ✅ Folder-browse view, side-sheet preview, and Shelf ⇄ Folder toggle.
• ✅ Feedback review queue (UI + MCP channels).
• ✅ tenant.config foundation + MCP build provenance.

Next

• Private content + access control — keep public docs public, add an optional gated private shelf, with the public/private policy controlled from the admin dashboard (configurable per library, not hard-coded).
• Authenticated MCP — per-user MCP access tokens with scopes (read-public / read-private / submit-feedback), so private content never leaks to anonymous agents.
• MCP upgrade — typed tool outputs, taxonomy/changelog/roadmap exposed as MCP resources, and richer agent guidance.
• Admin dashboard — triage feedback, flip feature flags and visibility, and see which integration keys are configured (status only — never secret values).

Later / ideas

• AI chat surface improvements over the docs.
• Versioning and per-section history.
• Downloadable template kits and print/PDF export.
• Internationalisation.

Items here are intentionally loose — they become “Next” once scoped, and move to the Changelog once shipped.