{#- The application frame: skip link, sidebar, top bar, page header, content. Extend it. Everything an application owns is a block, and everything the SYSTEM owns is the markup between them — the class names, their nesting, and the four layouts that all render this same DOM. A project that hand-writes this frame has forked the part of the design system that is hardest to keep in step, which is the whole reason this file exists. Navigation arrives as DATA rather than markup, because markup is what drifts: nav = [{"section": "Directory", "items": [{"href": "/contacts", "label": "Contacts", "icon": "users"}]}] A group with no `section` renders its items flat. `icon` is optional and is only used if the application has registered an `icon()` global — the package ships no icon set, on purpose (see the docs). For anything the data cannot express, override `{% block nav %}` and write the `ads-nav` markup yourself. Context it reads, all optional: nav the groups above current the path of the page being rendered, for `aria-current` layout_class "", "ads-app--folded", "ads-app--right" or "ads-app--horizontal". The reader can fold and unfold the sidebar with the top bar's menu button; their choice is remembered and wins over this one. container_class "", "ads-container--narrow" or "ads-container--fluid" stylesheet where the vendored ads.css is served from shell_script where the vendored shell.js is served from -#} {% import "ads/nav.html" as ads_nav with context %}