Harden and simplify the ARSAS product website

[masarray]

Summary

Second landing-page audit focused on product conversion, static SEO, branding consistency, accessibility, responsive behavior, and claim precision.

Critical findings corrected

• Smart Reporting copy and metadata were being injected by JavaScript instead of existing in the source HTML. Crawlers, social previews, and no-JavaScript users could receive the older page.
• Legacy ArIED 61850 / ArIED61850Tester branding remained in social-card, favicon, and an unused hero asset.
• Major content depended on .reveal JavaScript behavior and could remain invisible if script execution failed.
• Navigation became crowded before the previous mobile breakpoint.
• The homepage emphasized building from source more than the engineering problem ARSAS solves.
• FAQ schema existed without matching visible FAQ content.
• The reporting copy could be misread as claiming universal dynamic RCB creation.
• The validator did not detect JSON-LD drift, hidden schema questions, missing static Smart Reporting links, image dimensions, legacy text assets, external manifest icons, or project-version mismatch.

Product and UX changes

• Rebuilt the homepage around the message: IEC 61850 engineering without the setup maze.
• Makes Smart Reporting, empty-DataSet/no-RCB fallback, multi-IED ownership, and visible acquisition evidence clear in static HTML.
• Adds a direct traditional-workflow versus ARSAS comparison.
• Uses compact typography, spacing, cards, and heading weights.
• Adds stable image dimensions and aspect ratios to reduce layout shift.
• Adds explicit keyboard focus treatment and a wider responsive navigation breakpoint.
• Simplifies JavaScript to menu behavior and the copyright year only.
• Supports Escape-to-close and accurate navigation button labels.
• Aligns Overview, Smart Reporting, Capabilities, Smart Control, Architecture, Roadmap, and 404 pages.

Branding and sharing

• Replaces legacy social-card copy with current ARSAS positioning.
• Removes legacy favicon labeling.
• Removes the unused legacy hero SVG.
• Makes the web manifest self-contained with a local icon.
• Adds consistent Open Graph dimensions, descriptions, and Twitter metadata.

Technical claim boundary

Dynamic recovery is described precisely as an association-scoped temporary DataSet used with a suitable available RCB, including the required permitted writes. The website does not claim universal dynamic BRCB creation or universal interoperability.

Validation

• Static website validator and public-boundary checks
• JSON-LD parsing and visible FAQ parity
• Static Smart Reporting links, image dimensions, manifest and metadata
• Source, license, UX, GOOSE and SAS invariants
• ARIEC61850 compatibility gate
• .NET restore and Release build
• Portable Windows publish and artifact upload

Application and ARIEC61850 runtime code are unchanged.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6ae8eb52fe

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve navigation when JavaScript is disabled

At viewport widths from 761px through 1080px, this new media rule hides .nav-links and shows only the menu button. Since the open class is added solely by app.js, users with JavaScript blocked or failed lose access to every primary-navigation link at common tablet and narrow-desktop widths. Retain a no-script navigation fallback (or only apply the collapsed state after JavaScript has initialized).

Useful? React with 👍 / 👎.