{% comment %} The sidebar — the product's whole chrome. There is no top header: the workspace switcher, the primary navigation, notifications and the account menu all live here. 240px on a desktop, collapsing to 60px, and an off-canvas drawer below `lg`. **The three legs of the anti-flash contract.** The collapse is persisted, so a page can start in either of two widths and the wrong one flashes before Alpine boots. Three pieces stop that, and they only work together: a pre-paint script in base.html's head stamping `sidebar-is-collapsed` on (leg 1), the `.sidebar-initial` width mirror (leg 2, in base.html's head for the width and in styles.css for everything else), and the `x-init` below, which strips both markers the moment Alpine takes over (leg 3). Remove one and you get either a flash on every load or a sidebar frozen at its pre-paint width forever — `.sidebar-initial`'s width is unlayered and beats the `lg:w-*` utility Alpine binds. TestTheSidebar fails the page if any leg goes missing. **One copy of the nav, still.** The drawer does not break the invariant the old bottom tab bar existed to protect: it is this same

, repositioned by a media query and slid in with a transform. A *second* nav would mean a second `nav-badge-inbox`, and an out-of-band swap only ever finds the first — apps/notifications/tests/test_shell.py forbids it. **`settings_groups`.** A settings page draws its nav HERE, in place of the product's, rather than in a second column beside it — the two-column shell put 232px of settings rows next to 240px of app rows the reader had just left. The argument comes from the layout (see layouts/settings.html), because "this is a settings page" is exactly what a layout knows and nothing else does. One

, one renderer, one set of collapse rules; what changes is the rows in it and the block above them. ONE argument, and the rows themselves are it. A `settings_mode` flag beside it read better and had a silent failure: a layout passing the flag but naming the rows wrong — `settings_nav_groups`, which is what the context key is actually called — drew a sidebar with a back button, no rows and no error. Django resolves an unknown variable to the empty string, so nothing could raise. With the rows as the switch, the two cannot disagree: no rows, no settings mode. **The bell is on both sets of rows, and that is what keeps its badge honest.** Studio's settings layouts override a `sidebar_nav` block while base.html goes on rendering the poll outside it, so the 60s out-of-band swap aims at a badge id the page no longer has — what partials/_nav_badge_sinks.html existed to paper over. Two things stop that here. The poll is a child of the row (notifications/partials/_bell.html), so it can never outlive its own target; and the row is pinned to the foot of the settings nav as well, from the same `notifications_row` the product's nav draws, so every page in the product has it exactly once. It is the only unread indicator there is — a settings page without it is a page where an arriving channel_needs_reauth alert is invisible until you leave, and Plan & billing and the Library are both surfaces people sit on. ONE row, never two: `notifications_row` IS the row out of `nav_groups`, and the two branches below are exclusive. A second copy would put two elements on `nav-badge-notifications` and send every swap to whichever came first. `wsOpen` is local again. It sat on the shell wrapper while two controls opened one panel — the header's workspace button and the rail's logo mark — and with the header gone there is one trigger, inside the panel's own wrapper, so the `data-ws-toggle` guard the two-trigger arrangement needed is gone with it. {% endcomment %}

{% include "partials/_demandtrail_brand.html" with variant="sidebar" %} {% if settings_groups %} {% comment %} The way out, in the slot the workspace switcher holds everywhere else — same height, same divider, so the rows below start where they always do. Switching workspace from inside settings is not a thing to offer: half these rows are scoped to the workspace you are standing in, and the panel would silently retarget them. `.sidebar-ws-btn` rather than a nav row, for the collapse rules: at 60px it centres itself and `.sidebar-ws-name` goes, leaving the arrow. {% endcomment %}

{% comment %} Named for the workspace, not just for "app". Half these rows are scoped to the workspace you are standing in, and with the switcher gone this row is the only thing left on the screen that says which one — a reader with "Acme" and "Acme Staging" was otherwise editing tags with nothing to tell the two apart. `default` covers the user whose workspaces are all archived, whom app_home_url sends to the org's workspace list instead. `|default:'/'` on the url for the same reason the account menu's row below carries one: sidebar_context returns {} for a request with no session, and a bare {{ }} would render href="" — a link that reloads the page it is on. {% endcomment %}

{% else %}

{% if sidebar_workspaces %} {% comment %} `left-2 right-2` is studio's, and inside a 60px collapsed sidebar it would leave a 44px panel with a workspace name in it. The min-width floor keeps the switcher usable at every width rather than hiding it when collapsed — switching workspace is exactly what someone clicks that mark for. {% endcomment %}

{% for ws in sidebar_workspaces %} {% endfor %} {% if can_create_workspace %} {% endif %} {% comment %} Studio ends the switcher with a link into the workspace you are in, and the panel is where people look for it: the account menu's Settings row lands on the *account* page, and with no Settings row left in the nav this is the one direct way into the workspace's own settings — and so into the Library. The url is absent for a member without manage_workspace_settings — a row advertising a page somebody is refused at is worse than no row, the same rule NavItem.visible_to follows. {% endcomment %} {% if workspace_settings_url %} {% endif %}

{% else %} {% comment %} No workspaces to list — an anonymous visitor on /ui/, or a user whose memberships have all been archived. The mark and the name without a button or a panel, rather than a control that toggles a state nothing shows. (A user with exactly ONE workspace still gets the panel: the list is truthy, and it carries "New workspace" for anyone allowed to make a second.) {% endcomment %} {% endif %}

{% endif %} {% comment %} One renderer for both sets of rows, so a settings row collapses to a glyph, carries a `title` at 60px and lights up by the same `active` the sidebar has always used — the settings column had its own markup for all three. `aria-label` follows the rows rather than staying "Main": with the product's nav not on the page, calling this one "Main" would announce a list that is not there. {% endcomment %}

{% if settings_groups %} {% include "partials/_sidebar_items.html" with groups=settings_groups %} {% comment %} The bell, pinned below the settings rows rather than listed among them: it is not a settings destination, it is the product's one unread indicator, and it has to be on every page or the count it carries is only true on some of them. Rendered straight from its own row — the same dict partials/_sidebar_items.html would hand it — so the label, the count and the `active` flag have one source. {% endcomment %} {% if notifications_row %} {% endif %} {% else %} {% include "partials/_sidebar_items.html" with groups=nav_groups %} {% comment %} The workspace's channels, and the ones it could connect next. Inside this nav rather than below it so the rows collapse with every other row at 60px, and so one scroll container holds everything that can grow — a workspace with six connections and a long flow list scrolls once, not twice. {% endcomment %} {% include "partials/_sidebar_channels.html" %} {% endif %}

{% comment %} The footer carries no nav rows. It held two — Library and Settings — until Settings left the sidebar (the account menu below and the workspace switcher above both lead there) and Library moved into the workspace settings nav, beside the rest of the workspace's setup. What is left is who you are and the collapse toggle. {% endcomment %}

{% if request.user.is_authenticated %} {% comment %} The account block is not a NavItem: it has no glyph and no route, it is a menu trigger. Rendered straight from request.user so no CSS class or display string is ever built in Python — see test_no_python_file_emits_a_class_attribute. Its two halves are swapped by CSS, not by x-show. Studio uses x-show here and pays for it with two x-cloak flashes and an element whose visibility depends on an inline `display:none` that Alpine has to clear — the exact shape test_no_element_combines_x_show_with_a_display_none_utility exists to catch. The collapsed rules are already written twice for the pre-paint mirror; these two are just two more. {% endcomment %}

{% comment %} Studio's organisation menu: the email, the organisation under it, one framed way into the team, then the two rows that were already here. It is stretched across the footer rather than given a width, so it lines up with the account button that opens it; the rail state has no content box to stretch across and is handled in styles.css. Signing out stays a POST. Studio's is an to /accounts/logout/, which is a GET that changes state — one prefetch or one crawler and the session is gone. The row is a submit button styled as a row rather than a link that looks like one. {% endcomment %}

{% if members_url %} {% endif %}

{% comment %} Named for where it lands, not for what it is: this row opens the settings shell on your profile, and the shell's Organisation group is the rest of what is behind it. It read "Settings" while there was a second one beside it in the switcher; "Organization Settings" is what tells the two apart from the account menu. {% endcomment %}

{% if logout_url %} {% endif %}

{% endif %}