docs: add A2A & generative UI hackathon banner#1906
Conversation
Add an announcement banner promoting the A2A and generative UI hackathon in London on Saturday 13th June, linking to the Luma signup page. The existing DeepLearning.AI course banner is commented out for now and can be uncommented after the hackathon to restore it. Scope the supporting CSS to a new `.md-banner__hackathon` class with `:has()` so the layout (right-aligned compact button, vertically-centered dismiss icon) only applies while the hackathon paragraph is present. When the hackathon banner is later removed, the styles become inert and the restored course banner renders with its original default Material appearance. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
There was a problem hiding this comment.
Code Review
This pull request replaces the DeepLearning.AI course announcement banner with a new banner promoting the "A2A and generative UI hackathon" in London, along with corresponding CSS updates for layout and responsiveness. The reviewer suggested several improvements: adding flex-wrap: wrap and flex-shrink: 0 to the CSS to prevent layout overflow on smaller screens, adding target="_blank" and rel="noopener" to the external Luma link to open it in a new tab, and using Jinja2 comments ({# ... #}) instead of HTML comments to completely omit the commented-out block from the rendered output.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
- Add `luma` (from luma.com URL) to spell-check expect list. - Disable stylelint `selector-class-pattern` around the announcement rules, since Material's banner classes use BEM `__` selectors that the rule rejects. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Note on the failing Check linked issues check: there's no existing issue tracking this hackathon announcement, so I haven't linked one. The workflow allows bypassing via the (The spelling and Lint Code Base failures are addressed in the follow-up commit |
Drop the `.md-banner__hackathon` scope so the layout applies to any future announcement, not just the hackathon one. The commented-out course banner is updated to follow the same `<p>` + `<span>` markup convention so it can be uncommented later without further changes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Summary
Add an announcement banner promoting the A2A and generative UI hackathon in London on Saturday 13th June, linking to the Luma signup page.
The existing DeepLearning.AI course banner is commented out for now so a single, focused announcement is shown for the next 10 days. After the hackathon, removing the hackathon
<p>and uncommenting the original course banner restores the previous state exactly — see "Future state" below.Changes
Only two files are touched:
.mkdocs/overrides/main.html— add a new<p class="md-banner__hackathon">for the hackathon announcement; comment out the previous course-banner content.docs/stylesheets/custom.css— replace the previously dead.announce .md-buttonrule with a:has(.md-banner__hackathon)-scoped layout that right-aligns the announcement button (with smaller padding) and vertically centers the dismiss icon.Before / After
Before (current production banner)
After (this PR)
Future state (after the hackathon)
The CSS is scoped via
:has(.md-banner__hackathon), so when the hackathon paragraph is later removed and the course banner is uncommented, all custom styling becomes inert and the course banner renders exactly as it did before this PR (default Material styling, big inline "Enroll for free" button, ✕ floated top-right). Verified locally by reverting the template to its pre-PR contents — the page rendered identically to the current production site.Dismiss behaviour
Material's
announce.dismisskeys dismissal off a hash of the announce block's HTML, so users who previously dismissed the course banner will still see the new hackathon banner (different content → different hash → different dismissal state). The same applies when the course banner is reinstated after the hackathon.Test plan
./scripts/build_docs.sh— no warnings introduced.mkdocs serveand verify the hackathon banner renders with the button right-aligned, vertically centered, and the ✕ vertically centered with a small gap (see "After" screenshot)..mkdocs/overrides/main.htmlto its pre-PR contents; confirm the page renders identically to the current production site (default Material banner styling).custom.csschanges don't affect any other.md-buttonon the site — the new selectors are all scoped under.md-banner__inner:has(.md-banner__hackathon)/.md-banner__hackathon.