Complete workflow navigation and document page groups

README.md

@@ -17,7 +17,7 @@ docker compose up -d --build
 Open EC and create the first administrator using `EC_SETUP_TOKEN` (at least 32
 characters; generate it with `openssl rand -hex 32`). After setup, remove that
 token from the environment. Administrators can add administrators, operators and
-viewers from **Settings → Users**. See [Users and access](docs/authentication.md)
+viewers from **Administration → Users**. See [Users and access](docs/authentication.md)
 for permissions, sessions, password recovery and upgrade instructions.
 
 Operator pages and management APIs require login. Enrolled agents authenticate
@@ -32,11 +32,11 @@ including SQLite metadata and published game-file storage.
    including its DLC files. There are no library names or version labels to enter.
    Each upload becomes the latest files for that game after verification.
    Uploads work before any host is enrolled.
-2. **Hosts → Add Host**: configure a Debian 12/13 amd64 machine and run its
+2. **Fleet → Hosts → Add Host**: configure a Debian 12/13 amd64 machine and run its
    generated enrollment command. The host automatically prepares its Plutainer
    runtime and the latest T5 and T6 files, when available. The host page
    shows setup progress. Automatic agent updates are enabled by default.
-3. Add the exact Plutonium server keys in **Keys**, or supply missing keys when
+3. Add the exact Plutonium server keys in **Administration → Keys**, or supply missing keys when
    launching.
 4. Launch a server or collection. Collection previews show cached capacity
    estimates; Apply saves the queue and opens its progress page. Provisioning
@@ -61,6 +61,22 @@ continue. The host page shows update status and the last check.
 
 ## Fleet and operations
 
+The sidebar groups pages into **Fleet**, **Library**, **Operations**, **Analytics**,
+and **Administration** (administrators only). On small screens, open the navigation
+menu in the header. The account menu contains **My account**, including your
+browser's display timezone; keyboard shortcuts are available through **?**.
+
+**Operations → Overview** combines work that needs attention, running workflows,
+and recent results. Related provisioning attempts and host commands stay grouped
+under their workflow. Normal waits for empty lobbies remain under **Running**;
+successful routine checks remain in **Host operation history**. Full history is
+available on each workflow page.
+
+Server details use **Live**, **Matches**, **Configuration**, **Diagnostics**, and
+**History** sections. Hosts use **Overview**, **Servers**, **Setup**, and **Settings**.
+Contextual Back links preserve the originating filters and views, while breadcrumbs
+show each page's place in the navigation. Existing URLs and server tab links work.
+
 The fleet registry lives in SQLite, independently of host filesystems. Status
 combines agent container health, fresh game telemetry and agent-local RCON.
 Unreachable hosts report unknown instance state; they do not trigger duplicate