Scanopy gets the current map out three ways:
-- Those show the network as it is now. Auditors and authorities also ask whether it is kept current - over time, and topology snapshots are the feature for that. A snapshot is a saved, dated capture of - the network state; take one at each audit or review and you have a record of what the network looked - like on that date and what changed since. That dated record is the evidence your documentation is - maintained, not reconstructed for the assessment. -
+{#if layout === 'cards'} +Scanopy gets the current map out three ways:
++ Those show the network as it is now. Auditors and authorities also ask whether it is kept + current over time. {snapshot.title}: + {snapshot.what} + {snapshot.auditorUse} +
+ {/if} +{/if} diff --git a/src/lib/components/Footer.svelte b/src/lib/components/Footer.svelte index f5774b7..6a9ce43 100644 --- a/src/lib/components/Footer.svelte +++ b/src/lib/components/Footer.svelte @@ -172,6 +172,9 @@For a detailed comparison of these and other tools, see our full comparison of automated network diagram toolsfull network documentation tools comparison.
{/if} diff --git a/src/lib/content/contentSegments.ts b/src/lib/content/contentSegments.ts new file mode 100644 index 0000000..5b37b82 --- /dev/null +++ b/src/lib/content/contentSegments.ts @@ -0,0 +1,74 @@ +// Shared inline-component parser for markdown content routes (blog, guides, and any +// future route that renders authored markdown). Splits rendered HTML on inline markers +// so they render as Svelte components instead of raw HTML, letting a chosen vendor subset +// table, a live demo embed, a customer quote, the shared exports block, or a captioned +// topology figure appear inline in prose on WHATEVER route the content belongs on — the +// marker set is defined once here, not copied per route. +// +// Markers: +// arbitrary vendor subset table +// theme-aware live map embed +// customer quote + logo +// shared exports/embed/share block +// captioned topology screenshot + +export type ContentSegment = + | { type: 'html'; content: string } + | { type: 'vendor-inline-table'; vendorSlugs: string[]; columns: string[] } + | { type: 'scanopy-demo' } + | { type: 'customer-quote'; id: string } + | { type: 'evidence-exports' } + | { type: 'topology-figure'; view: string }; + +export const DEFAULT_INLINE_COLUMNS = ['name', 'discovery', 'pricing', 'bestFor']; + +/** + * Splits rendered markdown HTML into content segments on the inline-component markers above. + * Returns null when the content has none of the markers (caller renders the raw HTML instead). + * The second return value is the de-duplicated set of vendor slugs referenced by any + * vendor-table markers, so the caller can hydrate just the vendor data it needs. + */ +export function splitContentSegments( + html: string +): { segments: ContentSegment[]; vendorSlugs: string[] } | null { + const markerRegex = + //g; + if (!markerRegex.test(html)) return null; + + const segments: ContentSegment[] = []; + const allSlugs: string[] = []; + let lastIndex = 0; + markerRegex.lastIndex = 0; + let match: RegExpExecArray | null; + + while ((match = markerRegex.exec(html)) !== null) { + const before = html.slice(lastIndex, match.index).trim(); + if (before) { + segments.push({ type: 'html', content: before }); + } + + if (match[1]) { + const vendorSlugs = match[1].split(',').filter(Boolean); + const columns = match[2] ? match[2].split(',').filter(Boolean) : DEFAULT_INLINE_COLUMNS; + allSlugs.push(...vendorSlugs); + segments.push({ type: 'vendor-inline-table', vendorSlugs, columns }); + } else if (match[3]) { + segments.push({ type: 'customer-quote', id: match[3] }); + } else if (match[4]) { + segments.push({ type: 'topology-figure', view: match[4] }); + } else if (match[0].includes('evidence-exports')) { + segments.push({ type: 'evidence-exports' }); + } else { + segments.push({ type: 'scanopy-demo' }); + } + + lastIndex = match.index + match[0].length; + } + + const remaining = html.slice(lastIndex).trim(); + if (remaining) { + segments.push({ type: 'html', content: remaining }); + } + + return { segments, vendorSlugs: [...new Set(allSlugs)] }; +} diff --git a/src/lib/fixtures/daemon-config.json b/src/lib/fixtures/daemon-config.json index 69ccb11..c73de4b 100644 --- a/src/lib/fixtures/daemon-config.json +++ b/src/lib/fixtures/daemon-config.json @@ -138,5 +138,15 @@ "default": "30", "description": "Seconds between heartbeat updates to the server", "docsOnly": false + }, + { + "id": "config_dir", + "label": "Config Directory", + "cliFlag": "--config-dir", + "envVar": "SCANOPY_CONFIG_DIR", + "configFileKey": "config_dir", + "default": null, + "description": "Directory holding this daemon's config.json. Defaults to the per-user platform location; installing as a service sets it to a system directory.", + "docsOnly": false } ] diff --git a/src/lib/fixtures/network-diagram-vendors.ts b/src/lib/fixtures/network-diagram-vendors.ts index 481ca42..502748b 100644 --- a/src/lib/fixtures/network-diagram-vendors.ts +++ b/src/lib/fixtures/network-diagram-vendors.ts @@ -80,12 +80,12 @@ export const vendors: RecordFor all 13 tools side by side, see the full comparison of automated network diagram toolsfull network documentation tools comparison, or browse the head-to-head and alternatives comparisons.
diff --git a/src/routes/comparisons/vs/[slug]/+page.svelte b/src/routes/comparisons/vs/[slug]/+page.svelte index e6b4ef3..770f753 100644 --- a/src/routes/comparisons/vs/[slug]/+page.svelte +++ b/src/routes/comparisons/vs/[slug]/+page.svelte @@ -76,7 +76,7 @@ { '@type': 'ListItem', position: 2, - name: `Best automated network diagram tools`, + name: `Network documentation tools`, item: mainComparison }, { '@type': 'ListItem', position: 3, name: data.title, item: canonical } @@ -177,7 +177,7 @@ best {data.vendorName} alternatives.{/if} For all 13 tools side by side, see the full comparison of automated network diagram toolsfull network documentation tools comparison. diff --git a/src/routes/compliance/+page.svelte b/src/routes/compliance/+page.svelte new file mode 100644 index 0000000..240a216 --- /dev/null +++ b/src/routes/compliance/+page.svelte @@ -0,0 +1,294 @@ + + ++ NIS2, ISO 27001, and HIPAA all expect network documentation that is accurate today, not last + year. Scanopy discovers your network and keeps the map and inventory current on a schedule, + so the evidence is ready before the auditor asks. +
+ ++ Each one expects documentation that reflects the network as it is now, plus evidence that + it stayed that way over time. +
++ One scan produces four topology views, generated from the live network rather than redrawn + by hand. Each answers a question an assessor asks: what's on the network, how it's + segmented, what runs where, and how data moves between systems. +
++ Producing the evidence stops being a scramble before each assessment. The current map is + always a click from a document, a live embed, a shared link, or a dated record. +
++ Run Scanopy fully self-hosted and the network data never leaves your infrastructure. How + Scanopy handles data in each deployment model, with subprocessors and security practices, is + on the security page. +
++ Prefer to self-host? The + commercial editions + run in your own environment with support, and + pricing covers the tiers. +
+