Presentation Systems

Why This Layer Exists

Presentation products are not normal landing pages and not normal app dashboards. They need structure, chaptering, evidence, stagecraft, and just enough motion to feel directed.

This composition layer translates that presentation logic into Webspire patterns and snippets.

First-Class Families

These concepts belong as actual Webspire building blocks:

• Presentation Hero → presentation-led entry frames, deck mosaics, stage previews
• Story Arc → hook / problem / solution / proof / ask sequencing
• Widget Showcase → grids of metrics, embeds, summaries, charts, and narrative cards
• Collaboration → presence, comments, multiplayer review, shared narrative editing
• Deck Structure → outline rails, chapter maps, active stage views
• Canvas Stage → freeform-but-disciplined compositional surfaces
• Proof Wall → metrics, quotes, logos, screenshots in a layered evidence system
• Use-Case Matrix → role-based entry points for founders, sales, marketing, product, educators

Already In Webspire

Presentation logic also maps onto families that already exist in the system.

• Hero and entry framing → hero, presentation-hero, page-header
• Narrative sequencing → story-arc, steps, timeline, case-study
• Evidence and comparison → proof-wall, comparison, stats, testimonials, trust-strip
• Structured exploration → deck-structure, tabs, related-articles, blog-details
• Work and output proof → portfolio, gallery, use-case-matrix, services
• Interactive stage surfaces → canvas-stage, widget-showcase, code-preview, data-table

Existing Anchors

These existing Webspire patterns already participate in the same composition logic:

• Entry and framing → hero/base, page-header/base, presentation-hero/deck-mosaic
• Narrative flow → story-arc/framework-strip, steps/how-it-works, case-study/meta-header
• Evidence and trust → proof-wall/evidence-cascade, comparison/base, stats/base, testimonials/featured, trust-strip/base
• Exploration and chaptering → deck-structure/outline-plus-stage, tabs/underline, related-articles/base
• Portfolio and output proof → portfolio/case-study, gallery/masonry, services/reveal-list
• Stage-like surfaces → canvas-stage/freeform-board, widget-showcase/adaptive-grid, code-preview/split, data-table/with-filter

Ideas That Map Better to Existing Families

Not every idea needs its own permanent family. Some fit better as variants or semantic directions inside existing ones.

• Template Gallery → mostly extends existing gallery, portfolio, and blog preview logic
• Brand System → belongs near brand-kit and token-driven configuration patterns
• Presentation Export → can often live inside cta, announcement-bar, or utility panels
• Presentation FAQ → should usually extend faq rather than split into a new family
• Focus Mode → mostly a snippet layer or a strong variant on stage-oriented patterns
• Widget Slot → more a compositional principle than a whole family on its own
• Chapter Transition → usually a stage/divider pattern plus supporting snippets
• Deck Page / Web Export → a template/page-level concern that can reuse the families above

Snippet Layer

These snippets make the page feel closer to a presentation framework without forcing a slide metaphor everywhere.

• Chapter Snap → softer chapter rhythm for long pages
• Spotlight Reveal → focus one frame while the rest falls back
• Card Fan Stack → deck or preview groups feel alive on hover
• Story Progress Line → visible chapter progress in narrative flows
• Widget Expand → active widgets gain just enough emphasis
• Presentation Glass → cleaner translucent stage surfaces

These existing snippets already reinforce that behavior:

• scroll/chapter-snap
• masks/spotlight-reveal
• interactions/card-fan-stack
• decorative/story-progress-line
• interactions/widget-expand
• surfaces/presentation-glass

Core Composition Set

If a presentation-first composition belongs in Webspire, these are the clearest anchor patterns:

1. Deck Mosaic Hero
2. Framework Strip
3. Adaptive Widget Grid
4. Outline Plus Stage
5. Evidence Cascade

These snippets reinforce the same composition logic:

• Chapter Snap
• Spotlight Reveal
• Card Fan Stack
• Widget Expand

Semantics

These families are strongest for:

• saas, agency, consulting, education, personal
• tones like modern, premium, editorial, technical
• goals like provide_overview, tell_story, demonstrate_value, highlight_expertise, reduce_friction

The point is not “make the website look like slides”. The point is to make dense information feel directed, staged, and easy to follow.