Logseq/Entity/UI/Area
UI Area
- In this garden, UI Area pages model one named region of a product's interface — a panel section on hardware, or a view or bar in software — and list the controls and smaller areas inside it.
What counts
Atomic Design stages
Identity and names
- Place an area at
<Item>/UI/<Area>, nesting a smaller area under the area that holds it: <Item>/UI/<Area>/<Sub-area>. - A hardware panel can also be mapped by position. Each side of the device is an area,
<Item>/UI/Front or <Item>/UI/Rear; a side laid out in rows has one area per row at <Item>/UI/Front/Row/<NN Row>, numbered top to bottom, such as Microfreak/UI/Front/Row/02 Main. - Inside a row, or on a side without rows, each item takes a two-digit number counting left to right:
01 Matrix, 02 Paraphonic Button. A numbered group of controls is an area, such as Microfreak/UI/Front/Row/01 Top/01 Matrix; a numbered single control is a Logseq/Entity/UI/Control. - Use the name printed on the panel or used in the manual, in Title Case:
Oscillator, Control Bar, Arrangement View, Scrub Area. - Search
<Item>/UI and the item's older pages before creating an area. When the garden already has a page for the same region under another name, link it from the area page, and list the older name in alias:: when codekiln asks for it, per My/AI/Rule/Logseq/No Aliases Unless Asked.
Page shape
- Frontmatter:
logseq-entity:: [[Logseq/Entity/UI/Area]]; up:: links to the containing area, and a root <Item>/UI page links up:: to the item. See Logseq/Frontmatter for shared conventions. - One bullet-wrapped H1 with the area's name, then one sentence saying where the area sits and what it is for, then a picture of the area when the user guide has one.
- A
## Controls section links each Logseq/Entity/UI/Control in the area, in panel or screen order. A ## Areas section links smaller areas when there are any. Link rather than embed; control pages are short and many. - A
## Source section links the user guide or manual section that describes the area.
Examples