The Knowledge Base also lives inside mywork's floating chat-widget. Click the chat button at the bottom-right of any mywork page, click the Help tab at the bottom of the chat shell, and you're reading articles without leaving your work. This article tours that surface and explains how it stays in sync with the public reader.
Where it lives
mywork's chat-widget shell has four tabs at the bottom:
Chats — direct messages and group conversations.
Notifications — system-generated alerts.
Calls — voice calls.
Help — the Knowledge Base.
Clicking Help swaps the body content for a Web Component called . The component is Shadow-DOM-isolated, so its CSS doesn't bleed into mywork and mywork's CSS doesn't bleed in.
There is also a ? icon in the shared page header of every mywork screen. It always opens the Help tab. When the Knowledge Base has articles for the current screen, the icon lights up with a badge and a tooltip such as 3 help articles for this page.
The top bar
Every view shares a top bar: a breadcrumb trail on the left and a compact search field on the right (placeholder Search the Knowledge Base...). On the landing the trail reads Knowledge Base with a count of top-level collections; once you drill in, it shows a home icon › folder › … › current location, and every earlier segment is clickable to jump back. There is no separate back button — the breadcrumb is how you go back.
Four internal views
The widget renders one of four views at a time, depending on what the user is doing.
Tree — the landing. Shown on open and whenever the search field is emptied from the landing. When the current mywork screen has matching articles, a Suggested for this page block lists up to five of them first. Below that is a vertical list of folder cards — each with the folder icon, the folder name, the recursive article count, and a chevron. Clicking a card drills into the folder.
Folder — a drilled-in folder page, mirroring /f/ on the public reader: the folder's subfolders as cards, then its articles as cards. Click a subfolder to go deeper or an article to open it. The breadcrumb grows one segment per level.
Search — type into the search field (300 ms debounce). The current view is replaced by a flat list of article hits, each with the article icon and title. It is the same FULLTEXT result as the public reader's search — see Search the Knowledge Base. Clearing the field returns you to wherever you were (the folder you were in, or the landing).
Article — click a suggested article, a folder's article, a search hit, a Related card, or any in-body /a/ link. The rendered body appears with an inline On this page contents list at the start and a Related list at the bottom. The breadcrumb ends with the article title; clicking the folder segment before it returns to that folder.
The widget remembers where you were. Switching tabs and coming back to Help, or the chat panel refreshing, restores the same view, folder, and article rather than resetting to the landing.
Suggested for this page
The block at the top of the landing is driven by the mywork screen you are on. The widget sends the page's identifier to mywork's proxy, which looks the page up in mywork's own page registry and searches the Knowledge Base for that page's human label (for example "HR Settings"). The top hits come back as Suggested for this page. The same lookup lights up the header ? badge.
Authors: to make an article appear as a suggestion for a mywork screen, put the screen's label in the article's Keywords field. Keywords are part of the search index, so the label ranks the article even if the body never uses those words. See The Editor.
Pages that aren't in the registry, and screens with no matching articles, simply show no block.
How content gets there
The widget never talks to the Knowledge Base directly and never makes a cross-origin request. Every fetch goes same-origin to mywork's own KB proxy at /rest/kb/…, with the mywork session cookie. The proxy requires a signed-in mywork user, forwards the request to the Knowledge Base server-side with a shared guest key, and returns the response verbatim. The requests are:
/folders — on first mount. The full folder tree with article summaries, cached in the page for the session.
/suggest?path= — on mount, when the page is known. The suggestions for the current screen.
/search?q=… — each time the user types (debounced). Up to 50 article hits, ranked.
/article?slug=… — when opening any article. The article body, keywords, and Related list.
/widget.css — on first mount. A self-contained stylesheet covering article body chrome (callouts, code blocks, tables, image alignment), injected as a