and left UNSTYLED — plain black text with a transparent bg that overlaps the first line of code. We turn it into a clean header strip (language tag left, ghost copy button right) and pad the code body so the first line clears the header. Marker: sf-code-toolbar-2026-05-18 */ #articleContent .code-toolbar { position: relative; } /* Reserve room at the top of the code body for the header strip */ #articleContent .code-toolbar > pre { padding-top: 46px !important; } /* Header strip across the top of the code block */ #articleContent .code-toolbar > .toolbar { position: absolute; top: 0; left: 0; right: 0; height: 38px; display: flex; align-items: center; justify-content: space-between; gap: var(--sf-space-3); padding: 0 10px 0 var(--sf-space-5); margin: 0; border-bottom: 1px solid var(--sf-border); border-radius: var(--sf-radius-lg) var(--sf-radius-lg) 0 0; background: rgba(0, 0, 0, 0.02); } #articleContent .code-toolbar > .toolbar .toolbar-item { display: inline-flex; align-items: center; } /* Language label — small uppercase muted tag (left) */ #articleContent .code-toolbar > .toolbar .toolbar-item:first-child span { font-family: var(--sf-font-body); font-size: 11px; font-weight: 600; letter-spacing: 0.06em; text-transform: uppercase; color: var(--sf-text-muted); } /* sr-only language span is duplicated by Prism for a11y — keep it hidden */ #articleContent .code-toolbar > span.sr-only { position: absolute !important; width: 1px; height: 1px; padding: 0; margin: -1px; overflow: hidden; clip: rect(0 0 0 0); white-space: nowrap; border: 0; } /* Copy button — ghost button (right). Doc360 ships an icon as an absolutely-positioned ::before at left:-15px (escapes the button) + an inner forced to 16px uppercase. We lay the button out as inline-flex, pull the icon back inline as a masked clipboard glyph that tints with text color, and normalise the span. */ #articleContent .code-toolbar > .toolbar .copy-to-clipboard-button { display: inline-flex !important; align-items: center !important; justify-content: center !important; gap: 6px !important; font-family: var(--sf-font-body) !important; font-size: 12px !important; font-weight: 500 !important; line-height: 1 !important; color: var(--sf-text-muted) !important; background: var(--sf-surface) !important; border: 1px solid var(--sf-border) !important; border-radius: var(--sf-radius-sm) !important; padding: 5px 12px !important; cursor: pointer; box-shadow: none !important; transition: color 150ms ease, border-color 150ms ease, background 150ms ease; } /* Replace Doc360's stray absolute icon with an inline masked clipboard glyph */ #articleContent .code-toolbar > .toolbar .copy-to-clipboard-button::before { content: "" !important; position: static !important; top: auto !important; left: auto !important; display: inline-block !important; width: 13px !important; height: 13px !important; flex-shrink: 0; background: currentColor !important; -webkit-mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Crect width='14' height='14' x='8' y='8' rx='2' ry='2'/%3E%3Cpath d='M4 16c-1.1 0-2-.9-2-2V4c0-1.1.9-2 2-2h10c1.1 0 2 .9 2 2'/%3E%3C/svg%3E") center / contain no-repeat; mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Crect width='14' height='14' x='8' y='8' rx='2' ry='2'/%3E%3Cpath d='M4 16c-1.1 0-2-.9-2-2V4c0-1.1.9-2 2-2h10c1.1 0 2 .9 2 2'/%3E%3C/svg%3E") center / contain no-repeat; } /* Normalise the inner span (Doc360 forces 16px uppercase on it) */ #articleContent .code-toolbar > .toolbar .copy-to-clipboard-button span { font-size: 12px !important; font-weight: 500 !important; line-height: 1 !important; text-transform: none !important; color: inherit !important; } #articleContent .code-toolbar > .toolbar .copy-to-clipboard-button:hover { color: var(--sf-brand-600) !important; border-color: var(--sf-brand-600) !important; background: var(--sf-brand-50) !important; } /* Dark mode */ [data-bs-theme="dark"] #articleContent .code-toolbar > .toolbar { border-bottom-color: #3a3d44; background: rgba(255, 255, 255, 0.03); } [data-bs-theme="dark"] #articleContent .code-toolbar > .toolbar .copy-to-clipboard-button { color: #a1a1aa !important; background: #27292f !important; border-color: #3a3d44 !important; } [data-bs-theme="dark"] #articleContent .code-toolbar > .toolbar .copy-to-clipboard-button:hover { color: var(--sf-brand-600) !important; border-color: var(--sf-brand-600) !important; background: rgba(0, 67, 243, 0.12) !important; } /* --- 5.3 Tables --- Single canonical style. Retires the 2 conflicting table blocks in current_css.md (lines 240-265 "premium" rounded-soft, and lines 596-638 with #256bff header + heavy shadow + alternating #fafcff / #f4f7fc rows). Uses Doc360's documented selectors (table th, table td, tbody tr:nth-child(odd)) to maximise stability across template updates. Scoped to article-content to avoid bleeding into landing page block patterns which use their own grid markup. */ #articleContent table { width: 100%; border-collapse: separate; border-spacing: 0; border: 1px solid var(--sf-border); border-radius: var(--sf-radius-lg); overflow: hidden; margin: var(--sf-space-4) 0 var(--sf-space-5); box-shadow: var(--sf-shadow-sm); /* Inter ships proportional figures by default — tables need consistent digit width so columns of numbers align visually. */ font-variant-numeric: tabular-nums; } #articleContent table th { font-family: var(--sf-font-heading); font-weight: 600; text-align: left; background: var(--sf-brand-50); color: var(--sf-text-primary); padding: var(--sf-space-3) var(--sf-space-4); border-bottom: 1px solid var(--sf-border); } #articleContent table td { padding: var(--sf-space-3) var(--sf-space-4); border-bottom: 1px solid var(--sf-border); vertical-align: top; } #articleContent table tbody tr:nth-child(odd) td { background: var(--sf-surface-page); } #articleContent table tbody tr:last-child td { border-bottom: none; } /* --- 5.4 Blockquotes --- Migrated from current_css.md lines 294-301. Stripe-style — soft bg, left border in muted grey (NOT brand color; we reserve brand for action affordances). */ #articleContent blockquote { margin: var(--sf-space-4) 0 var(--sf-space-5); padding: var(--sf-space-3) var(--sf-space-4); border-left: 3px solid rgba(0, 0, 0, 0.22); background: rgba(0, 0, 0, 0.03); border-radius: var(--sf-radius-md); color: var(--sf-text-body); } #articleContent blockquote p:last-child { margin-bottom: 0; } /* --- 5.5 Article images — canonical B2B docs pattern (Phase 3.4, 2026-05-17) --- Aligned with Vercel docs (MCP-verified 2026-05-17): 1px border + 8px radius + 32px vertical margin + NO box-shadow. Vercel applies their 40px margin on a

wrapper, but Doc360 KB 2.0 doesn't wrap inline images in

— every audited image sits inside

. So we apply the margin directly to . Scalefusion-specific rationale: screenshots are mostly white-bg MDM console UI on a #ffffff article surface — the 1px border is the only thing framing them cleanly without decorative weight. Scope-tightening pass 2026-05-17 (after Phase 4 products section icon bug): Previous selector was `article img` which matched ANY inside ANY

element, including landing-page Custom code sections that use

for product cards / video tiles. Switched to `site-docs-content-panel-container img` — Doc360 KB 2.0's article-body wrapper, MCP-verified to contain article body images exclusively (no header/footer/sidebar/landing chrome). `#articleContent` retained for KB 1.0 back-compat. `.content_block .content_container .content_block_text img` retained for legacy markup (rarely seen). Marker: sf-images-canonical-2026-05-17 (rev 2 = scope-tightened) */ #articleContent img, site-docs-content-panel-container img, .content_block .content_container .content_block_text img { max-width: 100%; height: auto; border-radius: var(--sf-radius-md); /* 8px — was --sf-radius-lg (12px) */ border: 1px solid var(--sf-border-image); /* darker #d1d5db — frames white-bg screenshots */ margin: var(--sf-space-6) 0; /* 32px vertical breathing room */ display: block; } /* Image alignment helpers (Doc360 documented pattern) — preserved + margin retokenised to match the base rule. */ #articleContent img.center, site-docs-content-panel-container img.center { margin: var(--sf-space-6) auto; } #articleContent img.right, site-docs-content-panel-container img.right { margin: var(--sf-space-6) 0 var(--sf-space-6) auto; } /* --- 5.5b Article image viewport-relative height cap (Phase 3.4, 2026-05-17) --- Caps image height at 80% of the viewport. Live audit (2026-05-17): 6 of 20 images on the OKTA article exceed 75% of viewport height on a 1080×713 laptop; the tallest portrait screenshot is 888px (literally larger than the viewport). Without this cap, long step-by-step articles bury reader context in scroll. 80vh is responsive — large monitors get full-size images, small screens get scroll relief. Trade-off: capping can shrink admin-UI details. Acceptable until JS-based click-to-zoom lands in Phase 6 (out of v1 scope). Kept in its own section so it can be toggled off independently of the base image styling if editorial pushes back. Marker: sf-images-viewport-cap-2026-05-17 */ #articleContent img, site-docs-content-panel-container img, .content_block .content_container .content_block_text img { max-height: 80vh; } /* --- 5.6 Cards --- Migrated from current_css.md lines 351-366. Shared by landing OS/feature tiles + category sub-category cards. Hover lifts subtly via shadow + translate; the colors and radius come from tokens. */ .category-card, .kb-category-card { border: 1px solid var(--sf-border) !important; border-radius: var(--sf-radius-lg) !important; background: var(--sf-surface) !important; transition: transform 180ms ease, box-shadow 180ms ease, border-color 180ms ease; } .category-card:hover, .kb-category-card:hover { transform: translateY(-2px); box-shadow: var(--sf-shadow-lg); border-color: var(--sf-border); } /* --- 5.7 Sidebar (Doc360 "Category navigation") — Phase 2.A density refresh --- KB 2.0 selectors (site-docs-left-panel-container) are primary; .left_sidebar kept as KB 1.0 fallback. Density goals: 14px uniform nav font, 320px panel width, 4/10 padding on items. Phase 2.A.2 rebalance: left widened 260→320 to match a tightened right TOC rail (see 5.7b) and give the article body a comfortable ~85ch measure at 17px body. */ /* Panel container — Doc360 wraps panel in a flex parent that stretches it. Doc360's COLLAPSE TOGGLE mechanism uses inline `style` on the panel: Expanded: style="min-width: 250px; ..." Collapsed: style="min-width: 56px; width: 0px; flex: 0 1 0%; ..." Our `!important` width pinning beats both inline styles unless scoped. Use [style*="min-width: 250px"] so our pinning only applies in the EXPANDED state — in collapsed state, Doc360's inline width:0/flex:0 1 0% wins. Visual styling (border-right, background) is left UNSCOPED so it still renders cleanly during the expand→collapse transition. Bug fix 2026-05-17 (was breaking the left-panel collapse toggle). */ site-docs-left-panel-container[style*="min-width: 250px"], .left_sidebar { width: 320px !important; min-width: 320px !important; max-width: 320px !important; flex: 0 0 320px !important; } /* Visual chrome — applies in both expanded and collapsed states (background is invisible at width: 0 anyway). */ site-docs-left-panel-container, .left_sidebar { border-right: 1px solid var(--sf-border) !important; background: var(--sf-surface) !important; } site-docs-left-panel-container .left-panel, site-docs-left-panel-container .docs-left-panel, .left_sidebar { padding-top: var(--sf-space-3) !important; } /* All nav text — uniform 14px, 1.4 line-height */ site-docs-left-panel-container a, site-docs-left-panel-container button, .left_sidebar a { font-size: var(--sf-text-small) !important; line-height: 1.4 !important; } /* Nav links (leaf articles + category landing links) */ site-docs-left-panel-container a, .left_sidebar a { font-family: var(--sf-font-body) !important; font-weight: 500 !important; color: var(--sf-text-primary) !important; text-decoration: none !important; padding: var(--sf-space-1) var(--sf-space-3) !important; display: block !important; border-radius: var(--sf-radius-md); transition: background-color 120ms ease; } site-docs-left-panel-container a:hover, .left_sidebar a:hover { background: rgba(0, 0, 0, 0.045) !important; text-decoration: none !important; } /* Active / current-page item — strongest visual signal, always wins. Doc360 puts the 'active' class on a wrapper

, NOT on the itself. We highlight the wrapper, and also colour the link inside. */ .node.tree-wrapper.active, .node.active { background: var(--sf-brand-50) !important; border-radius: var(--sf-radius-md) !important; } .node.tree-wrapper.active a, .node.tree-wrapper.active .data-title, .node.active a, .node.active .data-title, site-docs-left-panel-container a[aria-current="page"], .left_sidebar a.active { color: var(--sf-brand-600) !important; font-weight: 600 !important; } /* === Hierarchy by font WEIGHT (depth-based ladder, 2026-05-17) === Doc360 renders the nav tree FLAT in DOM via Angular CDK virtual scroll — nothing is nested in

. Depth is conveyed instead by a count of `
` direct-child spacers inside each `.node.tree-wrapper`: 0 fillers = depth 0 (top-level category, e.g. "Windows Device Management") 1 filler = depth 1 (sub-category folder, e.g. "Identity Providers") 2+ fillers = depth 2+ (leaf article, e.g. "Configuring OKTA as ...") Weight ladder: top 600 → sub 500 (inherited default above) → leaf 400. Active leaf jumps back to 600 (rule lives further down, after this). Size stays uniform 14px — weight alone does the hierarchy work. Note: replaces the dead `button[aria-label*="section" i] + a` rule from Phase 2.A — that selector never matched because Doc360's chevron is a `
`, not a real `

Documentation Index

OS Update & Third Party App Patch Management