Overview

Everything so far treats your docs as files in the repository, and for many teams that's the whole story. The admin panel is an opt-in layer on top: a database-backed authoring environment you use from the browser, without touching the filesystem or waiting on a deploy.

What it adds

• Browser editing with a visual editor, so people who never open the repo can write docs.

• Drafts and publishing: edits stay invisible to readers until you publish them.

• Revision history: every save snapshots a revision you can review and revert to.

• Database pages that override file pages: the store composes over the filesystem.

• Group management: set a group's label, order, and icon from the UI.

• Image uploads: drop an image into the editor and it's stored and served for you.

How it composes with files

The database store doesn't replace your files; it layers over them. A database page with the same slug as a file page wins, so you can override a single file page in the UI while every other page still comes from the repository. Remove the override and the file version is back. Your repository can stay the source of truth, with the panel used for quick fixes or for pages that non-developers own.

Opt-in

The panel is off by default and requires the database store. It adds two migrations and a gate you define. Nothing about it changes how file-based docs work; if you never enable it, Docent stays a pure file-driven site.

The panel belongs to a site. On a multi-site install, each site enables its own panel with its own gate, and each panel edits only that site's pages, groups, and uploads.

Turn it on in setup.