# Product assets Store product-facing screenshots, demo recordings, and release artwork here. Use stable, descriptive filenames and keep source captures or editing files outside the plugin package when they are not needed by the documentation. ## Branding The current Omagen icon and wordmark are stored in `branding/`. They are the project-provided source assets for the README and future marketplace artwork. Before the stable release, confirm the project has permission to redistribute them and add a transparent/light-background variant if the current dark icon background is not suitable for every listing surface. ## Social preview The current v2 social-preview candidate is `social/omagen-social-preview-v2.png`. It is a 16:9 GitHub/Open Graph cover with a restrained image-to-palette visual, the supplied Omagen identity, and minimal copy that remains legible at thumbnail size. Keep this product-source artwork for GitHub and other link-preview surfaces. For the marketplace listing, the selected v2 preview is the walkthrough thumbnail below: it shows the product in use at a readable 16:9 size without duplicating the social-preview artwork. The current candidate copy is at the repository root as `preview.png`, sourced byte-for-byte from `social/omagen-walkthrough-thumbnail-v2.png`. Do not change that image after the stable commit is submitted for marketplace verification. The v2 YouTube walkthrough thumbnail is `social/omagen-walkthrough-thumbnail-v2.png`. It is a 1920×1080 product thumbnail linked from the canonical product README to the complete walkthrough video. Keep the thumbnail and video URL together when the product README is promoted to `main`. ## Hero demo The current v2 hero workflow recording is `demos/omagen-demo-v2.gif`. It preserves the full 51.9-second capture at 30 fps and 960×540, with audio removed for silent README playback. Keep the original MP4 as the source of truth and do not speed up the workflow merely to make the GIF shorter. Because this full-fidelity GIF is approximately 19 MB, it is intentionally kept as a product asset for now. After the stable release, a GitHub Release asset can become the canonical hosted copy if the repository would benefit from a smaller clone and checkout footprint. The [asset generation checklist](../ASSET-CHECKLIST.md) defines the filenames, capture goals, dimensions, and provenance required before the stable release. The [provenance ledger](PROVENANCE.md) records the source and release status of the current branding, screenshots, recordings, and example pairs. Before marketplace submission or any later stable asset update, every referenced asset must be present in the exact commit, have reviewable license/provenance, and stay within the marketplace preview limits when used as a listing preview. ## Setup walkthrough screenshots The curated v2 setup walkthrough is in [`screenshots/setup-v2/`](screenshots/setup-v2/). It was captured on workspace 5 from a reversible live session using one source image, then restored to the original desktop before the capture was accepted. The sequence covers image selection, workflow choice, palette generation, Balanced selection, Look & Feel, Glass Blur, Advanced, Demo, final review, and restoration. The public copies are resized to 1600×1000 for documentation and redact the local home-directory path visible in the file chooser. The original captures remain outside the product asset tree under the ignored UI-test workspace. These screenshots document the product flow; they are not evidence of a stable release or a marketplace security certification. ## Bar examples The [`bar-examples/`](screenshots/bar-examples/) gallery shows several product layouts for the optional full-bar experience: compact and wide variants, centered and left placements, and a minimal state. The full bar remains an explicit opt-in package; these images are examples of its visual range, not a replacement for the native Omarchy bar in the default installation path. ## Example pairs The generated v2 example pairs live in the repository's [`assets/examples/v2/`](../../../assets/examples/v2/) directory and are presented in the [product example gallery](../examples/README.md). Each theme has a source background and its generated `preview.png` represented as a documentation-friendly WebP asset. The older pairs remain available as historical references and are labeled as made with Omagen v1. Before the stable release, record the source background provenance and confirm that every background and preview can be redistributed with the project. See the [provenance ledger](PROVENANCE.md) for the current open confirmations.