Lexxify OPAQUE site

The corrected landing page is dependency-free HTML and CSS. The distributable ZIP contains index.html, styles.css, assets/, the original CNAME, and this README.

Open or deploy the ZIP

1. Extract the ZIP completely.
2. Open lexxify-opaque-site/index.html in a browser. No installation or build is required.
3. To deploy, publish index.html, styles.css, and assets/ together at the web root. Keep the original CNAME when using the existing GitHub Pages custom domain.

Documentation and contact actions use the original documentation URL and contact@lexxify.com. Contact buttons open the visitor's email client. All images and CSS are local; the page has no JavaScript, external fonts, trackers, or runtime dependencies.

Changes

• Rebuilt index.html and replaced the three accumulated CSS passes in styles.css with a single responsive cascade.
• Reset figure margins and constrained screenshot sizing in normal document flow. Removed absolute positioning and translated captions that caused collisions.
• Retained the warm light palette, Lexxify orange, primary blue text and buttons, and aqua backgrounds; rebuilt the hero, product gallery, React Native migration section, wallet story, integration boundary, evidence section, and closing CTA.
• Used the original, unmodified product screenshots: assets/Screenshot_20260910_153355.webp for Lexxify Hub and assets/Screenshot_20260910_153334.webp for LexxWallet. Both are 540 × 1024 pixels. The original logo is also retained.
• Replaced the oversized artifact panel with the 0.82 → 0.87.1 migration story. Made wallet recovery a numbered create → erase → recover → spend sequence, with a compact mobile summary.
• Shortened headings and supporting text. Preserved the existing audit, physical iOS runtime, and official RFC-vector caveats.
• Added a skip link, visible keyboard focus, semantic section headings, descriptive image alternatives, image dimensions, and reduced-motion support.

Latest refinement

• Matched the orange accent (#fe901c) to the most common fully opaque orange pixel in the supplied gradient logo asset, replacing the previous dark orange.
• Moved “Your password. Never your server’s.” to the first section after the hero, ahead of product and technical proof.
• Defined OPAQUE in the hero as a password authentication protocol, followed immediately by the encrypted-wallet-backup use case. Added “What is OPAQUE?” navigation and separated the protocol, wallet use case, and Lexxify library in the first explanatory section.
• Retained aqua section backgrounds and restored primary blue for OPAQUE text, hero highlights, links, and CTA buttons. The blue (#0146dc) is sampled from the dominant login-button color in the supplied Lexxify Hub screenshot; no app theme source was supplied. Original product screenshots remain unchanged.
• Made “Read the docs” the primary hero action, kept Docs visible in the mobile header, and added a documentation callout to the integration section.

Validation

• Checked local CSS/image references, fragment targets, unique IDs, section order, and documentation destinations. Checked the plain-language definition and client-only export-key explanation against RFC 9807, including section 10.4; the page links to that reference.
• Checked primary-blue text contrast against the light page and aqua backgrounds, and white button text against primary blue; ratios meet 4.5:1. Verified aqua surface colors are unchanged.
• Retained the existing responsive layout rules and added mobile styles for documentation links. This refinement has not had a fresh browser render; older screenshots are omitted from the updated ZIP.
• The existing documentation destination is retained; its live availability was not independently confirmed.

Remaining evidence limits

This work repairs the marketing page. Product implementation claims are retained from the supplied page, not independently re-audited. The added protocol explanation is grounded in RFC 9807 and its export-key guidance; application-specific recovery still requires backup encryption, storage, and recovery policy. The wallet screenshot shows recovery controls rather than four separate captured test stages. The supplied source includes no transaction hash or detailed test report, so no invented explorer link or proof artifact has been added.

Hosted preview source

In the Sites source checkout, the publishable page lives in dist/. preview.mjs and package.json are development-only helpers for responsive browser checks; neither is needed by the downloadable site or served as part of its deployment.