Preview parity
The catalog thumbnail, full studio, and exported result use the same geometry and rendering rules. A thumbnail may be paused or simplified for cost, but it must not advertise a different effect.
How the platform earns trust
A preview, a studio, and an export should tell the same truth.
Every EvenMesh module is expected to remain useful when animation stops, input changes, the viewport narrows, or the generated code leaves the platform.
The release bar
Four promises behind every studio.
Bounded performance
Particle counts, DOM layers, connection work, pixel ratio, and animation loops receive explicit ceilings. Offscreen work should pause, event-driven interactions should not become permanent render loops, and compact cards stay cheap.
Accessible states
Authored text remains semantic. Controls have names, keyboard behavior is deliberate, focus stays visible, state changes are exposed where necessary, and reduced-motion preferences produce a complete stable result.
Portable output
Every visible export action must produce a real snippet or file. Generated code is scoped, responsive, dependency-free where promised, and includes the same reduced-motion and input behavior demonstrated in the studio.
The release checklist
What the project checks—and rechecks—before production release.
This is the release contract, not a substitute for a dated audit report. Automated evidence lives with the code; production-host, desktop, mobile, assistive-technology, and real-device checks remain release gates whenever the affected surface changes.
- 01
Static structure
Titles, labels, headings, landmarks, canonical links, descriptions, schema, and server-rendered guidance are checked without depending on client-side animation.
- 02
Every changed preset
Each new or changed preset is opened at representative desktop and mobile widths, with broader regression sampling across the catalog. Overflow, clipping, alignment, empty states, hostile control values, and preview/export drift are treated as defects.
- 03
Every input model
Pointer, touch, keyboard, focus, Escape behavior, pause, replay, visibility changes, and reduced motion are exercised whenever the interaction supports them.
- 04
The production build
Type checking, linting, automated tests, static export, broken-link checks, metadata uniqueness, and structured-data parsing run against the final output. Real-browser and deployed-host smoke tests complete the release review.
Built to be checked
The standard is useful only when it can be checked.
The current release is a browser-first static application: no account, no upload service, and no hidden renderer between the studio and the exported result.