Reference
The pages generated from the source — the UI kit's classes, every CSS variable, the events, the core API, the engine, the wrappers and the icons — beside where aparté runs and what will not change under you.
On this page
| Page | The question it answers |
|---|---|
| Classes | Which ready-made classes can I put on my own elements? Buttons, fields, switches, tags, alerts, menus, tabs, avatars — plain classes on plain elements, themed by the same variables as the chat. Each family has its page, with a live example, in the kit. |
| CSS variables | Which --aparte-* token do I set to change this? Every declared variable with its default, and the ones a component reads with a fallback. |
| Events | What does aparté dispatch, with what detail? One row per event. |
| Core API | What does @aparte/core export, with which signature? Every export by area: configuration, client, transports, messages, conversations, questions, element types, utilities. |
| Engine | What does @aparte/engine export? The loop and its run events. |
| Wrappers | What is the same on React, Vue, Svelte and Angular? Every slot and callback, and how each framework spells it. |
| Icons | Which glyphs exist, and how do I swap them? The built-in set and the extended one behind @aparte/core/icons. |
| Support matrix | Does it run where my users and my build are? Browsers, Node, frameworks, bundlers and TypeScript. |
| Stability | What can I build on without a rename landing on me? The frozen names and the notice a change gets first. |
The elements themselves — <aparte-chat>, <aparte-composer>,
<aparte-select>… — are under Components, and llms-full.txt
holds every built page in one file.