Skip to content

Add Kagenti → Rosso rebrand announcement banner#83

Merged
mrsabath merged 1 commit into
kagenti:mainfrom
Ibrahim2595:add-rosso-rebrand-banner
Jun 12, 2026
Merged

Add Kagenti → Rosso rebrand announcement banner#83
mrsabath merged 1 commit into
kagenti:mainfrom
Ibrahim2595:add-rosso-rebrand-banner

Conversation

@Ibrahim2595

Copy link
Copy Markdown
Contributor

Summary

Adds a dismissible announcement banner at the top of the landing page noting the upcoming Kagenti → Rosso rename:

NEW NAME — Kagenti is becoming Rosso — you'll see the new name reflected across all project sites soon.

It's styled as a light red-tinted bar with a brand-red accent and a NEW NAME pill, so it reads as a distinct announcement rather than blending into the existing dark event banner. The KubeCon event banner is hidden (markup kept, just hidden class added) so the rebrand message stands alone.

Changes

  • index.html — new #rebrand-banner; hide the KubeCon #event-banner
  • style.css.banner-rebrand + .rebrand-pill styles (AA-compliant contrast)
  • script.js — independent dismiss handler with session-storage persistence, mirroring the existing event-banner pattern

Notes

  • Reuses the existing .banner system — no new patterns introduced.
  • The event banner is only hidden, not deleted, so it's trivial to restore.

🤖 Generated with Claude Code

Add a dismissible announcement banner at the top of the landing page
noting the upcoming Kagenti → Rosso rename. Styled as a light red-tinted
bar with a "NEW NAME" pill and a brand-red accent so it reads as a
distinct announcement, separate from the (now hidden) event banner.

- index.html: new #rebrand-banner; hide the KubeCon event banner
- style.css: .banner-rebrand + .rebrand-pill styles
- script.js: independent dismiss + session-storage persistence

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: IBRAHIM IBRAHIM <66755652+Ibrahim2595@users.noreply.github.com>
@Ibrahim2595 Ibrahim2595 force-pushed the add-rosso-rebrand-banner branch from 3cffa27 to 3b13af7 Compare June 12, 2026 17:42

@mrsabath mrsabath left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Summary

Clean, well-scoped frontend change. The new #rebrand-banner reuses the existing .banner system, dismissRebrandBanner() mirrors the established dismiss pattern with session-storage persistence, the close button has a proper aria-label, and the styling notes AA contrast. No new patterns introduced, no secrets, and the KubeCon banner is hidden rather than deleted so it's trivial to restore.

On the rebrand content: I flagged during review that the "Kagenti → Rosso" announcement has no linkable authorization anywhere in the org (no issue, PR, discussion, or repo references "Rosso"). The maintainer has confirmed out-of-band that the rename is sanctioned, so approving on that basis. Recommend linking the official rebrand announcement/decision in the PR description before merge so the public-facing claim has a paper trail.

DCO: now passing — commit re-signed with Signed-off-by since the first review pass.

Areas reviewed: Frontend (HTML/CSS/JS), Security, Commit conventions
Author: Ibrahim2595 (MEMBER — maintainer)
Commits: 1, signed-off: yes
CI status: passing (DCO ✓, add-to-project ✓)

Comment thread index.html
</div>
</div>

<div class="banner hidden" id="event-banner">

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

suggestion (non-blocking) — this adds hidden to the live KubeCon #event-banner so the rebrand message stands alone. Just confirming that's intended: KubeCon NA (Nov 9–12) is still upcoming, so you're trading the event promo for the rename notice. The markup is kept (only the class added), so restoring it later is a one-line revert — no concern there. Mentioning only so the event-banner drop is a conscious call, not a side effect.

@mrsabath mrsabath merged commit d28a84d into kagenti:main Jun 12, 2026
1 check passed
@github-project-automation github-project-automation Bot moved this from New /:ToDo to Done in Kagenti Issue Prioritization Jun 12, 2026
@rubambiza

Copy link
Copy Markdown
Contributor

@mrsabath @Ibrahim2595 I know this is already merged, but I wanted to mention that it deviates from our kagenti commit attribution policy (both the commit and PR description). Just wanted to flag for future reference since @Ibrahim2595 was likely not around when the policy was instituted.

@Ibrahim2595

Copy link
Copy Markdown
Contributor Author

@rubambiza Thanks for pointing it out. The work was rushed/urgent and it was my first contribution. I'll make sure to follow the contribution description template in later work.

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

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants