Internal Direction

Content

One trainer content workspace. The left sidebar collapses to a single `Content` entry, and the page itself becomes a lightweight router into Programs, Nutrition Plans, Meal Library, and Collections.

Specimen

This direction intentionally avoids a “dashboard of dashboards.” The page is mostly the selected workspace, with only a thin layer of guidance above it.

Trainer Content — Workspace Router Direction
Home / Content
96 credits

Content

Switch between every trainer content workflow in one place, then stay inside the selected tool until the work is done.

Create Program
Programs Draft, publish, template, sell
12
Nutrition Plans Build and manage client plans
8
Meal Library Reusable meals and custom foods
31
Collections Bundle programs into offers
4
2 program drafts need review
1 nutrition plan is incomplete
1 collection is empty
Continue: Shred 90

Programs

Keep the existing list and creation model intact. The only major change is that it now lives inside `Content` instead of its own left-nav destination.

Templates
Collections
Nutrition Plans
Create Program
All (12)
Draft (4)
Published (7)
Archived (1)
Templates

Shred 90

12 weeks · Intermediate
Published
4.9 rating $49

Home HIIT

6 weeks · Intermediate
Draft
No reviews yet Free

Strength Foundations

8 weeks · Beginner
Published
4.8 rating $29

Pattern Rules

One Dominant Workspace

The selected domain should own most of the screen. Guidance stays slim and never competes with the working area.

Guidance, Not Dashboard Theater

Use alert strips, continuation chips, and smart defaults instead of multiple hero cards, KPI rows, and stacked panels.

Preserve Existing Behaviors

Search, status tabs, empty states, template flows, and creation actions should feel familiar to current MTC trainers.

Route Notes

Primary Route

/content becomes the single left-nav destination for trainer content.

Mode Routing

Programs, Nutrition Plans, Meal Library, and Collections remain first-class page modes inside the same shell.

Redirect Behavior

Legacy routes should resolve into the matching content mode and preserve deep-link utility where possible.