Docs gaps surfaced by site search (no-result queries)

[bartlomieju]

Site search logs show several frequent queries that return no useful result —
topics people expect in the docs but can't find. Capturing them here as
pages/topics to add or fix. (Numbers are total queries over the sample period.)

Pages to add

• Model Context Protocol (MCP) — 34 queries, no page. Highest demand.
• DOMParser / HTML parsing — 30 queries (DOMParser + domparser). Not
  built in; needs a how-to pointing at deno-dom / linkedom and explaining
  why it isn't a global.
• denort — 19 queries. The runtime-only binary that deno compile
  produces/uses is undocumented.
• tsgo — 13 queries. TypeScript's native compiler — at least a note on
  where Deno stands on it.

Existing content that isn't findable

• minimumDependencyAge — 40 queries (minimumDependencyAge +
  minimum-dependency-age), no result. This is a real deno.json supply-chain
  setting; document it in the deno.json reference and the dependency-management
  guide.
• Windows installation — ~13 queries are the install command itself
  (irm https://deno.land/install.ps1 | iex) and the Windows binary
  (deno-x86_64-pc-windows-msvc.zip). The install / Windows content isn't
  surfacing in search; worth checking headings/indexing.

Popular features that may want clearer entry points

These do return results, but they're among the very top searches overall, so
they may deserve more prominent homes:

• SQLite (sqlite) and Deno KV (kv) — both in the top 10 queries.