FS26
Ctrl K
Phase 20 · Lesson 03

App Shell Navigation and Workspace Context

≈ 2 min core reading · 244 source/companion words
Learning contract

What you should be able to do after this

  • Explain App Shell Navigation and Workspace Context without relying on framework buzzwords.
  • Connect the lesson to the phase outcome: Build a production application shell and reusable UI states instead of isolated demo components.
  • Reproduce the relevant behavior and verify it with evidence.
  • Diagnose at least one representative failure instead of guessing.
Figure 20.3 — TaskFlow boundary map
route/layout
server data boundary
page composition
client interaction islands
responsive/accessibility states
This lesson belongs to Phase 20. Keep the full request/data path visible even when today's code changes only one box.
Instructor workflow: predict first → implement the smallest slice → run it → inspect evidence → break one assumption → diagnose → explain it back. Do not copy the whole code block before understanding the first failing boundary.

App Shell, Navigation & Workspace Context Create persistent orientation with semantic landmarks and accessible navigation

Phase 20 - Production Application UI Volume 06 - Professional Frontend

Architecture milestone

Sidebar/mobile nav

v

Header/workspace context

v

Main route content

Phase 20 turns the secure full-stack foundation into a coherent, accessible application interface without moving business authority into the browser.

Application shell: persistent orientation The shell has three jobs: primary navigation, current workspace/account context, and a predictable place for route content. It should not become a giant stateful component that owns every feature.

Figure 1 - Shell layout

Sidebar / mobile navigation

v

Header / workspace + account

v

Main content region

v

Route page

Persistent navigation surrounds changing route content.

Semantic landmarks • `` for the desktop sidebar where appropriate.

• `` for route links.

• `` for account/workspace context.

• `` for route content.

• Skip link for keyboard users to bypass repeated navigation.

Navigation target size TaskFlow gives primary navigation and buttons at least a comfortable 44px interaction height, exceeding WCAG 2.2 minimum target-size requirements and improving touch usability.

Shell decision Reason

Sticky desktop sidebar Navigation stays available during long pages

Contained main width Very wide screens do not produce unreadably stretched content

Responsive collapse Mobile does not inherit a 260px permanent sidebar

Text labels Icons alone are ambiguous and harder to learn

Visible focus Keyboard users can track position

Sticky UI can hide focus

WCAG 2.2 adds Focus Not Obscured. Test keyboard navigation around sticky headers/footers so the focused element remains visible.

Executable lesson studio · monorepo

Now turn the explanation into engineering skill.

App Shell Navigation and Workspace Context matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.

By the end, you should be able to

  • Explain App Shell Navigation and Workspace Context in terms of concrete inputs, ownership, outputs, and evidence.
  • Implement or reproduce the smallest TaskFlow slice that demonstrates this monorepo concept.
  • Diagnose one representative monorepo failure using observable evidence instead of trial-and-error.
Figure 20.3B — Mental model
repository root
workspace package
dependency graph
task runner
artifact
Read left-to-right while implementing. When debugging, walk right-to-left until the first observed fact differs from your prediction.
Code-along sequence

One coherent change at a time

  1. 01

    Restate the goal of “App Shell Navigation and Workspace Context” as one observable behavior. Write the success signal before touching code.

  2. 02

    Trace the boundary map: repository root → workspace package → dependency graph → task runner → artifact. Mark the one boundary this lesson changes.

  3. 03

    Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.

  4. 04

    Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.

  5. 05

    Connect the slice to TaskFlow’s phase artifact: TaskFlow responsive shell with navigation, workspace context, task screens, loading/empty/error states, and accessible interactions.. Verify behavior from the outside as a user or API client would.

  6. 06

    Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.

  7. 07

    Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.

txtBoundary trace
Input -> owner -> transformation -> observable output -> failure evidence

Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.

Verification

Prove the happy path

  1. Run the narrowest relevant command or request and require a clean exit/status.
  2. Inspect the boundary-specific evidence: terminal output, Network panel, database row/query plan, test report, container health, or deployment logs.
  3. Repeat the behavior once after the change so a one-off cached or stale result cannot masquerade as success.
Break it on purpose

Build debugging memory

  1. Clickable divs without keyboard semantics
  2. Change one assumption in the monorepo example—identity, input, configuration, ordering, connectivity, or state—and predict the exact symptom before running it.
SymptomInvestigation path
Expected result does not appear

Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.

A shortcut appears to fix it

Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.

Closed-reference challenge

Can you transfer the idea?

Without copying the final source, create a second small scenario that applies “App Shell Navigation and Workspace Context” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.

Explain-back

Answer these without reopening the solution

  1. What problem does App Shell Navigation and Workspace Context solve in TaskFlow, and what would be observably wrong without it?
  2. Which part of the monorepo boundary owns the decision, and which neighboring layer must not own it?
  3. What evidence proves the happy path instead of merely suggesting it worked?
  4. Name one realistic failure or abuse case and the first place you would inspect.
  5. If requirements doubled tomorrow, which part of this design should stay stable and which part is allowed to change?
Lesson studio

Turn the reading into skill

01

Do it

Build workspace/board/task navigation with active state derived from routing rather than duplicated local state.

Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.
02

Break it safely

Clickable divs without keyboard semantics

Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.
03

Explain it back

Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?

If your explanation is vague, repeat the boundary trace before moving on.
Exit ticket

Before marking complete

Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.

← Protected Route Groups and App LayoutTask Table and Domain Presentation →