Open each part when you need it. The note’s wording and sequence are preserved.
01The decision
Two Work cards use saved October 16 homepage packages so their text and layouts can reflow inside the selected viewport. They are dated copies, not live sessions. The remaining cards use screenshots, and the private ATLAS card keeps its private-workspace notice.
The embedded pages are read-only and removed from the interaction path. Scripts, form actions, outside connections, storage and nested frames are blocked. The ordinary project-story link remains the way to open the named destination.
02Why containment belongs to the design
An interactive-looking page can invite a click even when a preview should be passive. Hiding the frames from the accessibilityMaking information and controls usable by people with different abilities and ways of interacting.Open the source tree, preventing pointer and keyboard interaction, and keeping a screenshot fallback make the boundary part of the experience rather than an implementation footnote.
The result demonstrates saved responsive behavior. It does not prove that a live form works, that an account is available or that production traffic has no outside requests. Those are separate checks in the environment that owns them.
03Make passive previews visibly and technically passive.
Practical checklist
- Package an approved saved source instead of framing a live application.
- Remove actions and connections that can create production state.
- Provide a stable fallback before or when the saved page cannot renderTurned into the page or experience a person can actually see and use..
- Send visitors through a clear project link rather than interaction inside the preview.
04Reflow without a live session
Concrete example
TAGD and Storyline use saved anonymous homepage packages in empty-sandbox iframes. Their layouts reflow as the selected viewport changes, while account state, forms, source links and product requests remain unavailable.