# Images, captions and editorial asset guide

## Supplied assets

This package supplies original Omni Impact logo variants, three public-site screenshots, an explanatory workflow diagram, and two PDF documents. Use the [asset manifest](../assets-manifest.json) for exact paths, dimensions, hashes, captions, credits and evidence status. This edition includes no founder portrait, customer photograph, testimonial or video master.

Assets are supplied for editorial coverage of Omni Impact. Preserve context, avoid implying endorsement, and use the supplied marks intact. Third-party names and marks visible in an interface retain their owners' rights. Font files retain the bundled SIL Open Font License notices.

## Logo selection

Use the horizontal **gradient-light** lockup on a light background and **gradient-dark** on a dark background. The black and white variants are the supplied one-color alternatives. The symbol alone works where the company is already named. SVG is preferred for scaling; transparent PNGs are provided for standard publishing workflows.

Do not redraw, stretch, rotate, crop, recolor or alter the gradient. Leave clear space of at least one quarter of the symbol diameter. Keep the symbol at least 20 CSS pixels high. Use the provided horizontal logo rather than trying to recreate the wordmark with a font.

## Visual reference

| Role | Value |
|---|---|
| Charcoal | #141519 |
| Cool white | #F9FAFB |
| Light-surface blue | #3269C7 |
| Dark-surface blue | #5B8FE0 |
| Headings | Omni Impact Brand, typically Medium/Semibold |
| Body and interface type (website and product) | Omni Sans, since October 2026 |

The PDFs and offline page in this package are typeset in Omni Grotesk, the earlier supporting face, whose files and license travel with the package.

## Image 1 - Dashboard illustration

**File:** `assets/screenshots/01-dashboard-illustrative.png`

**Caption:** Omni Impact's public homepage illustrates its dashboard using a Paxora demo scenario, a fictional accounts-payable automation brand. All displayed scores, trends, brands and account details are illustrative; this is not a customer result. Captured October 14, 2026.

**Alt text:** Dark Omni Impact dashboard illustration with visibility summaries, a trend chart and competitor comparisons for the Paxora demo scenario.

**Source:** [Public homepage](https://omniimpact.net/). **Credit:** Courtesy of Omni Impact.

## Image 2 - Website findings illustration

**File:** `assets/screenshots/02-findings-illustrative.png`

**Caption:** An Omni Impact interface illustration on the public Recommendations page shows website findings and a proposed fix in the Paxora demo scenario. Displayed scores, issues, expected effects and the pull-request notice are illustrative; they do not record a change to a real site, establish a customer outcome or guarantee that a suggested tactic improves AI visibility. Captured October 14, 2026.

**Alt text:** An illustrative page-analysis view for the Paxora demo scenario lists website issues beside a selected finding, current and optimized code for a proposed fix, and a pull-request notice.

**Source:** [Recommendations page](https://omniimpact.net/recommendations/). **Credit:** Courtesy of Omni Impact.

## Image 3 - Public readiness entry screen

**File:** `assets/screenshots/03-readiness-public.png`

**Caption:** The public Omni Impact AEO Readiness Check entry page, captured October 14, 2026. No domain was submitted for this image. A website diagnostic is distinct from a measurement of actual mentions or citations in AI answers.

**Alt text:** The public AEO Readiness Check page with an empty domain field and a list of diagnostic categories.

**Source:** [Readiness Check](https://omniimpact.net/aeo-readiness-check/). **Credit:** Courtesy of Omni Impact.

## Image 4 - Workflow diagram

**File:** `assets/diagrams/measurement-to-action.svg`

**Caption:** Conceptual Omni Impact workflow: define questions, inspect sampled answers and sources, review improvements, then compare later observations. Diagram; not a screenshot or performance result.

**Alt text:** Four connected stages labeled Ask, Inspect, Improve and Measure, with a note that observed changes do not prove causation.

**Credit:** Omni Impact.

## Reuse and accessibility

Keep the illustrative/demo qualification with any screenshot, including social crops and broadcast graphics. Preserve image aspect ratios; do not enlarge small text beyond legibility or present a screenshot date as a measurement period. Use alt text and meaningful captions. The offline media page and text files provide accessible explanations alongside visual documents.