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 is Web Device?
Organizing content and interfaces into a website is another layer of work.
- Content and pagesOrganize and compose→
- Web DeviceBuild and render→
- Website
This Learning page needs more than interface nodes. It needs a URL, languages, navigation, a theme, content lists, search metadata and a build process. Web Device handles this Web-facing organization and presentation.
Consider an article page: site navigation at the top, an article title and body in the middle, and a footer below. A component is a reusable presentation unit, such as the article header. A layout specifies how units are arranged and what data they receive. The header receives this article’s title, author and cover before presenting it.
An AUP tree describes expanded interface nodes. An AUP layout is an authoring form for composition: it can reference components, which Web Device interprets and renders under its site conventions. The forms are related, but a component name is not automatically a core node type.
In Arc, Web Device is a provider. A site uses pages/ for pages, content/ for content, and .web/ for theme and component configuration.
There is also a supported path for directly rendering AUP trees as static HTML. This is related to layout composition, but does not imply that every interactive primitive can be dropped into every Web layout section.
For this Learning site, verify routes, languages, content and links. For an interactive AUP session, also verify events, state and updates. Passing one set does not substitute for the other.
Further reading
Technical documentation: read the full reference.
Check your understanding
Why does a complete website need more than AUP nodes?
It needs routing, content organization, languages, themes, SEO and builds—the site responsibilities handled by Web Device.
Continue along a learning path
- From protocol to siteStep 5 of 9