tr
TryGhost
GitHub
Ghost
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
Ghost
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
30318
576c9dc5 Moved application styles out of the Shade stylesheet no ref Shade's stylesheet carried admin-app concerns that every consumer paid for. The 21 fonts.bunny.net imports serving the settings font pickers loaded on every admin page; they now live in an admin-owned settings/custom-fonts.css imported by the two picker screens, so the fetches ship with the lazily loaded settings chunk instead of the entry CSS (entry drops from 319,977 to 318,348 bytes and no longer touches bunny.net). The font-* utilities those pickers use must still be generated in Admin's single Tailwind lane, so the family @theme variables moved to admin's index.css rather than the lazy file; first open of a picker can now show a brief FOUT while the families fetch. The .gh-prose-links and dark-mode .gh-loading-orb rules and the members-sticky-hover-bg variable were admin-only: the rules moved to admin's index.css, and the variable — an alias of table-row-hover in both themes — was replaced at its single consumer with the table-row-hover token. The unused setting-highlight-fade-out animation token was removed outright. The .dark .shade base color swapped its #fafafb literal for the foreground token. Before/after screenshots show no visible change: every dark-mode surface already sets explicit color tokens, and the inherited fallback now matches text-primary instead of sitting slightly brighter than it.
by Steve Larson
S
Previous
Next