Skip to content

Story: Add support for boostlook v3 and vendor the file#2411

Open
jlchilders11 wants to merge 2 commits into
developfrom
jc/integrate-boostlook-v3
Open

Story: Add support for boostlook v3 and vendor the file#2411
jlchilders11 wants to merge 2 commits into
developfrom
jc/integrate-boostlook-v3

Conversation

@jlchilders11
Copy link
Copy Markdown
Collaborator

Issues: #2399

Summary & Context

Implements boostlook-v3.css in the site, hidden behind a feature flag.

Changes

  • Vendors boostlook-v3.css
  • Serves the v3 boostlook to anyone with the v3 flag set

‼️ Risks & Considerations ‼️

Since we are vendoring this file, if any changes are made upstream we will need to make sure to downstream any changes made. Additionally, this file and flag should be removed during full prod deployment for cleanliness.

Self-review Checklist

  • Link this PR to the related GitHub Project ticket

@jlchilders11 jlchilders11 requested a review from julioest May 7, 2026 16:45
@herzog0 herzog0 linked an issue May 8, 2026 that may be closed by this pull request
Refreshes the vendored stylesheet to pull in the latest
boostlook v3 build. Color tokens are reorganized (neutral
becomes primary, blue becomes secondary), and a few new
palettes show up alongside the new Metalab 2.0 heading and
spacing primitives. Also includes the library README pass:
proper h1 sizing on mobile and desktop, a dark-mode
background, horizontally scrollable tables on small screens,
and tighter literal-block indentation.
@jlchilders11 jlchilders11 requested review from herzog0 and julhoang May 14, 2026 16:25
Copy link
Copy Markdown
Collaborator

@julhoang julhoang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

--
Just one thought from looking at base.html: I understand loading boostlook-v3.css here follows the existing pattern, but at some point it might be worth scoping it to just the /doc template(s) where the boostlook styles are actually used. That would prevent unintentional style leakage and avoid exposing CSS variables and classes we don't want available on V3 pages.

@julhoang
Copy link
Copy Markdown
Collaborator

Also, would you mind rebasing on develop before moving this to QA? The doc page on this branch still shows a duplicate header but develop should already includes a fix for it (from this PR) 😄
Screenshot 2026-05-14 at 12 21 14 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ingest Boostlook 2.0

3 participants