stitched-full-page-capture

1# Stitched Full-Page Capture
2 
3## Overview
4 
5Use settled viewport screenshots instead of trusting one-shot browser `fullPage` captures. This is especially important for Framer pages and other lazy/scroll-animated sites where the MP4 can look correct while the tall screenshot is mostly blank.
6 
7## Core Workflow
8 
91. Open the real page URL, not a marketplace thumbnail, cover image, remix page, or asset URL.
102. Warm the page by scrolling from top to bottom once so lazy media and reveal sections mount.
113. Return to the top.
124. Scroll downward in viewport-sized or slightly-overlapping steps.
135. Wait about 2 seconds after each scroll stop.
146. Capture the settled viewport.
157. Stitch the viewport captures vertically into one full-page image.
168. Cut section crops from that stitched image, not from the native browser `fullPage` screenshot.
179. Validate the stitched image against the representative still, MP4, and motion frames.
18 
19Reject a full-page candidate when it has blank/gray/white bands, very low visual content, missing lazy-loaded sections, an extremely narrow content column, or obvious disagreement with the scroll video.
20 
21## Script
22 
23For daily UI inspiration articles, use the helper script from this skill directory when available:
24 
25```bash
26node <skills-root>/stitched-full-page-capture/scripts/stitch_full_page_capture.mjs \
27  --manifest articles/YYYY-MM-DD-ui-inspiration-capture/manifest.json
28```
29 
30The script:
31 
32- reads `items[].pageUrl`, `fullPageImage`, and `sectionImages`;
33…