site: build search-to-engineering progressive landing architecture - #350
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1015d9c998
ℹ️ 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".
| for value in search_contract: | ||
| if value not in rendered: | ||
| errors.append(f"{label}: missing search-to-engineering contract value {value}") |
There was a problem hiding this comment.
Scope homepage contract checks to homepage-owned content
For the English homepage, rendered includes the shared header and footer, which already contain every required string: the header supplies “IEC 61850 tester,” while the footer supplies all five destination URLs. Consequently, a later change can remove the new task cards, hero category, and their links from index.html while this source check still passes; the rendered-site validator repeats the same whole-document substring check. Inspect the homepage-owned sections or specific anchors instead so the advertised search-to-engineering regression guard actually protects the routing introduced here.
Useful? React with 👍 / 👎.
|
Exact-head validation complete for PASS:
Change boundary remains website/content/validator only: 14 files, no production IEC 61850 runtime or engine code. |
R3 — Search-to-Engineering Progressive Architecture
Reframes the ARSAS public site around the way new users actually search and learn, while preserving the existing deep IEC 61850 engineering content.
What changes
Performance / architecture
Boundary
Landing/docs only. No IEC 61850 runtime, discovery, reporting, control, C#/XAML production path, or engine code is changed.
Please validate exact-head website build, localization, responsive media, internal links, sitemap/hreflang, release trust and repository guard workflows before merge.