Home: show both ways of investigating with AI - #903
Merged
Conversation
The page led with observability *for* AI and treated AI *for* observability as one product feature. SkyWalking now runs in both directions, so the hero and the highlight rows say so. Hero: the headline becomes two sentences, keeping the cloud-native identity and adding the turn. The lead names both paths instead of only the built-in assistant, and the meta description follows — it is what search and social actually render, and it still described only the assistant. Highlights: a second row for the AI-client path, with the Codex desktop capture and the capability/permission/credential boundary as its points. The 3D-map row flips to keep the rows alternating. Its clip is referenced from /screenshots/horizon-1.0/ rather than copied into /images/home/, so the 3 MB file is stored once and shared with the Codex post that also uses it. Deep-link hooks on the three feature headings, reusing the copy-and-select behaviour the docs and downloads cards already ship. The home page renders through the theme's baseof, which we do not fork, so the script comes in as a shortcode. The hook lives in a .frow-title wrapper that owns the containing block, and the id sits on that wrapper rather than the h2 — the theme's anchor.js injects a second hook into any heading carrying an id. No component names in the hero or the new row: SkyWalking is the brand a reader knows, and OAP, a permission identifier and "registry" all assumed concepts the page has not introduced yet. Also refreshes the AI Assistant clip and its poster, now 1920x936 and matching each other. Links go to the /next/ MCP doc, matching how the assistant row already links. MCP is on horizon-ui main and its page is live, but not in a tagged release yet, so /latest/ has no mcp page. The announcement post is still a draft; it becomes a second CTA when it publishes.
✅ Deploy Preview for skywalking-website-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The home page led with observability for AI and treated AI for observability as a single product feature. SkyWalking now runs in both directions, so the hero and the highlight rows say so.
Hero
Observability for cloud-native and AI./And AI for observability.— two sentences, keeping the identity term the project is known byseo_titleis deliberately unchanged. Adding the second clause makes it 83 characters; Google renders about 60, so it would truncate mid-phrase and gain nothing. It stays at 57 and fully visible.Highlights
A second row for the AI-client path, with the Codex desktop capture and the capability / permission / credential boundary as its three points. The 3D-map row flips so the rows keep alternating.
The clip is referenced from
/screenshots/horizon-1.0/rather than copied into/images/home/, so the 3 MB file is stored once and shared with the Codex post that also uses it.Deep-link hooks
The three feature headings get copy-able hooks —
#ai-assistant,#ai-client,#topology-3d— reusing the select-and-copy behaviour the docs and downloads cards already ship, rather than new JS. The home page renders through the theme'sbaseof, which we do not fork, so the script arrives as a shortcode.Two things worth knowing for anyone touching this later:
.frow-titlewrapper that owns the containing block. Positioning it against theh2broke whenever an ancestor gainedposition.idsits on that wrapper, not theh2. Docsy'sanchor.jsappends its own hook to any heading carrying anid, which produced a second, duplicate icon.Wording
No component names in the hero or the new row.
Horizonis a project and component; SkyWalking is the brand a reader knows.OAP, a permission identifier and "registry" were also removed — each assumed a concept the page has not introduced by that point, andOAPappeared nowhere else on the page.Horizonstill appears in row 1 and the capabilities card, which are existing copy and out of scope here.Media
Refreshes the AI Assistant clip and poster — now 1920x936 and matching each other.
Verification
Clean
hugobuild, no errors: 3 feature rows, all three hooks present, zeroh2elements carrying anid(so no theme duplicate), zeroHorizoninside the hero<section>, and both clips published at full size.Links
Both rows point at
/next/docs, matching how the assistant row already linked. MCP is merged tohorizon-uimain and its page is live, but it is not in a tagged release yet, so/latest/has nomcppage. The Codex announcement post is stilldraft: true— an HTML comment marks where it becomes a second CTA once it publishes.