Add dbt State webinar page banner (GTM-1034590) - #9849
Merged
Conversation
Promote the dbt State technical deep dive webinar (Sept 1 & 2) on the dbt State docs pages. The global announcement bar stays on the dbt Summit promo, so this is scoped to the 12 dbt State pages the docs team picked: the dbt-state-about category and everything nested under it, the billing usage page, and the reference configs page. Banner path matching is exact pathname equality, so the nested pages are enumerated individually. Versioning is a client-side query param and never changes the pathname, so the ?version=2 URLs in the ticket need no special handling. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The dbt Wizard webinar it promotes was July 22nd, nearly a month ago. Page banners have no expiry mechanism, so stale entries keep rendering until removed by hand. The 15 dbt Wizard/AI pages now fall back to the global dbt Summit announcement bar. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
john-rock
approved these changes
Aug 19, 2026
john-rock
left a comment
Contributor
There was a problem hiding this comment.
Confirmed specific routes show the state banner and others show the dbt Summit banner.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a page-specific promo banner for the dbt State technical deep dive webinar (Sept 1 & 2) to the dbt State docs pages, per GTM-1034590.
The global announcement bar stays on the dbt Summit promo. This banner replaces it only on the 12 dbt State pages the docs team identified.
Banner copy follows the format of the previous page banner:
Preview links
Expect the dbt State webinar banner (not the dbt Summit bar) on all 12:
Expect the global dbt Summit bar (control pages — confirms no over-matching, and that the expired Wizard banner removal landed):
Also worth a click: dbt-state-usage?version=2 — confirms the version query param doesn't break banner matching.
Commits
website/page-banners.yml. No component, plugin, or CSS changes.Notes
?version=2URLs in the ticket need no special handling.&intext(injected viadangerouslySetInnerHTML) but a bare&inlink(React escapeshrefattributes) is intentional, not an inconsistency.Verification
Checked the server-rendered HTML on the preview deploy above — all 14 pages return 200, and the banner is present in the static markup rather than swapped in client-side:
[page-banners] No page found for banner pathwarnings from the build plugin — every configured path resolves to a real page.Follow-up (not in this PR)
Page banners have no expiry mechanism — no
start_date/end_dateinbuildPageBanners. Entries render until someone deletes them by hand and the site rebuilds, which is how the Wizard banner outlived its webinar by a month. This banner will need manual removal after Sept 2. Adding date support to the plugin would prevent the recurrence; worth its own ticket.🤖 Generated with Claude Code