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 in an AUP tree?
Read identities, types, properties and children through one task card.
A task card can contain a view, two text nodes and an action. Parent–child relationships group the content. A node’s id identifies it, type says what it is, and props supplies its attributes.
{"id":"task-title","type":"text","props":{"content":"Prepare the talk"}}This minimal example displays static text. It does not connect a database or persist state. Resource connections require mechanisms such as src and bind; actions require event bindings.
Node identity and resource addressing are different: task-title identifies a UI node, while /tasks/talk/title would identify a resource in an AFS namespace. The connection must be explicitly established.
The tree gives renderers structure to interpret and systems structure to inspect. It does not infer all business semantics by itself.
Further reading
Technical documentation: read the full reference.
Check your understanding
Is a node id the same as an AFS path?
No. The id identifies a UI node; the path addresses a resource. A binding or runtime structure establishes their relationship.
Continue along a learning path
- From protocol to siteStep 2 of 9