Showcase

Use the showcase after the starter ladder. This is where Tessera should start to feel like product infrastructure, not just a control catalog.

Flagship Evaluation Order

1. GitConsole
2. OpsWatch
3. DataWorkbench

What the showcase is for

The showcase answers one question:

does the same public path still hold when the UI stops being simple?

Use the flagship apps to judge density, composition, workflow fit, and the theming model. Use the supporting demos only after the flagship answer is clear.

Quick reference

Example	Best for evaluating	Command
GitConsole	command-heavy workflow surfaces	dotnet run --project examples/GitConsole/GitConsole.csproj
OpsWatch	dashboard composition and operator density	dotnet run --project examples/OpsWatch/OpsWatch.csproj
DataWorkbench	the richest workbench-style shell	dotnet run --project examples/DataWorkbench/DataWorkbench.csproj

GitConsole

Best when you want to judge command-heavy workflow surfaces.

• patch deck and diff review
• worktree and commit flow
• denser navigation and action rails

bash.sh

dotnet run --project examples/GitConsole/GitConsole.csproj

OpsWatch

Best when you want to judge dashboard composition and operator-facing density.

• telemetry cards and charts
• alert feed and pressure indicators
• operator actions inside one surface

bash.sh

dotnet run --project examples/OpsWatch/OpsWatch.csproj

DataWorkbench

Best when you want the richest workbench-style evaluation.

• multi-pane investigation layout
• tabs, result grids, and inspector flows
• pointer-ready runtime configuration and denser state orchestration

bash.sh

dotnet run --project examples/DataWorkbench/DataWorkbench.csproj

Evaluation checklist

By the end of the flagship pass, you should be able to answer:

• does the same TesseraApp + Build(...) model still feel coherent?
• do controls, layouts, and themes still look like one framework?
• can you imagine mapping your own domain onto these surfaces?
• does the framework still feel explicit rather than magical?

Supporting Demos

Use these once the flagship path is already clear:

• DownloadCenter: grouped jobs and transfer-heavy surfaces
  • dotnet run --project examples/DownloadCenter/DownloadCenter.csproj
• IncidentDesk: triage and queue-oriented workflows
  • dotnet run --project examples/IncidentDesk/IncidentDesk.csproj
• MusicDeck: media-oriented dashboard styling and playback flows
  • dotnet run --project examples/MusicDeck/MusicDeck.csproj
• TransitBoard: dense board-style presentation and schedule surfaces
  • dotnet run --project examples/TransitBoard/TransitBoard.csproj

Where to go next

• layout and screen composition: layout-and-screen-composition
• controls by problem domain: controls-overview
• theme and overrides: theme-system
• exact type names: API Reference