feat(home): offer VS Code alongside Docker in the quick start

[guanzhousongmicrosoft]

What changed

The homepage quick start offers two paths to the same local database, as Terminal and VS Code tabs. Terminal is selected by default and keeps the original command and the public run-with-docker anchor.

The VS Code tab installs the extension and opens its DocumentDB Local setup wizard via vscode://ms-azuretools.vscode-documentdb/local.

Design review changes

A design and product review of the first version found the VS Code panel was written for someone who had already seen the wizard. The changes that came out of it:

Copy. The prerequisite now states plainly that the VS Code path still uses Docker and that the extension never installs Docker or changes the user's system, replacing the jargon "in your VS Code environment". Step 01 names what gets installed rather than pinning extension version 0.10.1, which is maintenance debt on a homepage and is noise for a new installer who gets the latest anyway. Step 02 was a four-action transcript of wizard buttons and is now click, allow, follow the wizard. Step 03 states the outcome, port and generated credentials, so the reader knows what they got. The fallback names the likely cause instead of treating "no VS Code", "no extension", and "old extension" identically.

The Docker steps were tightened in the same pass: the step that restated the command directly above it is gone, first-run pull time is called out, and the vague "continue with the docs or Linux packages for the setup you need" is now a concrete connect-and-query.

Structure. The tabs are Terminal and VS Code; labelling one "Docker" implied the other avoided Docker, when both start the same container. Install the extension is now the primary action and the deep link is secondary, matching the order of the steps — previously the most prominent control was the one that silently does nothing for a visitor without the extension. The card footer link follows the active tab and points at that path's full guide; "Download packages" is gone, since the hero already has "Download" pointing at the same page. Each panel links across to the other path, so neither is fully hidden behind a tab.

Presentation. The tablist gets a solid active state and larger hit targets (previously ~30px, under the 44px guideline), so it reads as a control rather than as a third row of small blue pills between the "Quick start" chip and the numbered step markers. The hero grid is now items-start: it was items-center, and because the card is the taller column, every tab switch nudged the DocumentDB headline vertically. Home and End keys move between tabs, completing the ARIA authoring practices for the pattern.

Known gap: the VS Code guide

The review surfaced a contradiction this PR cannot fix on its own. /docs/getting-started/vscode-quickstart still describes only the manual flow — run the container yourself, then create a New Local Connection and disable TLS — and never mentions the setup wizard. A reader who follows this homepage tab and then opens the guide finds instructions that disagree with it.

That page is not in this repository. articles/** is gitignored and cloned at build time from documentdb/docs per content.config.json, so the fix has to land there. documentdb/docs#77 rewrites that guide to lead with the wizard, keeping the manual flow as an explicit alternative (its hardened commands from documentdb/docs#75 are preserved byte-for-byte). This PR already links the VS Code tab at that page, so the two should merge together — or this one can wait on it.

Extension compatibility

Verified against microsoft/vscode-documentdb main (013e429f) and published releases on 2026-09-10, reading extension source rather than release notes:

• vscodeUriHandler.ts routes /local as shorthand for /local/documentdb, so the published URL needs no change or query parameters, and it shows a modal confirmation before anything opens.
• LocalQuickStart.tsx drives introduction → Continue → configure → Start DocumentDB Local → Open Connection.
• quickStartTypes.ts confirms the container name, persistent volume, port 10260, and generated credentials the steps now promise.
• package.json contributes Set up DocumentDB Local under the DocumentDB category, so the Command Palette fallback string is exact.
• "Linux containers required" is a real Docker readiness state, so the prerequisite is accurate.

The deep link shipped in v0.10.1, still the latest published release. 0.10.2 exists only on main; nothing on this page depends on it shipping.

Validation

Regression coverage asserts the terminal default and public anchor, tab/panel relationships, the tab labels, link order and URLs, the Docker prerequisite and no-system-changes promise, the setup outcome, the absence of a pinned version number, the per-path guide link, and the fallback command. 91 tests across 5 files pass through the project's own vitest.config.ts, with the latest main merged in.

npm install still fails in this environment with a 404 for Vite's pinned postcss@8.5.28 on the configured package-feed proxy. Runtime dependencies were installed into a scratch directory and linked in for the test run; no dependency versions, package.json, or lockfiles were modified. GitHub Actions remains the authority.

Browser-to-VS-Code handoff and Docker provisioning have not been exercised end to end; the compatibility claims are verified from extension source and the released tag.

[guanzhousongmicrosoft]

Closing in favor of #179, which carries identical commits from my personal account. Continue review there.