diff --git a/site/astro.config.mjs b/site/astro.config.mjs index 336d7934..be12b238 100644 --- a/site/astro.config.mjs +++ b/site/astro.config.mjs @@ -82,6 +82,7 @@ export default defineConfig({ // scripts/css-regions.mjs and css-shadowing.mjs hold this shape. customCss: [ './src/styles/tokens.css', + './src/styles/nav-spacing.css', './src/styles/docs/theme.css', './src/styles/docs/base.css', './src/styles/docs/shell.css', diff --git a/site/src/components/Compare.astro b/site/src/components/Compare.astro new file mode 100644 index 00000000..d20b30b9 --- /dev/null +++ b/site/src/components/Compare.astro @@ -0,0 +1,155 @@ +--- +import { + compareColumns, + compareCopy, + compareNoteHtml, + compareRows, +} from '../data/site-content/compare'; + +const highlightIndex = compareColumns.findIndex((c) => c.highlight); +--- + +
+
+

{compareCopy.heading}

+ {/* Optional: netscli's table stands on its heading, and a lead that only + listed what was compared and which versions was filler. */} + {compareCopy.leadHtml &&

} + + +

+ + + + + {compareColumns.map((c, i) => ( + + ))} + + + + {compareRows.map((row) => ( + + + {row.cells.map((cell, i) => ( + + ))} + + ))} + +
Feature{c.name}
{row.feature} + {cell === '—' ? ( + <> + + Not offered + + ) : ( + cell + )} +
+
+ + {compareNoteHtml &&

} +

+
+ + diff --git a/site/src/components/Install.astro b/site/src/components/Install.astro index ada24c19..a22aa88b 100644 --- a/site/src/components/Install.astro +++ b/site/src/components/Install.astro @@ -48,13 +48,21 @@ const groups = [ return (

{title}

-
+
{recommended.label}
{recommended.command ? (
{recommended.command}
) : ( - - Download {recommended.label} + /* A button, not a command chip. It was drawn in the + `.cmd big` box the other tabs use for their + recommended command, so it read as a command that + said "Download Debian / Ubuntu" -- the label above + it, repeated, in a box made for copying. The label + names the package type; the button just says + Download, like the AppImage row's, and is styled like + it (not green: see `a.install-download` below). */ + + Download → )} {recommended.hint &&

{recommended.hint}

} @@ -217,6 +225,16 @@ html[data-theme='light'] #install .reco{ box-shadow:var(--ui-lift-sm); } .reco-meta{font-size:.85rem;font-weight:500;color:var(--ui-text);margin-bottom:8px} +/* A recommended download (Linux's .deb) lays out like the download rows + under it: label left, button on the right edge. Stacked, the button sat + under the label on the left while the AppImage button below it sat on the + right, so the two buttons in one group pointed in different directions. + 16px sides match `.alt`, so labels and buttons line up down the group. */ +.reco-download{ + display:flex;flex-wrap:wrap;align-items:center;justify-content:space-between; + gap:8px 16px;padding-inline:16px; +} +.reco-download .reco-meta{margin-bottom:0} .cmd.big{font-size:1.05rem;padding-right:74px} /* The container is the divider: the rows sit on it with a 1px gap, so its background shows through as the hairline between them. Chip tokens, so the @@ -267,8 +285,8 @@ html[data-theme='light'] #install .reco{ * * This was accent text on an accent tint inside an accent border -- the * loudest thing in the section, on the row that is the *least* recommended - * route: a direct download is unsigned, unverified and unmanaged, while the - * package-manager rows above it check a hash. The green was pointing at the + * route: a direct download is unmanaged and nothing checks it on the way + * in, while the package-manager rows above it check a hash. The green was pointing at the * wrong option. It reads as one route among several now, and keeps the * accent for hover and focus so it is still obviously a control. */ a.install-download{ diff --git a/site/src/components/Nav.astro b/site/src/components/Nav.astro index 3d5ec590..b071876d 100644 --- a/site/src/components/Nav.astro +++ b/site/src/components/Nav.astro @@ -206,7 +206,7 @@ html[data-theme='light'] nav[data-site-nav]::after{ border-color:rgba(var(--ui-accent-rgb),.35); outline:none; } -.nlinks{display:flex;gap:20px;font-size:.8125rem;flex-wrap:wrap;justify-content:flex-end} +.nlinks{display:flex;gap:var(--ui-nav-link-gap);font-size:var(--ui-nav-font-size);flex-wrap:wrap;justify-content:flex-end} .nlinks a{ color:var(--ui-text-muted);text-decoration:none; display:inline-flex;align-items:center; @@ -235,12 +235,12 @@ html[data-theme='light'] nav[data-site-nav]::after{ starlight/Header.astro, where the docs page shows it. */ .nlinks a.nav-group-start{ position:relative; - margin-inline-start:32px; + margin-inline-start:var(--ui-nav-group-gap); } .nlinks a.nav-group-start::before{ content:""; position:absolute; - inset-inline-start:-16px; + inset-inline-start:calc((var(--ui-nav-group-gap) + var(--ui-nav-link-gap) + 1px) / -2); top:50%; width:1px; height:18px; diff --git a/site/src/components/starlight/CopyPage.astro b/site/src/components/starlight/CopyPage.astro new file mode 100644 index 00000000..1c3dc64b --- /dev/null +++ b/site/src/components/starlight/CopyPage.astro @@ -0,0 +1,120 @@ +--- +/** + * The "Copy page" button: copies this page's markdown source to the + * clipboard. Rendered twice on a docs page -- above the content on wide + * screens (MarkdownContent.astro), and at the end of the collapsed "On this + * page" bar on narrow ones (PageSidebar.astro), where it stays in reach as the + * page scrolls. CSS shows one or the other; the script wires every copy. + */ +const { entry } = Astro.locals.starlightRoute; +// 'docs/cli' -> 'cli'. The section index arrives as the bare id 'docs', +// which the strip does not match -- see the same mapping in +// src/pages/docs/[...slug].md.ts, which serves these files. +const slug = entry.id === 'docs' ? 'index' : entry.id.replace(/^docs\//, ''); +const markdownHref = `/docs/${slug}.md`; +--- + + + + + + diff --git a/site/src/components/starlight/Footer.astro b/site/src/components/starlight/Footer.astro index 98b2a4dd..662a8350 100644 --- a/site/src/components/starlight/Footer.astro +++ b/site/src/components/starlight/Footer.astro @@ -4,7 +4,7 @@ import LastUpdated from 'virtual:starlight/components/LastUpdated'; import Pagination from 'virtual:starlight/components/Pagination'; import { site } from '../../data/site'; -const { meta, hero, builtWith } = site; +const { meta } = site; const year = new Date().getFullYear(); --- @@ -19,35 +19,19 @@ const year = new Date().getFullYear(); */} - {/* Below the Previous/Next cards, not above them. These are a footnote - about the page you just read; the pagination is where you go next, and - it should not be pushed down the screen by metadata. */} -
- - -
- -
-
© {year} {meta.author.name} · MIT
-
- GitHub - Releases - Docs - Changelog + {/* One row under the Previous/Next cards: this page's metadata on the + left, the copyright on the right. It used to be three blocks -- the + metadata, then the landing footer's copyright, links and built-with + line -- and in the docs' content column, far narrower than the landing + page, that wrapped into four lines of small grey text. The links are + all in the header on every docs page, so the footer dropped them and + the built-with line; the landing footer keeps both. */} +
+
+ +
- {builtWith.length > 0 && ( -
- Built with{' '} - - {builtWith.map((b, i) => ( - <> - {i > 0 && {i === builtWith.length - 1 ? ', and ' : ', '}} - {b.name} - - ))} - . -
- )} +
© {year} {meta.author.name} · MIT
@@ -62,12 +46,12 @@ const year = new Date().getFullYear(); border-top: 1px solid var(--sl-color-hairline); } - .docs-footer-inner { + .docs-footer-row { display: flex; align-items: center; justify-content: space-between; flex-wrap: wrap; - gap: 0.9rem 1.25rem; + gap: 0.5rem 1.25rem; width: 100%; max-width: 1060px; margin-inline: auto; @@ -76,23 +60,11 @@ const year = new Date().getFullYear(); font-size: 0.75rem; } - /* Sits above the pagination, on the same measure as the rest of the - footer. Row rather than column so the date and the edit link read as - one line of page metadata; it wraps on narrow screens instead of - squashing. Empty on a page where neither renders, and `:empty` keeps - it from adding a gap in that case. */ .docs-page-meta { display: flex; align-items: center; - justify-content: space-between; flex-wrap: wrap; gap: 0.5rem 1.25rem; - width: 100%; - max-width: 1060px; - margin-inline: auto; - padding-inline: 1.5rem; - color: var(--sl-color-gray-3); - font-size: 0.75rem; } .docs-page-meta:empty { @@ -106,12 +78,6 @@ const year = new Date().getFullYear(); padding-inline: 1.5rem; } - .docs-footer-links { - display: flex; - gap: 1rem; - flex-wrap: wrap; - } - .docs-footer a { color: var(--sl-color-gray-3); text-decoration: none; @@ -121,13 +87,5 @@ const year = new Date().getFullYear(); color: var(--sl-color-gray-1); } - /* Matches the landing page's footer: a third item in the same row rather - than a centred band of its own behind another rule. components/Footer - .astro is the reference -- the two footers carry the same links and the - same built-with line, and reading as two different components on two - pages of one site was the whole complaint. */ - .docs-built-with { - color: var(--sl-color-gray-3); - } } diff --git a/site/src/components/starlight/Header.astro b/site/src/components/starlight/Header.astro index b7ce1434..967cd810 100644 --- a/site/src/components/starlight/Header.astro +++ b/site/src/components/starlight/Header.astro @@ -48,10 +48,6 @@ function linkClass(link: (typeof navLinks)[number], index: number): string | und /> -
- {shouldRenderSearch && } -
- +
+ {shouldRenderSearch && } +
+
@@ -87,7 +87,7 @@ function linkClass(link: (typeof navLinks)[number], index: number): string | und display: flex; align-items: center; justify-content: flex-start; - gap: 1rem; + gap: var(--ui-nav-link-gap); height: var(--sl-nav-height); min-height: var(--sl-nav-height); width: min( @@ -125,22 +125,22 @@ function linkClass(link: (typeof navLinks)[number], index: number): string | und filter: var(--ui-mark-filter); } - /* The bar is two groups: identity on the left, then search, navigation - and the theme control together on the right. The auto margin is the - seam, and it sits on the search box because search is the first - element of the right-hand group. + /* The bar is two groups: identity on the left, then navigation and the + controls on the right -- links, then search and the theme control + together at the end. The auto margin is the seam, on the links because + they begin the right-hand group. * - * Two earlier placements are worth not repeating. On the wordmark, the - * whole gap landed immediately after it, and since search was the next - * element search came to rest near the middle of the bar, reading as a - * stray control belonging to neither side -- measured at a 1367px bar, - * search at x=704, the centre to within a few pixels. On .docs-nav-links, - * search stayed pinned beside the wordmark at the far left, a long way - * from the navigation it belongs with. + * Search used to lead that group, before the links, so that the keyboard + * reached it first. It read as a stray box at one end of the links with + * the theme control at the other; grouped with the theme control it is + * one cluster of controls, as on most docs sites. The cost is keyboard + * order: search now comes after the nav links. Starlight's Ctrl+K / `/` + * shortcut still opens it from anywhere. * - * DOM order is unchanged: search still precedes the nav links, so it is - * reachable by keyboard before six nav items rather than after them. */ - .docs-header-search { + * An earlier placement worth not repeating: the seam on the wordmark put + * the whole gap straight after it, and whatever came next floated near the + * middle of the bar -- measured at a 1367px bar, search at x=704. */ + .docs-nav-links { margin-inline-start: auto; } @@ -149,9 +149,9 @@ function linkClass(link: (typeof navLinks)[number], index: number): string | und display: flex; align-items: center; justify-content: center; - gap: 1.15rem; + gap: var(--ui-nav-link-gap); min-width: 0; - font-size: 0.8125rem; + font-size: var(--ui-nav-font-size); height: var(--sl-nav-height); line-height: 1; } @@ -185,13 +185,13 @@ function linkClass(link: (typeof navLinks)[number], index: number): string | und * sits in that margin, negatively inset. */ .docs-nav-links a.nav-group-start { position: relative; - margin-inline-start: 1.3rem; + margin-inline-start: var(--ui-nav-group-gap); } .docs-nav-links a.nav-group-start::before { content: ""; position: absolute; - inset-inline-start: -0.65rem; + inset-inline-start: calc((var(--ui-nav-group-gap) + var(--ui-nav-link-gap) + 1px) / -2); top: 50%; width: 1px; height: 18px; @@ -203,14 +203,12 @@ function linkClass(link: (typeof navLinks)[number], index: number): string | und border-bottom-color: var(--ui-accent); } + /* Sized to its button. It was a fixed 168px box with a 135px button + centred in it, which added 16px either side on top of the row gap. */ .docs-header-search { - flex: 0 1 10.5rem; - width: 10.5rem; - max-width: 10.5rem; - min-width: 8.5rem; + flex: 0 0 auto; display: flex; align-items: center; - justify-content: center; height: var(--sl-nav-height); } @@ -251,17 +249,11 @@ function linkClass(link: (typeof navLinks)[number], index: number): string | und @media (max-width: 72rem) { .docs-topbar { - gap: 0.85rem; width: min(100%, calc(100vw - 2rem)); max-width: calc(100vw - 2rem); padding-inline: 1rem; } - .docs-nav-links { - gap: 0.75rem; - font-size: 0.78rem; - } - .docs-header-search { flex-basis: 8.75rem; width: 8.75rem; @@ -294,7 +286,6 @@ function linkClass(link: (typeof navLinks)[number], index: number): string | und @media (max-width: 72rem) { .docs-topbar { - gap: 0.75rem; width: min(100%, calc(100vw - 5.25rem)); max-width: calc(100vw - 5.25rem); justify-content: flex-start; @@ -310,11 +301,6 @@ function linkClass(link: (typeof navLinks)[number], index: number): string | und second auto margin on the same flex row splits the free space between the two rather than adding to it -- measured at 1142px, 206px of it landed between the search icon and the first link. */ - .docs-nav-links { - gap: 0.7rem; - font-size: 0.76rem; - } - .docs-header-search { flex: 0 0 auto; width: 2.5rem; diff --git a/site/src/components/starlight/MarkdownContent.astro b/site/src/components/starlight/MarkdownContent.astro index 9474a790..45678666 100644 --- a/site/src/components/starlight/MarkdownContent.astro +++ b/site/src/components/starlight/MarkdownContent.astro @@ -23,72 +23,15 @@ * inside it. */ import '@astrojs/starlight/style/markdown.css'; - -const { entry } = Astro.locals.starlightRoute; -// 'docs/cli' -> 'cli'. The section index arrives as the bare id 'docs', -// which the strip does not match -- see the same mapping in -// src/pages/docs/[...slug].md.ts, which serves these files. -const slug = entry.id === 'docs' ? 'index' : entry.id.replace(/^docs\//, ''); -const markdownHref = `/docs/${slug}.md`; +import CopyPage from './CopyPage.astro'; ---
- +
- - diff --git a/site/src/components/starlight/PageSidebar.astro b/site/src/components/starlight/PageSidebar.astro index e13e9541..e278c6f8 100644 --- a/site/src/components/starlight/PageSidebar.astro +++ b/site/src/components/starlight/PageSidebar.astro @@ -1,6 +1,7 @@ --- import MobileTableOfContents from 'virtual:starlight/components/MobileTableOfContents'; import TableOfContents from 'virtual:starlight/components/TableOfContents'; +import CopyPage from './CopyPage.astro'; const { toc } = Astro.locals.starlightRoute; --- @@ -49,6 +50,11 @@ const { toc } = Astro.locals.starlightRoute; {/* Narrow screens keep the collapsed dropdown. */}
+ {/* Copy page, pinned at the bar's end so it stays in reach while the + page scrolls; the wide-screen copy is above the content. */} +
+ +
) diff --git a/site/src/data/site-content/compare.ts b/site/src/data/site-content/compare.ts new file mode 100644 index 00000000..a3ee55ac --- /dev/null +++ b/site/src/data/site-content/compare.ts @@ -0,0 +1,90 @@ +import type { ComparisonColumn, ComparisonRow, SectionCopy } from './types'; + +// The comparison matrix. Every cell describes what ships, out of the box. +// +// Checked on 2026-09-24 against each project's own website, documentation and +// source: nmap 7.991 (nmap.org changelog, reference guide, NSE index), Angry IP +// Scanner 3.10.0 (angryip.org, the GitHub release and the source), Advanced IP +// Scanner 2.5.4594.1 (advanced-ip-scanner.com, its help pages, and Famatech's +// replies on radmin-club.com). NetsCLI's column was checked against this +// repository's code, not against the site copy. +// +// A dash means the tool's own documentation and source show no such feature. +// Where a feature exists but is undocumented -- Advanced IP Scanner's console +// version, which Famatech confirms but never describes -- the cell says so +// rather than guessing either way. + +export const compareCopy: SectionCopy = { + heading: 'How NetsCLI compares', + // No lead. One that listed what was compared and which versions said + // nothing a reader needs before the table; the dates and versions are in + // the comment above, where the next person to recheck the cells needs them. + leadHtml: '', +}; + +export const compareColumns: ComparisonColumn[] = [ + { name: 'NetsCLI', highlight: true }, + { name: 'nmap' }, + { name: 'Angry IP Scanner' }, + { name: 'Advanced IP Scanner' }, +]; + +// Ticks, not phrases. A version with a short phrase in every cell (one row +// per question a buyer asks, 2026-09-24) was accurate and unreadable: too much +// to take in, nothing to scan. A tick table is only honest if some rows go to +// the other tools, so some do: service versions and OS detection, where nmap +// goes further than netscli's partial answers; add-ons (nmap, +// Angry IP Scanner); remote actions (Advanced IP Scanner); and "Open source" +// is a tick for three of four. +// Rows every tool ticks (desktop app, naming devices by MAC vendor) are left +// out: they tell nobody anything. +export const compareRows: ComparisonRow[] = [ + { feature: 'Windows, macOS and Linux', cells: ['✓', '✓', '✓', 'Windows only'] }, + // Advanced IP Scanner installs a console exe that Famatech confirms but has + // never documented. + { feature: 'Command line', cells: ['✓', '✓', '✓', 'Undocumented'] }, + { feature: 'Terminal UI', cells: ['✓', '—', '—', '—'] }, + { feature: 'AI agents (MCP server)', cells: ['✓', '—', '—', '—'] }, + // NetsCLI and Angry IP Scanner do TCP connect scans. Advanced IP Scanner's + // docs cover checks for HTTP, HTTPS, FTP, RDP, Radmin and shared folders; + // Famatech sells port scanning as Advanced Port Scanner. + { feature: 'TCP port scan', cells: ['✓', '✓', '✓', 'Some services'] }, + // UDP: NetsCLI probes DNS, NTP, NetBIOS, SSDP and mDNS with the request + // each expects (#475). Angry IP Scanner can ping over UDP but scans only + // TCP ports (PortsFetcher). Advanced IP Scanner documents no UDP. + { feature: 'UDP port scan', cells: ['✓', '✓', '—', '—'] }, + // NetsCLI reads what SSH, web, FTP/mail and MySQL servers announce, and + // asks Redis/Valkey and Memcached one read-only question (#474): the + // common services, not nmap's -sV probe database. Angry IP Scanner's "Web + // detect" fetcher reads the HTTP Server header only. + { feature: 'Service versions', cells: ['Common services', '✓', 'Web servers only', '—'] }, + // nmap's -O fingerprints the TCP/IP stack with crafted packets (admin + // rights). NetsCLI's inspect gives a labelled hint from SMB, banners, MAC + // vendor and TTL instead (#476). Neither of the others tries. + { feature: 'OS detection', cells: ['Hints', '✓', '—', '—'] }, + // nmap's NSE runs Lua scripts (hundreds ship with it, vulnerability checks + // among them). Angry IP Scanner takes Java plugins that add fetchers and + // feeders (angryip.org documentation). NetsCLI and Advanced IP Scanner + // have no extension point. "Add-ons", not "Plugins or scripts": the + // latter read as "can't be scripted", and NetsCLI is driven from scripts + // through --json and the MCP server (the Command line and AI agents rows). + { feature: 'Add-ons (plugins, scripts)', cells: ['—', '✓', '✓', '—'] }, + // Record queries, not hostnames: all four name hosts by reverse DNS, so a + // row that read as "resolves hostnames" would be wrong for the others. + // nmap queries other record types and DNS-SD only from specific NSE + // scripts. Angry IP Scanner asks mDNS only to name a local host. + { feature: 'DNS record and mDNS queries', cells: ['✓', 'Via scripts', '—', '—'] }, + { feature: 'Remote desktop, shutdown, Wake-on-LAN', cells: ['—', '—', '—', '✓'] }, + // No output-format row. A "JSON output" row went to NetsCLI alone, but + // nmap writes XML, Angry IP Scanner CSV, XML, text and SQL, and Advanced + // IP Scanner CSV, XML and HTML: every tool has a machine-readable export, + // so singling out JSON read as a gotcha. + // nmap calls itself "free and open source" (NPSL, source available). + // Advanced IP Scanner publishes no source code or licence text. + { feature: 'Open source', cells: ['✓', '✓', '✓', '—'] }, +]; + +// When and against what, because every cell goes stale as the other tools +// release. Keep the versions in step with the header comment when rechecking. +export const compareNoteHtml = + 'Compared in September 2026 against NetsCLI 0.3.4, nmap 7.991, Angry IP Scanner 3.10.0 and Advanced IP Scanner 2.5. Spot something wrong? Open an issue.'; diff --git a/site/src/data/site-content/faq.ts b/site/src/data/site-content/faq.ts index 3ee5c773..cfb9201e 100644 --- a/site/src/data/site-content/faq.ts +++ b/site/src/data/site-content/faq.ts @@ -15,9 +15,9 @@ export const faq: FaqItem[] = [ { group: 'What it is', q: 'What is NetsCLI?', - a: 'NetsCLI is an open-source network scanner written in Rust. It discovers hosts on a subnet, scans TCP ports, queries DNS, traces routes, reads local interfaces and the ARP neighbor cache, and can capture packets when packet-capture support and the required system library are available. You can use it from the desktop app, terminal UI, CLI, or Model Context Protocol (MCP) server.', + a: 'NetsCLI is an open-source network scanner written in Rust. It discovers hosts on a subnet, scans TCP and UDP ports, queries DNS, traces routes, reads local interfaces and the ARP neighbor cache, and can capture packets when packet-capture support and the required system library are available. You can use it from the desktop app, terminal UI, CLI, or Model Context Protocol (MCP) server.', aHtml: - 'NetsCLI is an open-source network scanner written in Rust. It discovers hosts on a subnet, scans TCP ports, queries DNS, traces routes, reads local interfaces and the ARP neighbor cache, and can capture packets when packet-capture support and the required system library are available. You can use it from the desktop app, terminal UI, CLI, or Model Context Protocol (MCP) server.', + 'NetsCLI is an open-source network scanner written in Rust. It discovers hosts on a subnet, scans TCP and UDP ports, queries DNS, traces routes, reads local interfaces and the ARP neighbor cache, and can capture packets when packet-capture support and the required system library are available. You can use it from the desktop app, terminal UI, CLI, or Model Context Protocol (MCP) server.', }, { group: 'Install and updates', @@ -123,9 +123,9 @@ export const faq: FaqItem[] = [ { group: 'Network workflows', q: 'Can NetsCLI replace nmap, and does it have a TUI?', - a: 'NetsCLI covers the simpler cases nmap is often reached for: host discovery, basic TCP port scans, DNS lookups, and ARP-table inspection on a local network, with direct subcommands and structured output. It also ships a terminal UI — run netscli with no arguments to get an interactive, keyboard-driven scanner in the terminal, which nmap itself does not provide. For advanced service detection, NSE scripts, and OS fingerprinting, nmap remains the better tool.', + a: 'NetsCLI covers the simpler cases nmap is often reached for: host discovery, TCP and UDP port scans, DNS lookups, and ARP-table inspection on a local network, with direct subcommands and structured output. It also ships a terminal UI — run netscli with no arguments to get an interactive, keyboard-driven scanner in the terminal, which nmap itself does not provide. For advanced service detection, NSE scripts, and OS fingerprinting, nmap remains the better tool.', aHtml: - 'NetsCLI covers the simpler cases nmap is often reached for: host discovery, basic TCP port scans, DNS lookups, and ARP-table inspection on a local network, with direct subcommands and structured output. It also ships a terminal UI — run netscli with no arguments to get an interactive, keyboard-driven scanner in the terminal, which nmap itself does not provide. For advanced service detection, NSE scripts, and OS fingerprinting, nmap remains the better tool.', + 'NetsCLI covers the simpler cases nmap is often reached for: host discovery, TCP and UDP port scans, DNS lookups, and ARP-table inspection on a local network, with direct subcommands and structured output. It also ships a terminal UI — run netscli with no arguments to get an interactive, keyboard-driven scanner in the terminal, which nmap itself does not provide. For advanced service detection, NSE scripts, and OS fingerprinting, nmap remains the better tool.', }, { group: 'Network workflows', diff --git a/site/src/data/site-content/hero.ts b/site/src/data/site-content/hero.ts index a08ad0e0..85c72cdc 100644 --- a/site/src/data/site-content/hero.ts +++ b/site/src/data/site-content/hero.ts @@ -52,7 +52,7 @@ export const hero: Hero = { // it. "All on one Rust core" carries the same point as "each interface // calls the same Rust core, so results stay consistent" -- the reader who // needs the longer version is already reading /docs/. - 'Discover LAN devices, scan TCP ports, query DNS, and inspect hosts from the desktop app, terminal UI, CLI, or MCP server — all on one Rust core.', + 'Discover LAN devices, scan TCP and UDP ports, query DNS, and inspect hosts from the desktop app, terminal UI, CLI, or MCP server — all on one Rust core.', // `winget install netscli` leads, and the shell script follows. // // os-tabs.ts already swapped these per-OS at runtime -- Windows visitors diff --git a/site/src/data/site-content/install.ts b/site/src/data/site-content/install.ts index ef68108f..a20eb9f0 100644 --- a/site/src/data/site-content/install.ts +++ b/site/src/data/site-content/install.ts @@ -9,28 +9,22 @@ export const installCopy: SectionCopy = { const RELEASE_DOWNLOAD = 'https://github.com/fstubner/netscli/releases/latest/download'; -/** Shown on every direct .dmg / .msi row. +/** Shown on the direct .dmg rows and on the Homebrew cask. * - * The desktop installers are not code-signed yet (tracked separately — - * notarization needs a paid Apple Developer cert, Authenticode needs a - * Windows cert). Warning up front is better than someone hitting a - * Gatekeeper or SmartScreen dialog with no context and assuming the - * download is malware. */ -const MACOS_UNSIGNED_HINT = 'Unsigned — right-click → Open on first launch'; -/* Describes the row it is attached to, which is the direct .msi download. - * It used to end "winget verifies the hash" -- true of winget, and winget is - * not what this row does. Someone clicking Download gets the installer - * straight from GitHub Releases with nothing checking it, and was being told - * otherwise at the moment they did it. The checksums are real and published; - * this now points at them. + * The cask too: Homebrew quarantines what a cask downloads, and 5.0 + * deprecated `--no-quarantine`, the flag that skipped it. A cask install + * meets the same Gatekeeper block as a browser download. * - * Stated as the exception rather than labelling its opposite. Every package - * manager row used to carry a "Hash-verified" tag so this row would read as - * different -- four copies of it in one Windows panel, saying the unremarkable - * thing four times to make the remarkable thing stand out once. The - * verification is the norm; not having it is the news, so only the news is - * written down. */ -const WINDOWS_UNSIGNED_HINT = 'Unsigned — SmartScreen may warn. Checksums are published.'; + * The macOS app is not notarized (that needs a paid Apple Developer + * account). Warning up front is better than someone hitting a Gatekeeper + * dialog with no context and assuming the download is malware. + * + * It said "right-click → Open on first launch" until 2026-09. macOS 15 + * Sequoia removed that override: Control-click → Open now shows the same + * refusal with no Open button. Apple's support page for opening an app from + * an unknown developer gives only the System Settings route, which is what + * this names now. */ +const MACOS_UNSIGNED_HINT = 'Unsigned — open it once, then System Settings → Privacy & Security → Open Anyway'; export const installByPlatform: Record = { windows: { @@ -63,7 +57,6 @@ export const installByPlatform: Record = { { label: 'Installer', href: `${RELEASE_DOWNLOAD}/netscli-gui-windows-x86_64.msi`, - hint: WINDOWS_UNSIGNED_HINT, }, ], }, @@ -87,6 +80,7 @@ export const installByPlatform: Record = { // scoop, AUR and winget already name the two artifacts. label: 'Homebrew', command: 'brew install --cask fstubner/tap/netscli-gui', + hint: MACOS_UNSIGNED_HINT, }, { label: 'Apple Silicon', @@ -128,7 +122,7 @@ export const installByPlatform: Record = { * readers actually wanted buried two rows below it. */ desktop: [ { - label: 'Debian / Ubuntu', + label: 'Debian / Ubuntu (.deb)', href: `${RELEASE_DOWNLOAD}/netscli-gui-linux-x86_64.deb`, }, { @@ -177,7 +171,7 @@ export const tryCommands: TryCommand[] = [ * alternative route for every platform, which is what made it read as a wall * rather than a choice. */ export const installBinariesNote = - 'Rust users can cargo install netscli. Every asset is checksummed and signed with Sigstore cosign — see how to verify a download, plus standalone binaries and packet-capture builds.'; + 'Rust users can cargo install netscli. Every binary and installer is checksummed and signed with Sigstore cosign — see how to verify a download, plus standalone binaries and packet-capture builds.'; // Two things /llms.txt says that no page does: a build-from-source route, // listed after the per-platform quickstart, and any caveat a reader acting diff --git a/site/src/data/site-content/meta.ts b/site/src/data/site-content/meta.ts index 9748d6e2..cf32ad5d 100644 --- a/site/src/data/site-content/meta.ts +++ b/site/src/data/site-content/meta.ts @@ -15,17 +15,17 @@ export const meta: Meta = { // "inspect hosts", not "trace routes": the sentence attributes what it // lists to all four interfaces, and the MCP server has no traceroute tool. // `inspect_host` is a real MCP tool, so the swap keeps the claim true. - // Measured at 154 characters in the built page, one more than the 153 this - // replaced -- still inside the ~160 a search result shows, and the MCP - // mention this description was rewritten to protect is nowhere near the cut. + // "TCP and UDP" took it to 162, past the ~160 a search result shows, so + // the closer became the hero's "All on one Rust core." Check the length in + // the built page after any edit; the MCP mention must stay clear of the cut. description: - 'Discover LAN devices, scan TCP ports, query DNS, and inspect hosts from a desktop app, terminal UI, CLI, or MCP server. One Rust core, consistent results.', + 'Discover LAN devices, scan TCP and UDP ports, query DNS, and inspect hosts from a desktop app, terminal UI, CLI, or MCP server. All on one Rust core.', // Same scoping as the hero subhead: capture is not in any published desktop // installer, so this must not imply it ships with the app. It is what search // results and link previews show, which is where an inaccurate claim travels // furthest. ogDescription: - 'Discover LAN devices, scan TCP ports, query DNS, and inspect hosts from the desktop app, terminal UI, CLI, or MCP server backed by one Rust core. Packet capture in capture-enabled CLI builds.', + 'Discover LAN devices, scan TCP and UDP ports, query DNS, and inspect hosts from the desktop app, terminal UI, CLI, or MCP server backed by one Rust core. Packet capture in capture-enabled CLI builds.', siteName: 'NetsCLI', author: { name: 'Felix Stubner', url: 'https://github.com/fstubner' }, ogImage: 'https://netscli.com/assets/tui-discover.png', diff --git a/site/src/data/site-content/nav.ts b/site/src/data/site-content/nav.ts index f6ce4aef..fe2615ab 100644 --- a/site/src/data/site-content/nav.ts +++ b/site/src/data/site-content/nav.ts @@ -30,6 +30,7 @@ export interface NavLink { const allLinks: NavLink[] = [ { label: 'Features', section: 'surfaces', mobileGroup: 'site' }, + { label: 'Compare', section: 'compare', mobileGroup: 'site' }, { label: 'Install', section: 'install', mobileGroup: 'site' }, { label: 'FAQ', section: 'faq', mobileGroup: 'site' }, { label: 'Docs', href: '/docs/', mobileGroup: 'site' }, diff --git a/site/src/data/site-content/sections.ts b/site/src/data/site-content/sections.ts index 9af98ba5..288bbf6f 100644 --- a/site/src/data/site-content/sections.ts +++ b/site/src/data/site-content/sections.ts @@ -2,7 +2,7 @@ import type { LandingLayout, LandingSection } from './types'; // Which sections the landing page renders, in order. // -// The four are independent: each reads its own content file and none assumes +// The sections are independent: each reads its own content file and none assumes // what sits above it. So a product with no install story drops 'install' // rather than filling it with something weak, and one whose visitors ask // questions before they read features can put 'faq' second. @@ -10,7 +10,7 @@ import type { LandingLayout, LandingSection } from './types'; // A name that appears twice renders twice; a name whose content is empty // renders nothing. Dropping the last section is fine -- the footer is not in // this list, and neither is the nav. -export const sections: LandingSection[] = ['hero', 'surfaces', 'install', 'faq']; +export const sections: LandingSection[] = ['hero', 'surfaces', 'compare', 'install', 'faq']; // How the landing page is laid out above the fold, and the rhythm that // follows from it. diff --git a/site/src/data/site-content/types.ts b/site/src/data/site-content/types.ts index c4069f7b..9c528da5 100644 --- a/site/src/data/site-content/types.ts +++ b/site/src/data/site-content/types.ts @@ -212,6 +212,18 @@ export interface Analytics { cloudflareToken?: string; } +/** A comparison column. `highlight` marks this product's, which is tinted. */ +export interface ComparisonColumn { + name: string; + highlight?: boolean; +} + +/** A capability row. `cells` is one per column, in order: '✓', '—', or a word. */ +export interface ComparisonRow { + feature: string; + cells: string[]; +} + export interface SectionCopy { heading: string; /** HTML allowed — typically short tagline with an anchor link. */ @@ -223,7 +235,7 @@ export type LandingLayout = 'centered' | 'split'; /** A section the landing page can render. Adding one here means adding a * component for it in src/pages/index.astro's map. */ -export type LandingSection = 'hero' | 'surfaces' | 'install' | 'faq'; +export type LandingSection = 'hero' | 'surfaces' | 'compare' | 'install' | 'faq'; /** One group in the docs sidebar, as Starlight expects it. */ export interface DocsSection { diff --git a/site/src/layouts/Page.astro b/site/src/layouts/Page.astro index e7e52934..c5eede45 100644 --- a/site/src/layouts/Page.astro +++ b/site/src/layouts/Page.astro @@ -2,6 +2,7 @@ // Shared with the docs shell (astro.config.mjs customCss): the palette, the // code surface and the theme control. Then the landing page's own tier. import '../styles/tokens.css'; +import '../styles/nav-spacing.css'; import '../styles/code-surface.css'; import '../styles/landing/tokens.css'; import '../styles/landing/base.css'; diff --git a/site/src/pages/index.astro b/site/src/pages/index.astro index a491615e..9c74129f 100644 --- a/site/src/pages/index.astro +++ b/site/src/pages/index.astro @@ -3,6 +3,7 @@ import Page from '../layouts/Page.astro'; import Nav from '../components/Nav.astro'; import Hero from '../components/Hero.astro'; import Surfaces from '../components/Surfaces.astro'; +import Compare from '../components/Compare.astro'; import Install from '../components/Install.astro'; import Faq from '../components/Faq.astro'; import Footer from '../components/Footer.astro'; @@ -14,7 +15,7 @@ const githubRepo = site.social.repo; // One component per section name. The list in site-content/sections.ts is // the order; this is only the lookup, and a name with no entry here is a // type error rather than a silently missing section. -const COMPONENTS = { hero: Hero, surfaces: Surfaces, install: Install, faq: Faq }; +const COMPONENTS = { hero: Hero, surfaces: Surfaces, compare: Compare, install: Install, faq: Faq }; ---