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
How do AUP and Web Device divide responsibilities?
One describes interface contracts; the other organizes a Web site implementation.
Separate a protocol from the system hosting it to understand where a change belongs.
| Question | Start with AUP | Start with Web Device |
|---|---|---|
| Interface structure? | Tree, types and properties | Supported rendering paths |
| Events and operations? | Event and state contracts | Web implementation and integration |
| URLs and languages? | No whole-site directory convention | Pages, locales and routes |
| Reusable brand header? | Layout composition | Theme and site components |
| Search discovery? | Not an SEO system | Metadata and build output |
Changing a task button’s operation can involve an AUP event. Changing an article header usually involves a Web Device component. Organizing /en/learn/ is a site-design concern.
Check the inference: successfully building HTML does not establish synchronized multi-display sessions. Session and update behavior requires its own verification.
Further reading
Technical documentation: read the full reference.
Check your understanding
Where should you start when replacing a brand header?
The Web Device theme and components, and the page layout that uses them.
Continue along a learning path
- From protocol to siteStep 6 of 9