Repository navigation
Conversation
This was referenced Nov 16, 2026
allozaur
force-pushed
the
allozaur/docs/llama-ui-storybook
branch
from
November 16, 2026 13:52
1e11686 to
e53c531
Compare
allozaur
force-pushed
the
allozaur/docs/llama-ui-storybook
branch
from
November 16, 2026 16:12
e53c531 to
33cdd56
Compare
allozaur
force-pushed
the
allozaur/docs/llama-ui-storybook
branch
from
November 16, 2026 16:50
33cdd56 to
7388192
Compare
allozaur
force-pushed
the
allozaur/docs/llama-ui-storybook
branch
2 times, most recently
from
November 16, 2026 18:58
e36eafc to
469bb99
Compare
allozaur
force-pushed
the
allozaur/docs/llama-ui-storybook
branch
2 times, most recently
from
November 17, 2026 05:55
d2a9da1 to
d3611b1
Compare
allozaur
force-pushed
the
allozaur/docs/llama-ui-storybook
branch
from
November 17, 2026 10:31
d3611b1 to
fe20107
Compare
allozaur
force-pushed
the
allozaur/docs/llama-ui-storybook
branch
from
November 17, 2026 11:15
fe20107 to
2e54d38
Compare
…ma-ui As Llama Chat does since it moved onto the library: the pages import the base components as @ggml-org/llama-ui/ui/<name>, and the design system export reads the tokens from ui/lib/ui. Assisted-by: Claude (Opus 5.5 Medium)
…/apps/chat The move to ui/ rewrote every tools/ui in these pages to ui/apps/chat, which put the library there too, and Architecture > Stack still drew the ui/ folder as a proposal. The Stack, Introduction and Product pages and the Design guidelines now say where each part lives, and the library's own Storybook introduction says that Llama Chat is built on the package. Assisted-by: Claude (Opus 5.5 Medium)
The design system commit was squashed from allozaur/docs/storybook-overhaul at 4bddabf. This adds what that branch gained since (up to a83b110), in the ui/ folders, so there is one Storybook to work on: - Brand: a Lockup page for Llama and llama.cpp with their clear space and smallest size, Llama Sans and Llama Mono on their own Typography pages, Llama Mono's glyph grid, and the brand's repository named ggml-org/llama-brand - Fonts: Llama Sans and Llama Mono from llama-brand's latest, with optical sizes from 10 to 36; they live in ui/lib/ui - Communications: the Virtual models post, and brand files that download as files, also through a CDN redirect - Architecture: Llama Harness as its own package, Llama Connect by name with its two figures in Channels, brand.llama.app next to ui.llama.app - Scrapbook: five key visual proposals after four reference sets - Bash code blocks mark shell commands and flags - export:brand-readme, which exports the logo, font and palette pieces for llama-brand's README Assisted-by: Claude (Opus 5.5 Medium)
The brand pages named the app "the web UI" where they meant Llama Chat: the asset grid, a communications board, the Llama Mono interface sample and the logo usage notes. Descriptions of what it is (the built-in web UI, the legacy web UI it replaces) and sample chat text stay as they are. Assisted-by: Claude (Opus 5.5 Medium)
The brand (logo, type and colours), Communications (direction, foundations, elements, modules, key visuals and applications, the store pages and their scenes), the brand book BRAND.md as Agents > Brand guidelines, the key visual proposals in the Scrapbook, and the scripts that render llama-brand's README art and export the design system for Claude, now live in ggml-org/llama-brand, next to the files they draw, with their own Storybook. This Storybook keeps Llama UI and Llama Chat: the introduction, the design guidelines, the philosophy, the architecture, the UI and the UI scrapbook. The brand parts the remaining pages draw with (the post frames, the logo geometry, the fonts and the splash screens) stay. Links to the moved pages are no longer redirected here, and the .svx type declaration moves to the stories' root, out of the logo showcase that held it. Assisted-by: Claude (Opus 5.5 Medium)
The ContinueConversation story ended while its reply was still being stored, and the next story reset the stores under it. It now waits for the reply to finish. Assisted-by: Claude (Fable 5.2)
…elling them out The Storybook's color scheme helper, its mode decorator and its surface toolbar compared string literals: the mode-watcher storage key, 'dark', 'light', 'system', 'paper', 'matte' and the dark media query. They take mode-watcher's modeStorageKey, the ColorMode and SurfaceTheme enums, MEDIA_QUERIES.PREFERS_DARK and applySurfaceTheme from the app instead. Assisted-by: Claude (Opus 5.5 Medium)
Six ways to set the add key and the model selector apart from the white chat form in light: a darker fill, a tighter shadow, a hairline edge or a flat shade. C, the tighter shadow, was chosen and is --elevation-key; the others stay as the record. Assisted-by: Claude (Opus 5.5 Medium)
allozaur
force-pushed
the
allozaur/docs/llama-ui-storybook
branch
from
November 17, 2026 13:44
430f34b to
a5c8ac4
Compare
allozaur
changed the base branch from
allozaur/style/glass-surfaces
to
master
November 17, 2026 13:44
…to llama-brand AGENTS.md still filed proposals under Scrapbook › Brand and Communications and pointed to LogoShowcase, DESIGN.md had a proposals folder and a Design system › Foundations path that no longer exist, and the library's Introduction and Scrapbook still listed the brand sections. Proposals now go to Scrapbook › UI here and to llama-brand's Scrapbook for the brand, and a chosen proposal stays as a record, as Scrapbook › About says. Assisted-by: Claude (Opus 5.5 Medium)
…book's sections Safe areas and GlassKey were titled Design system/..., which made a second top-level section next to UI, and ChatForm single row sat at the Scrapbook's root. They are now UI › Foundations › Safe areas (after Surfaces), UI › Patterns › GlassKey and Scrapbook › UI › ChatForm single row, whose file moves into scrapbook/. Assisted-by: Claude (Opus 5.5 Medium)
Twelve logo SVGs under brand/assets/files were byte-for-byte copies of @ggml-org/llama-brand's, which Llama Chat already depends on; the stories import them from the package now. The download rule in Storybook's config and modern-screenshot went with the brand pages that used them: no story offers a file to download or takes a screenshot any more. Assisted-by: Claude (Opus 5.5 Medium)
@chromatic-com/storybook and @storybook/addon-svelte-csf were "latest", so a fresh install could take a new major. They now take a caret range from the versions in the lock, like the library's other dependencies. Assisted-by: Claude (Opus 5.5 Medium)
The Scrapbook's proposals (Composer keys, Simple and powerful, ChatForm single row and llama.app's in the library) leave both Storybooks, with the ChatForm single row fixture only they used. The sidebar order, the introductions, the sections figure, the uses figure, the library's README and AGENTS.md no longer point to it, and DESIGN.md drops the proposals section that filed changes there. Assisted-by: Claude (Opus 5.5 Medium)
Philosophy (Ideology, Product, Design and their figures) goes to its own PR. The pages that stay were set in its frame, so the Editorial, its chapter list and Figure move to editorial/ in both Storybooks, and the products figure the Introduction draws moves into introduction/. The communications pieces only Philosophy's figures drew with go with it. The sidebar order, the sections figure (which now lists Architecture), the Introduction, the Design guidelines, AGENTS.md, DESIGN.md and the redirects for old Philosophy links no longer point to it. Assisted-by: Claude (Opus 5.5 Medium)
A new UI Storybook workflow builds ui/apps/chat's Storybook whenever ui/apps/chat or ui/lib/ui changes on master (or on demand) and uploads it to the static Space ggml-org/Llama-UI-storybook, with a Space card naming the commit it was built from. Files the new build no longer has are removed; the Space's .gitattributes stays. It runs only in ggml-org/llama.cpp, takes the UI's Hugging Face token (HF_TOKEN_UI_STATIC_OUTPUT), and the Space can be changed with the HF_SPACE_UI_STORYBOOK variable. Assisted-by: Claude (Opus 5.5 Medium)
Architecture (Stack, Chat, Channels) describes products, packages and release channels that are not built yet when this Storybook lands, so it goes to the PR that holds Philosophy. The sidebar order, the sections figure, AGENTS.md and the library's Introduction (which still named Philosophy too) no longer point to either. Assisted-by: Claude (Opus 5.5 Medium)
…tory with its code The sidebar's UI section held the library's foundations and components and the app's blocks together, its Patterns were single components of either, and 13 of the library's stories were kept twice, once in each package. It now has two sections, one per layer: - Llama UI (ui/lib/ui/tests/stories): Foundations, Components (the 29 base components as Actions, Forms, Display, Overlays and Navigation), App components (ActionIcon, SearchInput, SyntaxHighlightedCode), Models and Mockups. Every library story lives with the library, imports it by its published names (@ggml-org/llama-ui/..., aliased onto src/lib) and runs as the library's tests; its type check now covers them too. - Llama Chat (ui/apps/chat/tests/stories): Foundations (Safe areas, Brand), then one folder per src/lib/components/app/<area>, each accessibility story next to its component's. Llama Chat's Storybook shows the library's stories as they are (only this app's packages are installed beside them, so Storybook resolves from here) and its story tests leave them to the library. ActionIcon's and SearchInput's stories keep the library's parts; Chat's own ActionIconCopyToClipboard and HighlightedMatch get stories of their own. Old links to the UI section redirect to the new places, and AGENTS.md says where a new story goes. Assisted-by: Claude (Opus 5.5 Medium)
The Library checks job type-checked and packed ui/lib/ui but never ran its tests, so the library's stories, which now hold every library component's, went untested in CI. It installs Chromium and runs `npm test`. Assisted-by: Claude (Opus 5.5 Medium)
Menus, popovers, dialogs and the other matte-float panels carry a 1px border that the surface made transparent, and drew their inner highlight as an inset shadow. An inset shadow sits inside the border, so the 1px of fill between it and the outer ring showed as a second edge. The border now draws the highlight, right inside the ring. Assisted-by: Claude (Opus 5.5 Medium)
allozaur
force-pushed
the
allozaur/docs/llama-ui-storybook
branch
from
November 17, 2026 22:35
0be135e to
2858836
Compare
This branch has not been deployed
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.
Overview
Llama UI and Llama Chat get Storybooks with two jobs: documentation that people and coding agents read for context, and a test environment in which every story runs as a test. The brand pages live in
ggml-org/llama-brand, and Philosophy and Architecture are in #80.Additional information
flowchart LR subgraph code["In the repo, next to the code"] D["DESIGN.md"] L["Llama UI stories<br/>ui/lib/ui"] C["Llama Chat stories and pages<br/>ui/apps/chat"] end subgraph docs["Documentation, for people and agents"] SB["Llama Chat's Storybook<br/>Llama UI and Llama Chat sections"] HF["Hugging Face Space<br/>ggml-org/llama-ui-storybook"] end subgraph tests["Testing, in CI"] LT["Library checks<br/>npm test"] CT["E2E Tests<br/>story tests"] end D --> SB L --> SB C --> SB SB -->|"on master"| HF L --> LT C --> CTDESIGN.md). It's published to a Hugging Face Space on every UI change onmaster.npm test, now in CI, and Llama Chat's in its story tests.Part 1 of the fork's stack, on
master. Its first commit, the fork-only dev-proxy commit, stays off upstream: ggml-org#32485 has the same tree without it, in six commits. The deploy needsHF_TOKEN_UI_STATIC_OUTPUTto have write access to the Space.What changed
ui/lib/ui/tests/stories): Foundations, Components (the 29 base components as Actions, Forms, Display, Overlays and Navigation), App components (ActionIcon, SearchInput, SyntaxHighlightedCode), Models and Mockups.ui/apps/chat/tests/stories): its own Foundations (Safe areas, Brand), then one folder persrc/lib/components/app/<area>, with each accessibility story next to its component's.@ggml-org/llama-ui/..., aliased ontosrc/lib). It runs in the library'snpm testand is covered by its type check. Llama Chat's Storybook includes these stories as they are, and its own story tests leave them to the library. Llama Chat's Tailwind also scans the library's stories, so the classes only they use (the Elevation samples, for one) are generated. The 13 stories that were kept twice, once in each package, are now kept once.ActionIcon's andSearchInput's stories keep the library's parts, and Chat'sActionIconCopyToClipboardandHighlightedMatchget their own stories.AGENTS.mdsays where a new story goes.BRAND.mdand the scripts that render llama-brand's README art. The brand parts the remaining pages draw with stay: the logo geometry, the fonts and the splash screens. Their logo files come from@ggml-org/llama-brandinstead of copies.Editorial, its chapter list andFiguremove toeditorial/and the products figure moves tointroduction/. Nothing in this PR points to Philosophy or Architecture any more.AGENTS.md,DESIGN.mdand the library's README no longer mention them.ColorModeandSurfaceThemeenums,MEDIA_QUERIES.PREFERS_DARKandapplySurfaceThemeinstead of string literals.latest.ui/apps/chat's Storybook wheneverui/apps/chatorui/lib/uichanges onmaster, and on demand. It uploads the build to the static Spaceggml-org/llama-ui-storybookand removes files the new build no longer has. It runs only inggml-org/llama.cppand uses the UI's Hugging Face token (HF_TOKEN_UI_STATIC_OUTPUT), which needs write access to that Space.matte-floatpanels drew their inner highlight as an inset shadow inside a transparent 1px border, so the fill between it and the outer ring showed as a second edge. The border now draws the highlight, right inside the ring, and the edge is one line.Known gaps
npm run checkinui/apps/chatpasses as CI runs it, with only Chat's dependencies installed. Ifui/lib/ui/node_modulesis also installed, it reports errors from a second copy of Svelte (5.57.2 in the library, 5.57.3 in Chat). That also happens on master.Testing
ui/apps/chat, with only its own dependencies installed as in CI: the type check and lint pass, and so do its 166 story tests.npm run build-storybookbuilds with the library's stories in it (218 entries), and old story links redirect (all 205 old IDs checked).ui/lib/ui: the type check (stories included), prepack and its 63 tests (the story tests among them) pass, and its Storybook builds.Requirements
Claude (Opus 5.5 Medium)