feat(website): new Angular-based documentation website (#1533) * feat(website): add new Angular documentation website Co-Authored-By: Claude Fable 5 * fix(website): address CodeRabbit review feedback on PR #1533 - ssr.js: don't cache a rejected dynamic import, guard the 500 response when headers were already sent by the SSR stream - auth: add CSRF protection to the GitHub OAuth flow (random nonce in a short-lived HttpOnly cookie, verified on callback) and harden siteOrigin against x-forwarded-host spoofing (SITE_ORIGIN wins, x-forwarded-proto decides the scheme, first forwarded host only) - github-api: bound the in-memory cache with eviction, add a request timeout and 403/429 backoff retries, and return partial leaderboard results with a short TTL instead of discarding every fetched page - solutions: branch templates on a `loaded` flag so SSR no longer renders a false "loaded and empty" state while the httpResource is disabled - docs: correct the view-transition-name uniqueness rule, show a Signal `.update()` in the CRUD example, split in-app navigation from page unload in the form-data challenge, fix the `forms-child-forms` test command and the `counter.component.cy.ts` spec name, align the challenge-creation guide with the website content pipeline, and recommend `--force-with-lease` over `push -f` Co-Authored-By: Claude Opus 5 (1M context) * feat(website): gate Google Analytics and AdSense behind a consent banner Neither Google script is loaded before the visitor makes a choice. index.html now only declares Consent Mode v2 defaults (everything denied), and the new Consent service injects gtag.js and adsbygoogle.js — and sends the consent update — only on acceptance. The choice is remembered in localStorage; rejecting after a previous acceptance flips the signals back to denied and expires the _ga/_gid cookies. The banner is browser-only so it never lands in the prerendered HTML, and a "Cookie settings" control in the landing footer and the docs sidebar lets visitors change their mind. Co-Authored-By: Claude Opus 5 (1M context) * fix(website): make the consent banner stand out The banner blended into the dark page. It is now a floating card with a lighter surface, a pink ring and a shadow, over a dimmed scrim. The scrim and the outer wrapper are pointer-events-none so the site stays usable while the choice is pending, matching aria-modal="false". Co-Authored-By: Claude Opus 5 (1M context) * feat(website): add light/dark mode with a header toggle The site was dark-only with hardcoded dark Tailwind classes. Dark mode is now driven by a .dark class on (class-based @custom-variant), managed by a new Theme service that persists the choice in localStorage and falls back to the OS preference. An inline script in index.html applies the theme before first paint to avoid flashing the wrong mode. Every template gains light defaults with dark: variants. Code blocks use Shiki dual themes (github-light/dark-default) switched in CSS, the PR diff viewer carries both token colors and recolors reactively, and giscus follows the active theme. Co-Authored-By: Claude Fable 5 * feat(website): add in-browser Monaco editor for challenge starter code The content generator now bundles each challenge's starter app (apps//-/src) into lazy-loadable modules, and a new /challenges/:category/:slug/editor page shows them in a Monaco editor (loaded from CDN) with a file tree, modified indicators, reset actions and light/dark theme sync. Challenge pages with starter code get a "Solve in editor" button. Co-Authored-By: Claude Fable 5 * feat(website): run challenges in a WebContainer and submit answers as PRs The editor page can now serve a challenge's app (synthesized standalone Angular project, npm install + ng serve in a WebContainer with live preview iframe), run its jest/vitest tests with streamed output, and open an Answer: pull request from the signed-in user's fork via a new /api/challenges/:number/submit endpoint. The generator bundles dependency versions, test-runner metadata and base64 assets per challenge; the editor route gets COOP/COEP headers for cross-origin isolation. Co-Authored-By: Claude Fable 5 * revert(website): remove in-browser code editor and WebContainer runner Reverts the Monaco editor page, the WebContainer challenge runner and the answer-submission endpoint, along with the generator changes that bundled starter code, dependency versions and assets per challenge. This reverts commits 5ff16d39 and 1efb2192. Co-Authored-By: Claude Opus 5 (1M context) * feat: one-click challenge onboarding — CLI, IDE deep links and Codespaces Adds a "Try this challenge" button on every challenge page opening a dialog with three paths: a new zero-dependency `angular-challenges` npm CLI (`start ` forks/clones/installs/branches/serves, `submit` pushes and opens the prefilled Answer: PR page), fork-on-click (new /api/fork endpoint) with VS Code / Cursor / JetBrains clone deep links, and a GitHub Codespaces link backed by a new devcontainer. Co-Authored-By: Claude Fable 5 * fix(cli): normalize bin path so npm publish keeps the executable Co-Authored-By: Claude Fable 5 * feat(website): manual-setup guides in try-challenge dialog; safer CLI branch switching Replace the fork + IDE deep-link section with links to the Getting Started and Resolve a Challenge guides (and drop the now-unused /api/fork endpoint). The CLI now offers to commit uncommitted work before switching answer branches, and `submit` offers to commit pending changes before pushing. Co-Authored-By: Claude Fable 5 * chore(cli): bump to 0.1.1 for the branch-switch commit guards Co-Authored-By: Claude Fable 5 * style(website): larger, airier try-challenge dialog Co-Authored-By: Claude Fable 5 * docs(website): clarify the npx command runs in a terminal Co-Authored-By: Claude Fable 5 * fix(website): keep docs, landing and solutions readable on narrow screens Long tokens (npx commands, paths, URLs) no longer widen the page, wide markdown tables scroll in place, and the header, landing, leaderboard and solutions layouts reflow instead of overflowing. Co-Authored-By: Claude Opus 5 (1M context) * feat(cli): ask where to clone the fork The clone used to land in whatever folder the command was run from. `start` now prompts for a destination (default ./angular-challenges), accepts ~ paths, and nests into /angular-challenges when the folder already has files in it. `--dir ` skips the question for scripted runs, and prompts fall back to their default when stdin is not a TTY instead of hanging. Co-Authored-By: Claude Opus 5 (1M context) * fix(website): address review comments on the docs rework - expire analytics cookies on every parent domain, including AdSense ones - pass the request timeout to the direct GitHub fetch calls - reset the PR reaction state when the router reuses the diff component - tell challenge authors to copy, not move, the generated Markdown Co-Authored-By: Claude Opus 5 (1M context) --------- Co-authored-by: Claude Fable 5

Uh oh!