docs: pages for devices, clients, topology, traffic, wireless and services
An audit prompted by the new in-app docs button: 34 routes, 15 pages, and
whole navigation entries with nothing written about them at all. DNS, NTP,
WireGuard, syslog and Guest WiFi had not one mention across the entire docs
tree. Devices and Clients -- the two most-used screens -- had no page.
The coverage that did exist was weighted toward operational subsystems I
happened to write up while building them (alerting, firmware, backups,
change guard) and thin to absent on the pages people open daily. Adding a
prominent button pointing at the docs raised the cost of that gap.
Six pages, written from the actual API surface and component behaviour
rather than from memory:
devices the list, adding and adopting, every tab, the faceplate
and factory-name identification, VLAN changes and why
they are guarded, the on-device tools
clients where client data is merged from, why a client shows a
port and a radio, identification and overrides, presence
and roaming history, per-port clients
topology LLDP/CDP/MNDP precedence, MAC-before-IP matching,
spanning-tree upstream resolution, manual links, orphans
traffic the built-in collector, deduplication, NAT-tolerant
ingest, retention settings, and a troubleshooting path
wireless radios and SSIDs, RF health, the recalibrated signal
bands, rogue detection, guest portal
network-services DHCP, DNS, NTP, WireGuard, logging, NetFlow, discovery
Limitations are stated rather than omitted, because a reader hitting one
without warning trusts the rest less: the topology layout is still too wide
on flat networks (#115), unmanaged nodes cannot be placed (#147), the
connectivity funnel counts normal disassociations as failures (#156),
point-to-point radios read Poor on the client signal scale, and TX-retry
figures cannot exist on an all-RouterOS-7 fleet.
Each page also names the collector that feeds it, so the consequence of
switching one off is discoverable from the feature rather than only from the
settings screen.
mkdocs --strict clean; every relative link resolves; no page missing from
the nav.
Container image: ghcr.io/2gt-media-group-llc/mikrotik-manager:0.24.23-beta
Documentation: https://2gt-media-group-llc.github.io/mikrotik-manager/