parts before the app's name. The title is built here and only here, "{part} · {part} · Docs", so no handler can drift from the suite's separator. <meta charset> comes first, before anything that could be read as text. The stylesheets are in the suite's fixed order: tokens, theme, brand, then estilo's base, menu and chrome, then the page's own. */}} {{define "layout"}}<!doctype html> <html lang="en" dir="ltr"{{with .Frame.Theme}} data-theme="{{.}}"{{end}}> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>{{range .Frame.TitleParts}}{{.}}

. It replaces rastrillo's topbar shell, whose

hard-codes an "Account" summary and a tail that wraps, neither of which estilo may restyle (estilo's CSS may not select rastrillo's markup). Every page's data carries a Frame (chrome.go): the bar, and the parts before the app's name. The title is built here and only here, "{part} · {part} · Docs", so no handler can drift from the suite's separator. <meta charset> comes first, before anything that could be read as text. The stylesheets are in the suite's fixed order: tokens, theme, brand, then estilo's base, menu and chrome, then the page's own. */}} {{define "layout"}}<!doctype html> <html lang="en" dir="ltr"{{with .Frame.Theme}} data-theme="{{.}}"{{end}}> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>{{range .Frame.TitleParts}}{{.}} · {{end}}{{.Frame.Chrome.App.Name}} {{template "head" .}} {{iconAssets}}