plan: nxdns.sh landing page settled; doq waits on a quic stack, dnscrypt is out

PLAN.md

@@ -37,9 +37,10 @@ Serves a household LAN (≈2–20 devices). Portfolio-grade public repo with ext
 - Partial-segment wildcards (`ads*.example.com`) as a rule kind. The regex kind covers the need without a second globbing dialect.
 - DHCP server.
 - DNSSEC validation (DO bit passthrough only).
-- DoQ (QUIC), HTTP/2 upstream transport.
+- DoQ (DNS over QUIC). Out of scope until the Zig stdlib, or an equivalent dependency, provides QUIC; neither the stdlib nor mbedTLS does at 0.16.0. This is the one conditional entry in this list.
+- HTTP/2 upstream transport.
+- DNSCrypt. It is older than DoH and DoT and not an IETF standard, and DoH and DoT already cover encrypted DNS.
 - Clustering / distributed state.
-- Project website. The repository, its README and `docs/` are the whole published surface.
 
 ---
 

website/PLAN.md

@@ -1,6 +1,6 @@
 # nxdns.sh — marketing and docs website plan
 
-Agreed in an interview on 2026-08-15. This directory will hold the site's source.
+Agreed in an interview on 2026-08-15, revised on 2026-10-02 and 2026-10-19 (screenshots in, section order set, the personal story moved to the owner's blog). This directory will hold the site's source.
 
 ## Purpose
 
@@ -19,13 +19,14 @@ Convince, then teach. A marketing front page sells the project; the docs sit one
 
 ## Landing page
 
-Three sections:
+Four sections, in this order:
 
-1. Hero: one-line pitch and a copyable install command. Releases 0.0.1–0.0.3 exist, so the command is real.
-2. Feature grid: filtering, config-as-code, DoH/DoT, per-client groups, metrics, query log.
-3. Comparison table vs Pi-hole, AdGuard Home, Technitium — short, only to help people choose.
+1. Hero: the README pitch — "A DNS sinkhole for your LAN. It blocks the names you do not want, and forwards the rest over an encrypted connection." — and a copyable install command in two tabs: Docker compose first, the signed tarball second. The registry allows anonymous pulls (verified 2026-10-02 against v0.0.21), so the Docker tab works without an account.
+2. Screenshots of the web UI, taken from a running instance with realistic data: Overview, Activity (with a query's provenance), Clients, Diagnostics.
+3. Feature grid: filtering, config-as-code, DoH/DoT, per-client groups, metrics, query log.
+4. Comparison table vs Pi-hole, AdGuard Home, Technitium — only to help people choose. Seven rows: how it ships; config as a file in git that the tool converges onto; encrypted upstreams built in; serves DoH/DoT to clients; signed, reproducible releases; DHCP server; DNSSEC validation. The last two are rows nxdns loses, kept because a table that only lists wins does not help anyone choose. Competitor cells were checked against Pi-hole 6.5 (FTL 6.8), AdGuard Home 0.107.79 and Technitium 15.6.2 on 2026-10-19.
 
-The pitch leads with what nxdns does, not with attacks on the incumbents. No screenshots.
+The pitch leads with what nxdns does, not with attacks on the incumbents. The page is about the tool: why the owner built it is a blog article, not a landing-page section.
 
 ## Docs section
 
@@ -38,7 +39,7 @@ The pitch leads with what nxdns does, not with attacks on the incumbents. No scr
 - Clean technical. Light default with a dark toggle.
 - Orange/amber accent.
 - Brand is the lowercase `nxdns` wordmark in a distinctive typeface. No drawn logo.
-- Copy tone: personal / indie, first person — why I built it and what it fixes — in the honest voice the docs already use.
+- Copy tone: the honest, direct voice the docs already use, about the tool. The personal story is the blog's.
 
 ## Links
 
@@ -47,5 +48,4 @@ Source links point to `git.mial.net/mokhtar/nxdns` only. No GitHub mirror.
 ## Open questions
 
 1. Wordmark typeface — resolve in the design pass.
-2. Does the Gitea container registry allow anonymous pulls? That decides whether the hero shows `docker run` or the binary install from INSTALL.md.
-3. Fact-check the comparison table against current competitor versions before publication.
+2. Re-check the comparison cells against the then-current competitor versions before publication. AdGuard Home had a 1.0 beta on 2026-09-30, so its cells are the most likely to move.