V1 Web PWA · Surface walkthrough

Studio · Yemaya · Community

A per-surface walkthrough of the V1 Web PWA studio surface: layout, states, interactions, data, and cross-references.

walked
8sections2 minread
Markdown source
On this page

Context. surface studio · domain yemaya · route /studio/yemaya/community · auth signed-in + studio entitlement · source apps/oshun/web/src/app/studio/yemaya/community/page.tsx

Last walked. 2026-05-29 automated runtime walk (Playwright headless) — render, /v1 data (2xx), console/page-errors, expected content, screenshot verified; live screen-reader, touch, offline, and telemetry-delivery checks pending a manual AT pass. Evidence: WALKTHROUGH/results/runtime-sweep-2026-05-29.md; body re-derived 2026-06-03 from current source (lane-console architecture)

Purpose#

Aggregator workspace that composes the community-adjacent Yemaya lanes — Community Features, Team Collaboration, and Enterprise Analytics — under a single Yemaya Community capability summary. It owns no /v1 fetch of its own; each embedded lane is its own admin-scoped console with independent data and states.

Entry points#

  • Breadcrumb chain on this page: Studio › Yemaya Community Features › Community.
  • Reachable from sibling Yemaya routes that quick-action to /studio/yemaya/community.
  • Direct URL / bookmark (signed-in + studio entitlement).

Layout regions#

page.tsx renders ShellLayout active="studio" and:

  • Breadcrumbs panel: Studio › Yemaya Community Features › Community.
  • Workspace panel (StudioYemayaCommunityWorkspace, data-yemaya-community-workspace):
    • <h1> (WorkspaceHeading) "Yemaya Community Workspace".
    • Summary paragraph (data-yemaya-community-summary).
    • Capability Summary (data-yemaya-community-capability-summary, <h2>): four informational cards — Community Engagement Orchestration, Cross-Team Collaboration, Community Observability and Insights, Security and Parity.
    • Community Features Lane (data-yemaya-community-features-lane, <h2>): embedded StudioYemayaCommunityFeaturesWorkspace.
    • Team Collaboration Lane (data-yemaya-community-collaboration-lane, <h2>): embedded StudioYemayaTeamCollaborationWorkspace.
    • Enterprise Analytics Lane (data-yemaya-community-analytics-lane, <h2>): embedded StudioYemayaEnterpriseAnalyticsWorkspace.
  • Route Map panel (data-yemaya-community-route-map): <h2> "Route Map" + six entries from STUDIO_YEMAYA_COMMUNITY_ROUTE_MAP.
  • Quick-action panel: four quickAction links.

States#

The page renders the capability cards + three embedded lanes unconditionally; each lane owns its own Loading / Unauthorized (admin-scope 401/403) / Error / Ready / Result states.

  • Community Features Lane — states owned by /studio/yemaya/community-features.
  • Team Collaboration Lane — states owned by /studio/yemaya/team-collaboration.
  • Enterprise Analytics Lane — states owned by /studio/yemaya/enterprise-analytics.

Interactions#

Capability cards#

data-yemaya-community-capability — four informational <article> cards (Community Engagement Orchestration, Cross-Team Collaboration, Community Observability and Insights, Security and Parity); not interactive.

Embedded lanes#

  • Community Features Lane — see /studio/yemaya/community-features.
  • Team Collaboration Lane — see studio-yemaya-team-collaboration.md.
  • Enterprise Analytics Lane — see /studio/yemaya/enterprise-analytics.

Route map#

data-yemaya-community-route-map — six non-interactive entries:

  • /studio/yemaya/community — primary workspace
  • /studio/yemaya/community/hubs/[hubId]
  • /studio/yemaya/community/collaboration/[sessionId]
  • /studio/yemaya/community/analytics/[dashboardId]
  • /studio/yemaya/community/parity/[parityId]
  • /studio/yemaya/community/governance/[policyId]

Quick actions#

  • "Open Yemaya Community Features workspace" → /studio/yemaya/community-features.
  • "Open Yemaya Team Collaboration workspace" → /studio/yemaya/team-collaboration.
  • "Open Yemaya Enterprise Analytics workspace" → /studio/yemaya/enterprise-analytics.
  • "Back to Studio workspace index" → /studio.

Data & contracts#

  • Reads: none at this aggregator boundary; each embedded lane issues its own GET /v1/admin/yemaya/... on mount.
  • Writes: none at this boundary; each embedded lane owns its own POST verb.
  • Realtime: none.
  • Caching: aggregator owns no fetch; embedded lanes fetch on mount with cache: 'no-store'.
  • Auth/role check: each embedded lane is admin-scoped and fail-closed; signed-in + studio entitlement enforced by the proxy/middleware.

Cross-references#

  • Studio overview: studio-overview.md
  • Workspace source: apps/oshun/web/src/components/studio/StudioYemayaCommunityWorkspace.tsx
  • Route map source: apps/oshun/web/src/components/studio/StudioYemayaCommunityRouteMap.ts
  • Embedded lanes: studio-yemaya-team-collaboration.md, /studio/yemaya/community-features, /studio/yemaya/enterprise-analytics
  • Feature spec: V1/features.md

Open questions / known gaps#

  • The route-map dynamic children (hubs / collaboration / analytics / parity / governance) are sitemap-only — confirm whether any are backed by page.tsx files yet.