Skip to content

Update color scheme to match BMT brand identity#65

Open
devin-ai-integration[bot] wants to merge 2 commits intomainfrom
devin/1772854845-update-color-scheme
Open

Update color scheme to match BMT brand identity#65
devin-ai-integration[bot] wants to merge 2 commits intomainfrom
devin/1772854845-update-color-scheme

Conversation

@devin-ai-integration
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Mar 7, 2026

Update color scheme to match BMT brand identity

Summary

Replaces off-brand colors (fuchsia, orange, generic blue) with teal/cyan tones derived from the BMT logo gradient (rgb(0,175,230)rgb(89,188,163)). Changes span 4 files — all are Tailwind class swaps with no logic changes. Alert shortcode colors are intentionally left unchanged since they carry semantic meaning (error/info/warning).

Key color mappings:

Element Before After
BmMT 2026 event card fuchsia-700→900 teal-500→700
BmMT Online event card orange-700→900 cyan-500→700
News notifications rose-50/100/200 teal-50/100/200
Blog notifications blue-50/100/200 cyan-50/100/200
Prose links blue-500 cyan-600
Link underline highlight blue-100/200 cyan-100/200
Button links teal-500 teal-600 + hover teal-700
404 gradient teal-400→emerald-300 cyan-500→teal-400
404 shadow emerald-500 teal-600

Unchanged (intentionally):

  • Alert shortcode colors (rose/blue/orange) — these are semantic (error/info/warning) and should not follow brand palette.
  • BMT 2025 China card (slate-200→300) — appropriate for a past/partner event.

Updates since last revision

  • Lightened event card gradients from 700→900 to 500→700 range based on feedback that the dark teal was too heavy
  • Reverted alert shortcode colors to original semantic colors (rose/blue/orange)
  • Adjusted button from teal-700 to teal-600 for a medium, on-brand feel

Local preview screenshots (v2 — lighter event cards, original alert colors):

Homepage with teal news notification:
homepage-v2

Event cards (medium teal + cyan gradients):
events-v2

Event page with cyan links, teal button, and original blue info alert:
event-page-v2

Review & Testing Checklist for Human

  • Event card visual distinction — both cards now use teal/cyan gradients (teal-500→700 vs cyan-500→700). Verify they look distinct enough; previously fuchsia vs orange gave strong contrast between them.
  • News vs blog notification distinction — now teal-50 vs cyan-50, which are visually close. Confirm they're distinguishable or if that's acceptable.
  • Link readabilitycyan-600 on white should meet WCAG AA (~4.5:1 contrast). Verify links are legible and the cyan underline highlights feel right across different pages.
  • Deploy preview — build the site and click through key pages (home, event pages, about, resources, any page with alerts and button_link shortcodes) to verify nothing looks off.

Notes

- Event cards: fuchsia->teal, orange->cyan to match logo gradient
- News notifications: rose->teal tints
- Blog notifications: blue->cyan tints
- Prose links: blue-500->cyan-600 with cyan underline highlights
- Button links: teal-500->teal-700 with hover state
- 404 page: emerald->teal/cyan gradient
- Alert shortcodes: rose->red (error), blue->cyan (info), orange->amber (warning)

Co-Authored-By: liu.andrew <liu.andrew@berkeley.edu>
@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

- Event cards: teal-500→700 and cyan-500→700 (medium, not dark)
- Button: teal-600 with teal-700 hover (medium range)
- Alerts: reverted to original semantic colors (rose/blue/orange)
  since these convey meaning (error/info/warning) independent of brand

Co-Authored-By: liu.andrew <liu.andrew@berkeley.edu>
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.

0 participants