You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add media split layout back to supported docs (#8)
Treat media split as a supported layout again so the package guidance and
component surface stay aligned, and add coverage for its fallback
normalization behavior.
Copy file name to clipboardExpand all lines: resources/boost/skills/slidewire-development/SKILL.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,6 +84,7 @@ Without those `@source` entries, package components may render with missing styl
84
84
-`<x-slidewire::panel>`: reusable modern surface for grouped content, supporting variants like `default`, `elevated`, `outlined`, and `glass`.
85
85
-`<x-slidewire::title-slide>`: opinionated opening slide for titles, subtitles, overlines, and presenter metadata.
86
86
-`<x-slidewire::two-column-slide>`: responsive split layout for explanation-plus-supporting-content slides.
87
+
-`<x-slidewire::media-split-slide>`: media-first split layout with left/right positioning, ratio controls, and optional framed or panel-style media treatment.
87
88
-`<x-slidewire::timeline-slide>` and `<x-slidewire::timeline-item>`: structured milestone and roadmap layouts.
88
89
-`<x-slidewire::steps-slide>` and `<x-slidewire::step-item>`: process and rollout layouts with optional auto-numbering.
89
90
-`<x-slidewire::agenda-slide>` and `<x-slidewire::agenda-item>`: section overview and agenda layouts.
@@ -98,6 +99,7 @@ Without those `@source` entries, package components may render with missing styl
98
99
- Use `panel` when content needs a polished surface without rebuilding the same rounded, theme-aware wrapper.
99
100
- Use `title-slide` for opening slides, chapter intros, and title cards.
100
101
- Use `two-column-slide` for explanatory layouts that pair copy with supporting visuals or code.
102
+
- Use `media-split-slide` when the visual side should lead the composition and you want built-in media framing controls.
101
103
- Use `timeline-slide` and `agenda-slide` for milestones, sections, and chapter overviews that need more structure than bullets.
102
104
- Use `steps-slide` for process, rollout, or tutorial content.
103
105
- Use `text` for semantic headings, paragraphs, inline text, vertical labels, or reusable animation-ready copy blocks.
@@ -116,6 +118,7 @@ Recommendations:
116
118
- Prefer `panel` as the base surface primitive for grouped text, code, media, or mixed content.
117
119
- Prefer `title-slide` over ad hoc hero markup for opening slides or chapter separators.
118
120
- Prefer `two-column-slide` for both general split layouts and media-plus-content layouts; frame the visual side with `panel` when needed.
121
+
- Prefer `media-split-slide` when the deck benefits from a more opinionated media-led split with `plain`, `framed`, or `panel` media presentation.
119
122
- Prefer `timeline-slide`, `steps-slide`, and `agenda-slide` over plain lists when the sequence or hierarchy matters to the talk.
120
123
- Still allow local customization through slots and `class` passthrough when a deck needs light visual tailoring.
0 commit comments