Widen documentation screenshots to full column width 75% left the console UI small enough that table columns and field labels were hard to read at normal zoom. These are dense screenshots of a data grid; the detail is the point of including them.

marcpope committed Jul 26, 2026

Add screenshots to the feature documentation Twelve screenshots across ten pages, one to three per page, taken from the local Docker test stack running 0.9.6 seeded with demo data. Every image is 75% width with descriptive alt text. The demo data is entirely fictional by construction: example.com addresses, RFC 5737 documentation IP ranges (192.0.2.0/24, 198.51.100.0/24), invented hostnames and invented people. A DemoSeeder in the app repo reproduces it, so these can be retaken consistently rather than being one-off artefacts. Three passes were needed because the first screenshots leaked real data that had accumulated in the test container: - the Users screen showed the maintainer's actual personal email address on the admin account, plus a leftover local test account; - the Alarm log carried a real public IP from earlier live testing; - Settings showed a real third-party rdgen URL. All three were replaced with example/documentation values and the screens retaken. Worth remembering that a long-lived test container accumulates real data even when nothing intentionally puts it there -- screenshots need reviewing per image, not once at the start. Presence needed stabilising too: seeded devices never heartbeat, so they aged past the 60-second online window and the dashboard rendered "0 online" thirty seconds after seeding. The test container now uses a wide online window so the fleet reads as live and screenshots stay reproducible. The Add Strategy image doubles as evidence for the scroll fix in 0.9.6 -- the dialog now scrolls with its footer pinned and the Create button reachable.

marcpope committed Jul 26, 2026

Restructure the wiki: welcome, install, upgrade, features, documentation The index mixed four feature pages in with installation and called the rest "Operations". Nine of the console's features had no page at all, so anyone wanting to know what the software actually does had to read the README and guess. Home is now Welcome -> Install -> Upgrade -> Features -> Documentation, with the feature list as a table linking to a page per feature. New pages: What CortenDesk Is what it does, what it is NOT (not a RustDesk server, no patched client), and how the two paths fit together Devices and Device Groups presence, aliases, folders, pre-registration, the approval gate, recycle bin Users and Access Scoping the exact visibility rule, and that it governs the client API too, not just the console Roles and Delegated Admin the eight areas and three levels Address Books personal vs shared, share rules, tags Audit Logs the five screens, alarm types, retention Automation API tokens, envelope, endpoints, --assign Email and Invitations SMTP, invites, reset, sign-in codes Web Client what it does and why it needs HTTPS Dashboard and Active Sessions stats, and how ending a session really works Settings Reference all six tabs, every setting, real defaults Command-Line Reference every artisan command, break-glass first Importing from rustdesk-api dry-run first, and the non-bcrypt caveat Troubleshooting by symptom Every claim was checked against the source rather than the README. Four things the README got wrong or omitted, now correct in the wiki: - The online window default is 60 seconds, not 30. - API tokens live under Settings -> Security, not their own tab, and support an expiry date. - Trusted proxies already default to loopback plus all RFC1918, so the "everyone shares one IP" advice only applies to a proxy on a public address or a hand-set list. - Most important: password sign-in does NOT come back on its own when the identity provider is merely unreachable. localLoginDisabled() gates on isConfigured(), which only checks that the discovery URL, client ID and secret are non-empty -- it never touches the network. A provider that is down while still configured leaves the password form hidden. The actual break-glass is CORTENDESK_OIDC_DISABLED=true. The SSO page claimed the safer-sounding version; both it and the new Settings Reference now state the real behaviour, since getting this wrong locks someone out of their own console. Install examples bumped 0.9.0 -> 0.9.6. All 24 pages link-checked, and the forbidden-content scan is clean.

marcpope committed Jul 26, 2026