MSlide³ extends fragments beyond individual elements.
Entire layouts can evolve progressively inside a Content State.
Rather than revealing isolated components, successive layout regions become available while preserving the current state.
<!-- Initial layout -->
<div class="notification">
Layout 1
</div>
<!-- Second layout stage -->
<div class="notification fragment">
Layout 2
</div>
<!-- Third layout stage -->
<div class="notification fragment">
Layout 3
</div>
<!-- Final layout stage -->
<div class="notification fragment">
Layout 4
</div>
Fragments are applied to complete layout regions rather than individual text elements.
<!-- Layout stage 1 -->
<div class="notification">
Initial layout
</div>
<!-- Layout stage 2 -->
<div class="notification fragment">
Additional layout region
</div>
<!-- Layout stage 3 -->
<div class="notification fragment">
Complementary content
</div>
<!-- Final layout stage -->
<div class="notification fragment">
Final layout state
</div>
Fragments may control complete content regions.
<!-- Initial region -->
<div class="block">
Main content
</div>
<!-- Secondary region revealed later -->
<div class="block fragment">
Additional content region
</div>
This allows layouts to evolve progressively.
Fragments can reveal alternative views within the same layout.
<!-- Primary view -->
<div class="tab-content is-active">
View 1
</div>
<!-- Secondary view -->
<div class="tab-content">
View 2
</div>
MSlide² uses fragments to create progressive state layers within a slide.
MSlide³ expands this approach by allowing complete layouts and content regions to evolve progressively inside a Content State.
Both frameworks preserve continuity, but MSlide³ applies fragment progression at a larger scale.