Product Flows

Web Dashboard

What the current Next.js dashboard is responsible for and how to think about it.

The dashboard is the operator-oriented web surface for Logga. It is built in Next.js and lives in logga-frontend.

Current Responsibilities

The dashboard is responsible for:

  • login and access gating
  • workspace-aware navigation
  • project and channel browsing
  • project-scoped tracked-user activity review
  • event and session review
  • report management
  • settings and operational controls
  • documentation rendering at /docs

Important Implementation Areas

Path Role
app/login/page.tsx User login entry
app/access/page.tsx Optional first-level access password gate
app/app/[workspaceId]/* Authenticated workspace routes
components/dashboard/* Dashboard layout and page-specific UI
lib/api.ts Backend request types and helpers

API Contract Expectations

The dashboard assumes:

  • backend auth routes return user identity plus membership context
  • workspace summaries include counts, recent sessions, and recent notifications
  • paginated list endpoints return { data, nextCursor }
  • environment selection matters and should not be flattened away
  • project users are derived from stable event identity, not a separate product-user table

Design Direction

The existing web surface is not trying to be a generic admin panel. It leans into:

  • product personality
  • a more editorial, designed public landing experience
  • reusable textured UI components
  • a clean but branded internal shell

Any docs or admin work added to the web surface should respect that instead of reverting to plain boilerplate.

Documentation Route

This workspace now includes a docs viewer inside the frontend so the shared Markdown source is visible at /docs.

The intent is:

  • Markdown is the source of truth
  • navigation is explicit through docs/navigation.json
  • the Next.js route is just a renderer and browser
  • the same content can also be exported as standalone HTML

When To Update Dashboard Docs

Update this page when:

  • major route structure changes
  • auth flow changes
  • dashboard ownership changes
  • docs rendering behavior changes
  • project-level product analytics surfaces change