The volute.dev site explains the ideas well but shows almost none of the product. Before inviting people in, a visitor should be able to see what hosting minds looks like — the dashboard, chat, the timeline, a mind's pages — and get a feel for a real system that's been alive for a while, not an empty fresh install.
Scope for a first pass:
- Screenshots through the site: dashboard, mind chat, history timeline, a mind's homepage/pages, settings/bridges — captured from a populated system, light and dark.
- "A real system" section: a guided look at a lived-in install — minds with distinct profiles, an active #system commons, journal/dream artifacts, a visible sleep/wake rhythm. Could be curated captures from a real host (with its minds' consent) or the existing fixture approach — the website already vendors the timeline components with fixtures modeled on real rhythms (
website/src/components/timeline), which this can extend.
- Keep captures reproducible: note where each screenshot comes from (the integration-test rig in
docs/integration-testing.md can stage a populated system) so they can be re-taken as the UI evolves.
Related but not required: #145 (public read-only view) would eventually let the site link to a live system instead of pictures of one.
The volute.dev site explains the ideas well but shows almost none of the product. Before inviting people in, a visitor should be able to see what hosting minds looks like — the dashboard, chat, the timeline, a mind's pages — and get a feel for a real system that's been alive for a while, not an empty fresh install.
Scope for a first pass:
website/src/components/timeline), which this can extend.docs/integration-testing.mdcan stage a populated system) so they can be re-taken as the UI evolves.Related but not required: #145 (public read-only view) would eventually let the site link to a live system instead of pictures of one.