Meta: revamp agmsg.cc — coordination thread (raise your hand here)

[fujibee]

What this is

A coordination thread for giving https://agmsg.cc/ an overhaul. There is growing momentum to make the site a proper home for the project, so this issue is the place to raise your hand, propose a workstream, and coordinate — not a fixed spec. If you want to help, comment below.

Current state

agmsg.cc is already live: GitHub Pages served from /docs on main (custom domain agmsg.cc, set up in #10). Today it is a basic landing page (docs/index.html) plus the raw markdown docs (agent-types, teams, actas, plugins, opencode, design, the adr/ and spec/ sets, etc.) and some assets under docs/logos, a demo gif, and a screenshot.

It works, but it has not kept pace with the project. The goal is to make the landing page and docs match where agmsg is now.

Possible workstreams (a starting menu, not a mandate)

Pick one, propose your own, or split these further:

• Landing page / visual refresh — hero, value proposition, demo, above-the-fold quick start.
• Docs information architecture — navigation and structure across the /docs markdown set so pages are discoverable, not just a flat folder.
• Content — a clean quick start, an agent-type support matrix, examples/recipes, an FAQ.
• Site tooling — open question: keep hand-rolled HTML, or adopt a lightweight static-site generator? Trade-offs welcome.
• Branding / assets — logos already exist under docs/logos; consistency pass across the site and the repo.

How to participate

1. Comment to raise your hand and say which workstream you want to take (or propose a new one).
2. Coordinate scope here in the thread to avoid overlap.
3. Spin out focused issues / PRs per workstream and link them back to this one.

Keep it lightweight — this thread is the hub. All changes ship through /docs on main (that is what agmsg.cc serves), so PRs are previewable as normal.

Refs: #10 (original site setup).