Generic presentation system
Compose a deck with the same building blocks as the site.
The page controls layout and movement. Components focus only on content.
Presentation content stays reusable when it does not own the page layout.
Place the component in any grid cell and let the page define its position.
Make contrasting ideas easy to scan.
Before
Each deck invents its visual language.
- Repeated markup
- Inconsistent hierarchy
- Harder visual reviews
With the library
The page composes proven content patterns.
- Shared components
- Consistent typography
- Debuggable grid
Explain a sequence without hiding its structure.
- 01FrameDefine the problem and the audience.
- 02ComposePlace content inside the page grid.
- 03PresentUse vertical and horizontal motion.
- 04RefineReview every slide with the debugger.
Give important numbers room to speak.
Slide canvas
A familiar presentation aspect ratio.
Grid columns
The desktop grid from the base project.
Source of layout
The page remains in control.
A strong presentation system gives ideas a rhythm before it gives them decoration.
Show how the system is layered.
- 01PageOwns grid, parallax, spacing, and theme.
- 02SlideProvides the 16:9 content canvas.
- 03ContentReusable components express the story.
- 04TokensTypography scales with the slide width.
Organize evidence with deliberate emphasis.
- DefaultA regular item for the main explanation.
- AccentA stronger item for the central conclusion.
- MutedA quieter item for supporting context.
Make feedback loops explicit.
- 01ObserveCollect evidence.
- 02DecideChoose the next move.
- 03BuildCreate the smallest proof.
- 04LearnFeed the result back.
Learning starts the next cycle
Place milestones on a shared horizon.
- NowFoundationShared visual vocabulary.
- NextFirst deckContent meets the system.
- LaterLibraryPatterns emerge from use.
- FutureEvolutionThe base grows with evidence.
Introduce the people behind the work.
Portraits are optional. Initials provide a useful fallback.
- Alex MorganNarrativeTurns evidence into a clear story.
- Sam RiveraDesignCreates hierarchy and visual rhythm.
- Taylor KimEngineeringKeeps the system reusable and robust.