HUB-SETTINGS-HOSTED-UX-PASS.md markdown
38 lines 2.9 KB
Raw
sha256:65ccb454656ea5acdea0a10e559b78bcde1eb6ff753ecc2911bc99d1c3d7cadd feat(calendar): enforce agent context tiers in retrieval AP… Human minor ⚠ breaking 1 day ago

Hub Settings + “How to use” — hosted-first UX pass (handoff)

Goal: Hosted users see simple, non-intimidating copy first. Anything that only applies to self-hosted (paths, YAML, env vars, ffmpeg, Git on disk, …) or deep technical detail is folded behind clear affordances: Self-hosted (with a consistent icon/label), How?, Technical details, or <details> blocks. Cross-path concepts (JWT, MCP) can use How? / shared “technical” disclosure when both audiences need the same footnote.

Checklist parent: HUB-WIZARD-HOSTED-STORY.md Phase 5.

Precedents shipped on branch feature/hub-wizard-hosted-story:

  • Settings → Integrations lede: inline How? <details> for Hub API (web/hub/index.html, web/hub/hub.css — search settings-integ-how-inline).
  • How to use → Knowledge & agentsHosted MCP: secrets vs “prime” bootstrap: layman-first paragraphs, then <details class="how-to-details"> for URIs, env names, MCP readResource / prompts/list, and knowtation doctor (web/hub/index.html). Phase 5 extends this pattern to all How to use tabs and Settings blocks (track in this file + AI-ASSISTED-SETUP.md).
  • Self-hosted label in UI — use plain-English <summary> lines (e.g. Self-hosted setup — …); no separate icon asset required. Hosted-first lead: how-to-hosted-lead in hub.css.

Session prompt: Start from the quick reminder below or maintain a copy under development/ (gitignored) if you use long Cursor handoffs.

Scope: web/hub/index.html (Settings modals), How to use panels in the same file, and any linked copy in web/hub/hub.js that injects settings strings.

Non-goals: Do not remove documented behavior from the repo; relocate and label, do not delete safety text.


Copy-paste prompt (short)

Quick reminder:

Hosted-first Settings + How to use: layman lead; technical + self-hosted under <details>.
Precedent: Knowledge & agents → Hosted MCP prime section in web/hub/index.html.
Check off tabs in this file’s checklist as you go.

Checklist (execute in the session above)

  • [x] Backup — Hosted-first intro + Status context; self-hosted hub_roles / heavy proposal explainer → Technical details / details (web/hub/index.html); Danger zone & Configure backup still contain operator-level detail (relocated where noted).
  • [x] Integrations — Capture/Import lede; tiles plain-English; ports/API/ffmpeg → details blocks.
  • [x] How to useSetup: hosted callout + self-hosted in <details>; Getting started, Knowledge & agents, Media, Memory consolidation (privacy), Token savings updated for layman + technical fold-outs.
  • [x] Icons — Summaries use text “Self-hosted”; no new SVG (documented here).
File History 2 commits
sha256:65ccb454656ea5acdea0a10e559b78bcde1eb6ff753ecc2911bc99d1c3d7cadd feat(calendar): enforce agent context tiers in retrieval AP… Human minor 1 day ago
sha256:9103f98c89257ed2b01c237cea895dabb3e85ea337dccb1161c175e4422355b6 docs: accept Calendar Events v0 spec with Phase 0 security … Human 1 day ago