Add branded GitHub Pages site

[KSemenenko]

Summary

• add a custom static site generator that renders README.md into a branded landing page
• add a GitHub Pages workflow that validates on PRs and deploys from main
• keep the existing custom domain by publishing a CNAME and a lightweight favicon

Verification

• npm run build
• opened the generated site locally and verified the rendered layout

[Copilot]

Pull request overview

Adds a small Node-based static site build pipeline and a GitHub Pages workflow to publish a branded landing page generated from the repository’s README.md, including custom domain support.

Changes:

• Introduces a Node script (scripts/build-site.mjs) that renders README.md into a styled dist/index.html (with syntax highlighting + anchored headings + stats + TOC).
• Adds a GitHub Pages Actions workflow to build on PRs and deploy on main.
• Adds site assets and styling (CSS, favicon, CNAME) and updates .gitignore for Node build outputs.

Reviewed changes

Copilot reviewed 5 out of 8 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
website/site.css	Adds the branded page styling for the generated site.
scripts/build-site.mjs	Implements the static site generator that converts README.md to dist/index.html.
public/favicon.svg	Adds the favicon included in the published site.
public/CNAME	Preserves the custom domain for GitHub Pages deployment.
package.json	Defines the build script and dependencies for site generation.
package-lock.json	Locks dependency versions for reproducible builds in CI.
.gitignore	Ignores node_modules/ and dist/ from the Node-based site build.
.github/workflows/pages.yml	Builds on PRs and deploys the generated site to GitHub Pages from main.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The workflow uses a single global concurrency group (group: pages). This will cause runs from different PRs and pushes to main to cancel each other, potentially interrupting a production deploy when a PR validation run starts (and vice versa). Consider scoping the concurrency group to the ref (e.g., include ${{ github.ref }}) or separating build vs deploy groups so PR builds don't cancel main deployments.

Suggested change

	group: pages
	group: pages-${{ github.ref }}