Seo content restructure#71
Merged
Merged
Conversation
Three live guides (ISO 27001, HIPAA, Podman) had no inbound internal links and were reachable only from the /guides index. Cross-link the compliance series, add a reciprocal Docker->Podman link, and route auditor-driven readers from the network-documentation-software hub to the three control guides.
Consolidate around the vocabulary that converts and stop chasing the 'network diagram tool' head term (#20 slid pos 7->18 on drawing-tool intent). - Deepen the SolarWinds NTM fixture entry (cited); singular framing on all alternatives-page intros - Strengthen the network-documentation-template blog (best non-brand asset) - Extract the shared content-segment parser; new /guides/open-source-network- documentation for the OSS/self-hosted cluster - Retarget #20 to 'network documentation tools' and merge the network- documentation-software guide into it (301, slug kept); repoint all inbound links + anchor text - New /compliance landing page (homepage/product patterns): audit-ready hero, NIS2/ISO27001/HIPAA cards, ViewSwitcher visual, EvidenceExports as cards (data-driven, shared with the guides' prose), Motala quote; outcome-led headers; compliance guides link up to it - Copy: no personification/virtue/false claims; edition framing correct (commercial = self-hosted with caps removed; Cloud = managed)
Docs were last refreshed against 2026-07-15; everything after that was undocumented, including the change to server-provisioned daemon identity. Docs still told users to create a daemon API key by hand, which now yields a daemon the server rejects as daemon_not_provisioned. - Add reference/daemon-identity: provisioning, 1:1 key binding, the 0.17.5 version floor, legacy shared-key coexistence, fixed vs editable fields. Linked from the pages that previously restated a slice of this. - managing-daemons: describe install methods instead of reproducing the commands (the server assembles them and is their source of truth); add Reconfiguring a Daemon and Binding a Key to a Legacy Daemon; rewrite Updating Daemon Properties around the management modal; note the new uninstall dispositions and log-file purge. - daemon-status: document Awaiting Connection, which every provisioned daemon passes through. Fix two stale facts while here — the priority order was listed backwards, and a healthy daemon does show a tag. - Correct the identity claims in organization, troubleshooting-setup, planning-daemon-deployment, multiple-daemons, and both self-hosted pages. - daemon-configuration: add --config-dir and the installed-service config location; drop the --concurrent-scans section (no such flag) and the v0.15 deprecation block that promised removal in v0.16. - Document Max Discovery Duration and the partial-run warning; rewrite the FD-limit guidance now that the daemon raises its own soft limit; record the SNMP probe/query timeouts and the ifTable truncation warning. - Note that the generated install command no longer carries --name, so a multi-instance host must add it or every instance overwrites the last. - Drop the Windows MSI from the docs; it isn't signed yet.
Sync docs with today's scanopy changes: - Rewrite the multiple-daemons guide around install slots (--name is gone); update managing/planning-daemon pages for the new selectors and auto-port - Add a Staleness concept page plus the per-network window setting, list badges, topology filter, and the 28-day default fact - Document container topology in L3 Logical (multi-attach, Same Container and Container Runtime overlays) and the By staleness metadata filter - Clarify host-targeted credentials assign only after a successful probe - Note CARP/VRRP floating-VIP deduplication under host matching
Root and docs now report 0 vulnerabilities; both build clean. - sharp: bump direct dep to ^0.35.3 (libvips CVEs, GHSA-f88m-g3jw-g9cj) - esbuild -> 0.28.1 (GHSA-g7r4-m6w7-qqqr): root via vite 7.3.6 which widens its range to ^0.28; docs via an override (fumadocs-mdx pins 0.27) - brace-expansion, js-yaml, dompurify, fast-uri, fast-xml-parser: patched via npm audit fix; next 16.2.9 -> 16.2.11 (multiple advisories) - docs: add esbuild/sharp overrides and raise dompurify/fast-uri/ fast-xml-parser override floors to the patched versions
Deploying scanopy-website with
|
| Latest commit: |
69a8eba
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5bd02e58.scanopy-website.pages.dev |
| Branch Preview URL: | https://seo-content-restructure.scanopy-website.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.