Resource ViewsRegistry Catalogue
Overview
Every resource view registry the built-in engines declare — one page per engine, with each resource's registry names, built-in ids and a link to the source that wires it.
Registry Catalogue
The catalogue lists every registry the built-in engines declare. Use it to find:
- the registry name for the view you want to add to;
- the built-in ids in each slot, to place your items
beforeorafter; - the source file that renders the view, to see exactly how it is wired.
| Engine | Resources | Page |
|---|---|---|
| Fleet-Ops | 25 | Fleet-Ops Registries |
| Storefront | 8 | Storefront Registries |
| Ledger | 7 | Ledger Registries |
| IAM | 4 | IAM Registries |
| Developers | 5 | Developers Registries |
Reading an Engine's Page
Each page starts with a table of its resources:
| Column | Shows |
|---|---|
| Resource | The resource's name in the registry, which links to its section below |
| View | The screen it is, as users know it |
| Table, Details, Side panel | The source files that pass the registry to each view, on GitHub. A dash means the resource has no view of that kind |
Below the table, each resource opens to show its registries and built-in ids:
| Slot | Registry | Built-in ids |
|---|---|---|
| Columns | fleet-ops:driver:table:columns | name, public-id, phone, … |
| Row actions | fleet-ops:driver:table:row-actions | view, edit, assign-vehicle, … delete |
A dash in Built-in ids means the slot has no built-in items with ids: your items still render, at the slot's default spot.
Notes That Apply Everywhere
- Details rows (header buttons, menu items, tabs) only appear for resources with a details view.
- Ids follow two rules: a column's id is its
valuePathdasherized (created_at→created-at); an action's id is its handler's name dasherized (assignVehicle→assign-vehicle). The delete action is alwaysdelete. - Source links point at each engine's
mainbranch. A file's layout can change between releases; the registry names and ids are what stay stable.
Your Own Engine
If your extension's views are extensible, document their registries the same way. See Making Your Views Extensible.