Skip to content

Commit 5c270f8

Browse files
fstubnerfstubner
committed
Landing copy: FAQ names every desktop install and the real platforms, no pipeline words; CLI card lists CSV and Markdown
1 parent bcc2d06 commit 5c270f8

4 files changed

Lines changed: 23 additions & 22 deletions

File tree

‎site/src/data/site-content/faq.ts‎

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ import { INSTALL_SH_COMMAND } from './install-urls';
33

44
export const faqCopy: SectionCopy = {
55
heading: 'FAQ',
6-
leadHtml: 'The questions people actually ask before installing.',
6+
leadHtml: 'Common questions before installing.',
77
};
88

99
// Note: `a` (plain text) is embedded verbatim into JSON-LD structured data
@@ -29,19 +29,20 @@ export const faq: FaqItem[] = [
2929
// search engine and answer engine reads. The visible `aHtml` below was
3030
// already a template literal and rendered correctly, which is why the
3131
// page looked fine.
32-
a: `Install the netscli package for the CLI, terminal UI, and MCP server. On Windows, run: winget install netscli (the full identifier fstubner.netscli also works). On Linux or macOS, run: ${INSTALL_SH_COMMAND}. For the Windows desktop app, run: winget install netscli-gui. With Rust installed you can also run: cargo install netscli. Prebuilt binaries and desktop installers are attached to GitHub releases when available for that platform.`,
32+
a: `Install the netscli package for the CLI, terminal UI, and MCP server. On Windows, run: winget install netscli (the full identifier fstubner.netscli also works). On Linux or macOS, run: ${INSTALL_SH_COMMAND}. For the desktop app, run winget install netscli-gui on Windows or brew install --cask fstubner/tap/netscli-gui on macOS, or download it from GitHub releases; Linux has a .deb and an AppImage. With Rust installed you can also run: cargo install netscli.`,
3333
aHtml: `
3434
<p>Install the <code>netscli</code> package for the CLI, terminal UI, and MCP server:</p>
3535
<div class="faq-command-list" aria-label="Install commands">
3636
<div class="faq-command"><span>Windows</span><code>winget install netscli</code></div>
3737
<div class="faq-command"><span>Linux/macOS</span><code>${INSTALL_SH_COMMAND}</code></div>
3838
<div class="faq-command"><span>Rust</span><code>cargo install netscli</code></div>
3939
</div>
40-
<p>Install the Windows desktop app separately:</p>
41-
<div class="faq-command-list" aria-label="Desktop app install command">
40+
<p>Install the desktop app separately:</p>
41+
<div class="faq-command-list" aria-label="Desktop app install commands">
4242
<div class="faq-command"><span>Windows app</span><code>winget install netscli-gui</code></div>
43+
<div class="faq-command"><span>macOS app</span><code>brew install --cask fstubner/tap/netscli-gui</code></div>
4344
</div>
44-
<p>Prebuilt binaries and desktop installers for Windows, Linux, and macOS are attached to <a href="https://github.com/fstubner/netscli/releases/latest">GitHub releases</a> when available for that platform.</p>
45+
<p>Linux has a <code>.deb</code> and an AppImage. Every download is on the <a href="https://github.com/fstubner/netscli/releases/latest">GitHub releases page</a>.</p>
4546
`,
4647
},
4748
{
@@ -54,9 +55,9 @@ export const faq: FaqItem[] = [
5455
{
5556
group: 'Install and updates',
5657
q: 'Does NetsCLI work on Windows, macOS, and Linux?',
57-
a: 'Yes. Release artifacts target Windows, macOS, and Linux. CLI/TUI binaries are published for common x86_64 and aarch64 targets, including macOS Intel and Apple Silicon. The desktop app is published as Windows, macOS, and Linux installers where the release workflow supports that platform.',
58+
a: 'Yes. The CLI and terminal UI are published for Windows (x86_64), macOS (Intel and Apple Silicon) and Linux (x86_64 and ARM64). The desktop app is published for Windows and Linux (x86_64) and macOS (Intel and Apple Silicon).',
5859
aHtml:
59-
'Yes. Release artifacts target Windows, macOS, and Linux. CLI/TUI binaries are published for common <code>x86_64</code> and <code>aarch64</code> targets, including macOS Intel and Apple Silicon. The desktop app is published as Windows, macOS, and Linux installers where the release workflow supports that platform.',
60+
'Yes. The CLI and terminal UI are published for Windows (x86_64), macOS (Intel and Apple Silicon) and Linux (x86_64 and ARM64). The desktop app is published for Windows and Linux (x86_64) and macOS (Intel and Apple Silicon).',
6061
},
6162
{
6263
group: 'What it is',
@@ -68,9 +69,9 @@ export const faq: FaqItem[] = [
6869
{
6970
group: 'Limits and dependencies',
7071
q: 'Does NetsCLI require libpcap or other system dependencies?',
71-
a: 'Not for the normal scan, discovery, DNS, ARP, ping, trace, or interface workflows. Packet capture is the exception: it requires libpcap on Linux/macOS or Npcap on Windows at runtime, and only works in builds compiled with packet-capture support.',
72+
a: 'Not for the normal scan, discovery, DNS, ARP, ping, trace, or interface workflows. Packet capture is the exception: it requires libpcap on Linux/macOS or Npcap on Windows at runtime, and only works in the separate packet-capture downloads.',
7273
aHtml:
73-
'Not for the normal scan, discovery, DNS, ARP, ping, trace, or interface workflows. Packet capture is the exception: it requires libpcap on Linux/macOS or Npcap on Windows at runtime, and only works in builds compiled with packet-capture support.',
74+
'Not for the normal scan, discovery, DNS, ARP, ping, trace, or interface workflows. Packet capture is the exception: it requires libpcap on Linux/macOS or Npcap on Windows at runtime, and only works in the separate packet-capture downloads.',
7475
},
7576
{
7677
group: 'Network workflows',
@@ -87,21 +88,21 @@ export const faq: FaqItem[] = [
8788
// folders and remote shutdown, and a comparison that omitted the thing a
8889
// reader can see on that page in ten seconds would discredit the rest of
8990
// the answer.
90-
a: 'NetsCLI overlaps with those tools for common LAN discovery tasks: finding live hosts, scanning TCP ports, resolving hostnames, and showing MAC vendors from the local ARP cache. It is not a drop-in clone of either. Advanced IP Scanner is Windows-only and closed-source freeware. NetsCLI runs on Windows, macOS, and Linux, is MIT-licensed, and offers the same scans from a desktop app, a terminal UI, a CLI, and an MCP server, with JSON and YAML output. Angry IP Scanner is also open source and cross-platform, and ships its own command-line interface. What NetsCLI does not do is remote administration: Advanced IP Scanner can open shared folders, control machines over RDP or Radmin, and switch them off remotely, and NetsCLI has no equivalent.',
91+
a: 'NetsCLI overlaps with those tools for common LAN discovery tasks: finding live hosts, scanning TCP ports, resolving hostnames, and showing MAC vendors from the local ARP cache. It is not a drop-in clone of either. Advanced IP Scanner is Windows-only and closed-source freeware. NetsCLI runs on Windows, macOS, and Linux, is MIT-licensed, and offers the same scans from a desktop app, a terminal UI, a CLI, and an MCP server, with JSON, YAML, CSV and Markdown output. Angry IP Scanner is also open source and cross-platform, and ships its own command-line interface. What NetsCLI does not do is remote administration: Advanced IP Scanner can open shared folders, control machines over RDP or Radmin, and switch them off remotely, and NetsCLI has no equivalent.',
9192
aHtml:
92-
'NetsCLI overlaps with those tools for common LAN discovery tasks: finding live hosts, scanning TCP ports, resolving hostnames, and showing MAC vendors from the local ARP cache. It is not a drop-in clone of either. Advanced IP Scanner is Windows-only and closed-source freeware. NetsCLI runs on Windows, macOS, and Linux, is MIT-licensed, and offers the same scans from a <a href="#surfaces">desktop app, terminal UI, CLI, and MCP server</a>, with <code>--json</code> and <code>--yaml</code> output. Angry IP Scanner is also open source and cross-platform, and ships its own command-line interface. What NetsCLI does not do is remote administration: Advanced IP Scanner can open shared folders, control machines over RDP or Radmin, and switch them off remotely, and NetsCLI has no equivalent.',
93+
'NetsCLI overlaps with those tools for common LAN discovery tasks: finding live hosts, scanning TCP ports, resolving hostnames, and showing MAC vendors from the local ARP cache. It is not a drop-in clone of either. Advanced IP Scanner is Windows-only and closed-source freeware. NetsCLI runs on Windows, macOS, and Linux, is MIT-licensed, and offers the same scans from a <a href="#surfaces">desktop app, terminal UI, CLI, and MCP server</a>, with <code>--json</code>, <code>--yaml</code>, <code>--csv</code> and <code>--md</code> output. Angry IP Scanner is also open source and cross-platform, and ships its own command-line interface. What NetsCLI does not do is remote administration: Advanced IP Scanner can open shared folders, control machines over RDP or Radmin, and switch them off remotely, and NetsCLI has no equivalent.',
9394
},
9495
{
9596
group: 'Network workflows',
9697
q: 'How do I find devices on my home network with NetsCLI?',
97-
a: 'Run `netscli discover` from a machine on the network, or pass a subnet explicitly with `netscli discover <subnet>`. NetsCLI probes the range, then adds reverse DNS, ARP cache data, MAC addresses, and OUI vendor names when the operating system has that information available.',
98+
a: 'Run `netscli discover` from a machine on the network, or pass a subnet explicitly with `netscli discover <subnet>`. NetsCLI probes the range, then adds reverse DNS, ARP cache data, MAC addresses, and the device maker when the operating system has that information available.',
9899
aHtml: `
99100
<p>Run discovery from any machine on the network:</p>
100101
<div class="faq-command-list" aria-label="Discovery commands">
101102
<div class="faq-command"><span>Auto-detect</span><code>netscli discover</code></div>
102103
<div class="faq-command"><span>Specific subnet</span><code>netscli discover &lt;subnet&gt;</code></div>
103104
</div>
104-
<p>NetsCLI probes the range, then adds reverse DNS, ARP cache data, MAC addresses, and OUI vendor names when the operating system has that information available.</p>
105+
<p>NetsCLI probes the range, then adds reverse DNS, ARP cache data, MAC addresses, and the device maker when the operating system has that information available.</p>
105106
`,
106107
},
107108
{
@@ -130,16 +131,16 @@ export const faq: FaqItem[] = [
130131
{
131132
group: 'Network workflows',
132133
q: 'Is there a netscan command for Linux or Windows?',
133-
a: 'There is no standard netscan command on Linux, macOS, or Windows — it is not part of any of those systems. People searching for one usually want a command-line network scanner, which is what NetsCLI is: netscli discover lists live hosts on your subnet, netscli scan checks TCP ports on a host, and netscli sweep does both across a range. Several unrelated third-party tools also use the name NetScan, so check which one you mean before installing.',
134+
a: 'There is no standard netscan command on Linux, macOS, or Windows. People searching for one usually want a command-line network scanner, which is what NetsCLI is: netscli discover lists live hosts on your subnet, netscli scan checks TCP or UDP ports on a host, and netscli sweep does both across a range. Several unrelated third-party tools also use the name NetScan, so check which one you mean before installing.',
134135
aHtml:
135-
'<p>There is no standard <code>netscan</code> command on Linux, macOS, or Windows — it is not part of any of those systems. People searching for one usually want a command-line network scanner, which is what NetsCLI is:</p><div class="faq-command-list" aria-label="Scanning commands"><div class="faq-command"><span>Live hosts</span><code>netscli discover</code></div><div class="faq-command"><span>Ports on a host</span><code>netscli scan router.local -p 22,80,443</code></div><div class="faq-command"><span>Both, across a range</span><code>netscli sweep</code></div></div><p>Several unrelated third-party tools also use the name NetScan, so check which one you mean before installing.</p>',
136+
'<p>There is no standard <code>netscan</code> command on Linux, macOS, or Windows. People searching for one usually want a command-line network scanner, which is what NetsCLI is:</p><div class="faq-command-list" aria-label="Scanning commands"><div class="faq-command"><span>Live hosts</span><code>netscli discover</code></div><div class="faq-command"><span>Ports on a host</span><code>netscli scan router.local -p 22,80,443</code></div><div class="faq-command"><span>Both, across a range</span><code>netscli sweep</code></div></div><p>Several unrelated third-party tools also use the name NetScan, so check which one you mean before installing.</p>',
136137
},
137138
{
138139
group: 'Network workflows',
139140
q: 'What is the difference between scan, inspect, discover, and sweep?',
140-
a: 'Use scan when you already know a host and want TCP port status. Use inspect when you want a host profile that combines reachability, reverse DNS, and optional port checks. Use discover to find reachable devices on a subnet. Use sweep when you want discovery plus open-port checks across the discovered hosts.',
141+
a: 'Use scan when you already know a host and want TCP or UDP port status. Use inspect when you want a host profile: reachability, reverse DNS, MAC address and maker, an OS hint, and optional port checks. Use discover to find reachable devices on a subnet. Use sweep when you want discovery plus open-port checks across the discovered hosts.',
141142
aHtml:
142-
'Use <code>scan</code> when you already know a host and want TCP port status. Use <code>inspect</code> when you want a host profile that combines reachability, reverse DNS, and optional port checks. Use <code>discover</code> to find reachable devices on a subnet. Use <code>sweep</code> when you want discovery plus open-port checks across the discovered hosts.',
143+
'Use <code>scan</code> when you already know a host and want TCP or UDP port status. Use <code>inspect</code> when you want a host profile: reachability, reverse DNS, MAC address and maker, an OS hint, and optional port checks. Use <code>discover</code> to find reachable devices on a subnet. Use <code>sweep</code> when you want discovery plus open-port checks across the discovered hosts.',
143144
},
144145
{
145146
group: 'Limits and dependencies',

‎site/src/data/site-content/hero.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ export const hero: Hero = {
7070
heroImage: '/assets/tui-discover.png',
7171
heroImageWebp: '/assets/tui-discover.webp',
7272
heroImageAlt:
73-
'netscli terminal UI running /discover with sanitized lab hostnames, vendors, and response times',
73+
'netscli terminal UI running /discover with demo hostnames, vendors, and response times',
7474
heroImageWidth: 1640,
7575
heroImageHeight: 930,
7676
sourceUrl: 'https://github.com/fstubner/netscli',

‎site/src/data/site-content/meta.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ export const meta: Meta = {
3030
author: { name: 'Felix Stubner', url: 'https://github.com/fstubner' },
3131
ogImage: 'https://netscli.com/assets/tui-discover.png',
3232
ogImageAlt:
33-
'netscli terminal UI running /discover with sanitized lab hostnames, vendors, and response times',
33+
'netscli terminal UI running /discover with demo hostnames, vendors, and response times',
3434
faviconPath: '/favicon.svg',
3535
themeColor: '#111',
3636
};

‎site/src/data/site-content/surfaces.ts‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ export const surfaces: SurfaceCard[] = [
1515
src: '/gui-scan.png',
1616
webp: '/gui-scan.webp',
1717
alt:
18-
'NetsCLI Desktop dark theme scan view showing sanitized demo port results, row details, command preview, and status bar',
18+
'NetsCLI Desktop dark theme scan view showing demo port results, row details, command preview, and status bar',
1919
width: 1377,
2020
height: 740,
2121
},
@@ -28,7 +28,7 @@ export const surfaces: SurfaceCard[] = [
2828
src: '/assets/tui-discover.png',
2929
webp: '/assets/tui-discover.webp',
3030
alt:
31-
'netscli terminal UI running /discover with sanitized lab hostnames, vendors, and response times',
31+
'netscli terminal UI running /discover with demo hostnames, vendors, and response times',
3232
width: 1640,
3333
height: 930,
3434
},
@@ -37,7 +37,7 @@ export const surfaces: SurfaceCard[] = [
3737
{
3838
title: 'Command line',
3939
body:
40-
'Use the CLI for repeatable diagnostics and automation. Network operations expose <code>--json</code> and <code>--yaml</code> output, so scripts and other tools can consume the same data the desktop app displays.',
40+
'Use the CLI for repeatable diagnostics and automation. Network operations take <code>--json</code> and <code>--yaml</code>, and lists also <code>--csv</code> and <code>--md</code>, so scripts and other tools can consume the same data the desktop app displays.',
4141
// `--resolve` on the discover line is load-bearing, not decoration.
4242
// `hostname` is only populated when the flag is passed (core's
4343
// discover.rs guards the reverse-lookup pass on it), so without it this

0 commit comments

Comments
 (0)