Repository navigation
feat(home): How OneUptime works shows how a problem moves through OneUptime, and every product it has - #8999
Merged
Merged
Conversation
…Uptime and every product, by category The dialog named four products and said in one dense sentence that the rest was optional, so people never learned what else OneUptime does (#8891). It is now a small explorer: How it fits together first (Detect, Respond, Communicate, Improve, each a sentence with the products that do it), then every product of the products menu, one category at a time, each saying what it does and opening its page. It is built from the products menu's own catalog (getExploreCategories), so it stays in step with it, leaves out what the project hides or the server switched off, and names a plan a product needs before the click. The Welcome checklist's strip keeps its four products; its dialog-only props went with the old dialog, and its docs links are shared with the dialog. Opening a product records how_it_works/product_opened. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Every sentence the overview draws, in each language's own words for the products, using the menu's names (Korean 경고 for an alert, Italian "log", Danish "metrikker", Swedish "mätvärden", Simplified Chinese 追踪). Detect and Respond were keys nothing drew any more: Respond was still English in fifteen languages, and Danish, Swedish, Russian and Arabic now word Detect as a step's title alongside the other three. Co-Authored-By: Claude Opus 5.5 <[email protected]>
…nguage, and its chevrons point the way the line reads Each step's sentence was handed Detect's two defined words, and a sentence handed a slot it does not name reads as one its language has not worded: Respond, Communicate and Improve were English on a German page. Each sentence now gets only the slots it names (getSlotsOf). Icon already turns a chevron round on a page read right to left, so the hand-turned rtl:-scale-x-100 turned it back (ReadingDirectionGuard). And the docs links' test id is named like a test id, not like the copy the orientation scanner reads as words (HOW_IT_WORKS_*). Co-Authored-By: Claude Opus 5.5 <[email protected]>
…ory, the keyboard, the project's products and every language A new suite renders the overview and the dialog with the real catalog and the real locale files: the four steps in order with the products that do them (links into the current project), the defined words in Detect's sentence, every category of the products menu with its count and its line, the tab list's keyboard (both arrow pairs, wrapping, Home and End, the other way round in Persian) and Next, opening a product in place or in a new tab (with the event it records), hidden, switched-off and plan-locked products, no project, German and Persian, and the regression where three steps' sentences fell back to English. HowOneUptimeWorksAlwaysThere follows the dialog's new content (and draws it inside a router, as App.tsx does), and the orientation copy scan now reads the dialog's two files, so every word they draw stays a key that every language words. Co-Authored-By: Claude Opus 5.5 <[email protected]>
…with their one word Two lines merged into main since #8628 and #8767 said what those changes had retired, and OneWordInSentencesPerThing failed on main: the Korean notification settings page said 알림 beside an alert's 경고 in one sentence, and the Norwegian Incoming Request page set a monitor "frakoblet", Disconnected's word, where Offline is "offline". Co-Authored-By: Claude Opus 5.5 <[email protected]>
…the keyboard, opening a product, a phone and Persian The browser suite asked for the old dialog's four list items and its 'feed the loop' sentence. It now checks the four steps and their products, the focus starting on the first section, the arrow keys, End, Home and Next, a category's products, a product opening its page and closing the dialog, the sections as a sideways row inside the dialog on a 390px phone (the page never scrolls sideways), and Persian with the sections on the right and Left going on to the next. Co-Authored-By: Claude Opus 5.5 <[email protected]>
…guage The Home Page & Shortcuts page said only that How OneUptime works stays one click away. It now says the dialog opens on How it fits together, the four steps a problem moves through with the products that do each, then the Products menu's categories, walked with the arrow keys or Next, and that the project's hidden products are left out - in all 17 docs languages, each naming the Dashboard's own words in bold. A docs fact pins the four steps to the order the overview draws them. Co-Authored-By: Claude Opus 5.5 <[email protected]>
… works The dialog now lists every product OneUptime has, so "features", "capabilities", "all products" and "what can oneuptime do" find it in Search (Cmd/Ctrl+K) beside "how it works" and "overview". The comments in Help and the products catalog describe what it shows now. Co-Authored-By: Claude Opus 5.5 <[email protected]>
…works-overview # Conflicts: # packages/App/FeatureSet/Dashboard/src/Locales/ar.json # packages/App/FeatureSet/Dashboard/src/Locales/da.json # packages/App/FeatureSet/Dashboard/src/Locales/de.json # packages/App/FeatureSet/Dashboard/src/Locales/en.json # packages/App/FeatureSet/Dashboard/src/Locales/es.json # packages/App/FeatureSet/Dashboard/src/Locales/fa.json # packages/App/FeatureSet/Dashboard/src/Locales/fr.json # packages/App/FeatureSet/Dashboard/src/Locales/hi.json # packages/App/FeatureSet/Dashboard/src/Locales/it.json # packages/App/FeatureSet/Dashboard/src/Locales/ja.json # packages/App/FeatureSet/Dashboard/src/Locales/ko.json # packages/App/FeatureSet/Dashboard/src/Locales/nl.json # packages/App/FeatureSet/Dashboard/src/Locales/no.json # packages/App/FeatureSet/Dashboard/src/Locales/pt.json # packages/App/FeatureSet/Dashboard/src/Locales/ru.json # packages/App/FeatureSet/Dashboard/src/Locales/sv.json # packages/App/FeatureSet/Dashboard/src/Locales/zh-CN.json # packages/App/FeatureSet/Dashboard/src/Locales/zh-TW.json
…rean Dashboard does Two lines merged into main said 알림 (a notification) for Alerts beside 경고 everywhere else, and OneWordInSentencesPerThing failed on main: the menu path to an alert's AI settings, the re-investigation cooldown's row, and the heading about new incidents' and alerts' fixes, with the link to it, which now keeps its anchor in step. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Contributor
Author
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
This was referenced Nov 16, 2026
Merged
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
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.
What changed, and why
"How OneUptime works" (Help, Home's Explore OneUptime, Search) named four products and then said, in one dense sentence, that telemetry and infrastructure "feed the loop" and everything else was optional. People asked it to show what OneUptime can actually do, more simply and more interactively (#8891). It is now a small explorer of the whole product that still opens on the one thing a newcomer needs first: how the pieces fit together.
The new dialog, in words
Title and line under it: "How OneUptime works", "Everything OneUptime does, and how it fits together."
A list of sections down the side (on a tablet or phone it becomes a row of pills that scrolls sideways inside the dialog): How it fits together first, then, under a small "Products" label, every category of the Products menu with how many products it holds: Essentials 7, Observability 8, Security 2, AI 2, Code 1, Resources 5, Infrastructure 12, Cloud 3, Dashboards & Automation 4. Just seeing that list answers "what else can OneUptime do?".
How it fits together (the first view): "From the first sign of trouble to the fix, every problem moves through four steps", then a numbered, connected timeline:
Each product is a small chip with its own icon and colour, and opens its page.
A category shows its name, one line saying what it is for ("The servers, containers, clusters, storage and networks you run yourself."), and a grid of product cards (icon, name, what it does, a chevron). A card opens the product.
Next:
How it behaves
useDashboardNavigationItems) through the same rules as Home's Explore OneUptime (getExploreCategories,getListedItems,withProductMarks), so a product added to the menu shows up here with the same name, words, icon and colour, in every language.AppLink, so unsaved work still asks first). Ctrl, Cmd, Shift or Alt opens it in a new tab and leaves the dialog open for the next one. Each opening recordshow_it_works/product_opened(the product's key and whether it came from a step or a category), documented inDocs/analytics/activation.md.What I chose not to do, and why
ExploreProducts.tsxis untouched: the dialog reuses its exportedgetExploreCategories.Also fixed on the way
mainrecently failedOneWordInSentencesPerThingonmain: the Korean notification settings page and upgrade notes said 알림 (a notification) for an alert, which the Korean Dashboard calls 경고 (a menu path, a table row, and a heading with the link to it, whose anchor now stays in step), and Norwegian set a monitor "frakoblet" (Disconnected's word) where Offline is "offline". All fixed.RespondandDetectwere dead keys;Respondwas still English in 15 languages. They are the step titles now, worded in every language.Tests
Common/Tests/App/Dashboard/HowOneUptimeWorksOverview.test.tsx(54 tests): real i18next with the real locale files, the real catalog and the project-products store. It covers the four steps and their products (links into the current project), the defined words, every category with its count and its line, the tab list and keyboard (both arrow pairs, wrapping, Home/End, right to left, Next, focus), opening a product in place or in a new tab and the event it records, hidden, switched-off and plan-locked products, no project, German, Persian, the dialog (description, docs links, Was this clear?, initial focus, closing, reopening on the first section), and the pure helpers (getSectionForKey,getLoopStepProducts,getSlotsOf,scrollBackToStart).HowOneUptimeWorksAlwaysThere(the dialog's new content, drawn inside a router as App.tsx does),ProductOrientationCopy(the copy scan now reads the dialog's files, so every word stays a key every language words),DashboardCommandPaletteFindsMore(the new Search words),IntroductionDocsFacts(the docs name the four steps in the order the overview draws them), and the browser specE2E/HomeOverview/HowOneUptimeWorks.spec.ts(12 tests, run locally against the offline fixture: sections, keyboard, opening a product, phone, dark, German, Persian).HomeOverviewDarkMode),GlossaryTermsPerPage,ReadingDirectionGuard,NestedControlsGuard,SentencesFromTranslatedPiecesGuard,TranslatedSentenceInRowGuard,ComponentArrowsInRightToLeftPages,DialogPrimaryActionGuard,CardInCardGuard, the hardcoded-strings guard, the analytics catalog and docs tests, every locale guard (DashboardLocalesGuard,OneWordInSentencesPerThing,OneNamePerThingGuard,DashboardWordsInPersian,ArabicLocaleGuards,DashboardFrenchPunctuation,FrenchNoBreakSpacesGuard,EsbuildLocales,DashboardRuntimeLocalesand more), the Introduction docs translation and facts suites, and the neighbouring Home, Help, phone-menu and palette suites.HeaderAtTabletWidths.spec.tsand the Home spec's checklist and Explore tests also pass in the browser.Closes #8891
🤖 Generated with Claude Code