[mategogiberidze]

What does this change?

Adds a small project site for app users at https://meshand.app/, published with GitHub Pages.

• site/index.html: one static page, no build step and no external requests apart from the GitHub API call for the latest release.
  • What MeshAnd is (radio → MeshAnd over Bluetooth → OsmAnd map), features, who it's for, what you need (Android 7+, a Meshtastic radio such as the T-Beam Supreme, free OsmAnd or Pro), the five install steps with the OsmAnd → Menu → Plugins allow step highlighted, "good to know", and links to the radio guide, changelog, releases, source, developer guide, Discussions, issues and the GPL-3.0 licence.
  • The text comes from README, CHANGELOG and docs/. Chat and Phone GPS have a "Next version" badge plus a note that the current download doesn't have them yet.
  • Brand: the Summit logo (inline SVG and favicon), pine #1F5A47 and ember #F07B4F, a hero phone illustration in the style of the social preview. It follows the system light/dark setting.
  • The download button asks the GitHub API for releases/latest and links straight to the APK ("Download MeshAnd 0.2.0", size and date). If that call fails, it opens the latest release page.
• Guides under /docs/ (MkDocs Material): site/build.sh renders docs/radio-setup.md, docs/development.md and CHANGELOG.md (as "What's new"), plus a short overview page (site/guides/index.md), with the pine/ember colours, a light/dark switch, search and a contents list. The .md files stay the only source; the build rewrites the one ../CHANGELOG.md link and runs --strict, so a broken link fails the deploy. mkdocs==1.6.1 and mkdocs-material==9.7.7 are pinned in site/requirements.txt. Material is in maintenance mode and doesn't work with MkDocs 2.0, so mkdocs stays below 2.0. The landing page's guide links now open these pages instead of GitHub.
• .github/workflows/pages.yml: installs the pinned packages, runs site/build.sh and deploys build/site with setup-python@v7, configure-pages@v6, upload-pages-artifact@v5 and deploy-pages@v5. It runs on pushes to main that touch site/**, docs/**, CHANGELOG.md or the workflow file, or by hand. It doesn't touch ci.yml or release.yml.
• README: a "Website" link in the top link row.
• AGENTS.md (Build & run): how the site is built, published and previewed, plus a reminder to remove the "Next version" badges when 0.3.0 is released.

Pages is already enabled (Source: GitHub Actions) with the custom domain meshand.app; its DNS records are on Cloudflare (DNS only), and GitHub is issuing the HTTPS certificate. The first deploy runs when this is merged. No release, tag or version change.

Type of change

• Bug fix
• New feature
• UI / design
• Docs only
• Build, CI or refactoring

How was it tested?

No app code changed, so the Gradle checks and phone test don't apply (CI runs them anyway).

• ./site/build.sh builds cleanly with --strict. Served build/site locally and checked the landing page and the guide pages in headless Chrome at 1280 px (light and dark) and in a 375 px phone viewport (dark): no horizontal scroll, the release lookup fills in "Download MeshAnd 0.2.0 · APK, 9.5 MB".
• The Pages workflow itself runs only on main, so it's first exercised after merge.

Screenshots

The hero uses the same illustration style as docs/images/social-preview.png. The names on the illustration (Nino, Ana, Luka, Giorgi) are made up.

Checklist

• Doesn't log channel keys, radio configuration or other secrets
• Doesn't make MeshAnd transmit anything new to the mesh (or this was agreed in a discussion first)
• User-visible changes are added to CHANGELOG.md under the next version (not an app change)
• README / docs / AGENTS.md updated if something they say is no longer true
• AI tools were used for this change: yes

🤖 Generated with Claude Code

[claude]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.