wu-sheng opened a new pull request, #883:
URL: https://github.com/apache/skywalking-website/pull/883

   Completes the **Meet Horizon UI** 17-post series — **Act 5: make it yours & 
adopt**.
   
   | Post | Topic | Figures |
   |------|-------|---------|
   | **15/17** | Customization — Config-Driven Layer Templates | 4 |
   | **16/17** | Localization in Eight Languages | 3 |
   | **17/17** | Getting Started & Migration | 0 (code blocks + compat table) |
   
   **15 — Customization.** The whole console is template-driven: edit any 
layer/overview as a **local browser draft**, **Preview** it, and **Check diff & 
push** to publish to OAP (bundled JSON is the seed; OAP wins at render). Covers 
the widget canvas, add-a-layer, and Export/Import portability.
   
   **16 — Localization.** Eight first-class locales (English source + 
de/es/fr/ja/ko/pt/zh-CN). Translations are **server-side overlays** merged onto 
the source once per request; click-to-translate on the Translations admin; 
OAP-supplied data (service names, tags, logs) and codes (RPM/P95/SLA) stay 
verbatim; untranslated leaves fall back to English.
   
   **17 — Getting Started & Migration.** Single env-driven container 
(`horizon.yaml`, every field a `${HORIZON_X:default}` token), point it at your 
OAP. The **OAP 10.x vs 11** matrix: observe data-plane works on the query port 
`:12800`; operate surfaces need OAP 11's admin host `:17128`. Drop-in migration 
from an existing UI (same GraphQL + MQE, no agent/backend changes).
   
   All three drafts were render-verified against the screenshots and 
adversarially fact-checked against the `skywalking-horizon-ui` source 
(ship-as-is, zero findings). Hugo builds clean. Features framed as Horizon 
capabilities (not pinned to a release); the install example uses a generic 
`:<version>` image tag.
   
   Chinese translations to follow.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to