You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
What are Web Device components?
Distinguish core primitives, Web-only types and theme components, then browse the default theme.
- Content recordProvides fields→
- Page layoutPasses properties and slots→
- Component implementationProduces structure and styles→
- Rendered page
Web Device theme components are reusable Web presentation implementations. For example, portal-header handles navigation, post-hero handles an article header, and content-card presents a content card. They are not additional core AUP primitives.
On an article page, a layout can choose post-hero for the title, author and cover, and detail-content for the body. The same header component serves many articles with different data.
Some components reserve named positions called slots. A body slot receives article content; a sidebar slot might receive related reading. The layout assigns content to positions; the component determines how those positions appear. A slot is not a separate data storage service.
In the implementation, manifest.json describes accepted properties, render.js produces output, and style.css supplies styling, with script.js for client interaction when needed. These files implement the reusable unit’s interface and behavior.
A site can define or override components in .web/components/. This Learning map is a site component too; the word map does not turn it into AUP’s geographic map primitive.
Follow this Learning page through the layers
This page separates several responsibilities:
- The content record holds the question, answer, body and related nodes. Editing an explanation changes content.
- The page layout sends the heading to the header mode of
learning-map, places the body in thecontentslot, and sends related material to the same component’s detail mode. It composes the page. - Component properties connect content to presentation. For example,
title=$meta.namepasses the current record’s name into the component’stitleproperty;items=$source.nodespasses the result of a data source declared by the layout.$metaand$sourceare Web Device page lookups, not expressions that arbitrary JSON can execute. - The component implementation determines heading typography, related-node arrangement and how the knowledge map responds to dragging. Those presentation and interaction changes belong in the site component.
This traces how content reaches a page. A button that changes a task’s status also needs an operation, state connections and authorization. Displaying a component does not establish that business-operation chain automatically.
What is in the default theme?
These 27 entries belong to the default-theme directory in the reviewed revision. This is not a universal inventory of all themes, sites or Web widgets. Sites can extend it.
| Component | Purpose |
|---|---|
| access-gate | Preview or membership-access messaging in the content area |
book-reader | A page-by-page document reader |
| content-card | Cards for articles, news or events |
| detail-content | Centered detail content with optional reading navigation |
| detail-sidebar | A main content area with a sidebar |
| event-card | Event listings with dates and status |
| event-hero | Event details with date, location and registration links |
globe | A WebGL globe |
| hero-banner | A homepage title, description and calls to action |
key-pad | Directional-key hints |
leaf-shadow | A moving light-and-shadow overlay |
| news-ticker | Scrolling news headlines |
| page-sections | Named content slots grouped into sections |
| page-stack | Named content slots stacked vertically |
| platform-stack | A diagram of technology layers |
| portal-footer | Site footer navigation |
| portal-header | Site-wide primary navigation |
| post-hero | Article title, author, date and cover |
| product-frame | A frame for real product screenshots or terminal records |
| product-frame-gallery | A responsive arrangement of product frames |
| product-hero | The opening section of a product page |
| product-showcase | Product feature cards |
| related-content | Related content |
| site-home | An overall brand homepage presentation |
| tag-list | Linked tags |
| tech-hero | The opening section of a technology page |
| technology-card | Technology introduction cards |
Keep three meanings separate
- Core primitives are protocol types such as
textandaction. - Web-only AUP types are additional node types listed in
AUP_WIDGETS; their presence does not establish cross-device support. - Web Device theme components are implementations composed into pages, such as
portal-header, with interfaces declared by component manifests.
A name may appear in more than one directory. Identify its list, contract and runtime instead of classifying it by name alone.
Further reading
Technical documentation: read the full reference.
Check your understanding
Is portal-header a core AUP primitive?
No. It is a Web Device theme component with a manifest and Web implementation, composed by page layouts.
Continue along a learning path
- From protocol to siteStep 8 of 9