Core brand edition 3.0.0 · Updated September 18, 2026 (Hawaii time)
Current public website profile
Navy and royal blue hold the experience together. Gold guides the next action. Large sentence-case typography, fine borders, clear controls, and full-width media give the site its product feel. This is a composition example, not a new campaign headline.
About precedes featured media on the homepage. Editorial sand gives that explanation a warm reading surface. Photo and video carry the people, technology, and energy of the week.
Use it for community, nature, and selected active states. Keep primary actions gold and the footer navy. White remains useful for forms, tools, and report reading areas. Solar Cream (#FFFAEC) remains an existing utility; it is distinct from the editorial sand shown here.
HTW Navy#04153D · Canvas
Royal Navy#002868 · Depth
Royal Gold#FFB81C · Actions
Royal Green#1B7A5A · Nature
Soft green#B9D8B0 · Accents
Blue highlight#91B8EC · Headings
Muted blue#B7C6DF · Body text
Editorial sand#F2EEE3 · About
King David Kalakaua (1836-1891), known as the "Merrie Monarch," was Hawaii's last king and a champion of Hawaiian culture, arts, and modernization. His royal standard featured the colors of Hawaiian royalty:
By anchoring HTW's brand in these royal colors, we honor Hawaii's heritage while symbolizing the innovation and forward-thinking spirit that defined Kalakaua's reign — the perfect metaphor for "Where Tech Meets Hawaii."
Core brand palette built on Hawaiian heritage. HTW Navy is THE primary (matches logo). The four secondaries each play distinct roles.
Each status has a Dark variant (solid, for icons and borders) and a Light variant (tinted background for banners and toasts).
In use — status banners combine Light background + Dark border/text:
Three accent families, each with a light-mode and dark-mode variant shown side by side. Coral is the same in both modes.
Event category badge colors for the Calendar page, derived from HTW tokens.
Backgrounds, surfaces, text, and borders for both light and dark modes.
Retained brand gradient recipe. Current public pages also use quieter navy overlays and green-to-navy community bands; this gradient is not required on every hero.
Brand colors (use independently): The 4 royal heritage colors (Navy, Gold, Red, Green) + Neon Cyan.
Gradient-only colors: #0052A3, #5B9FD8, #93C5FD only exist as intermediate stops in Ocean Sunrise. Do not use them as standalone brand colors.
Ocean Sunrise gradient with Royal Gold CTA button in hero context.
A week of independently hosted events connecting people across Hawaii’s tech community. Verify current dates and participation details before adding them to campaign artwork.
Get updatesGradient opacity can be adjusted per use case when overlaying photos or video.
Use Inter for headings and body. The current public profile uses sentence case and weights 500–600, with large responsive headings. The utility examples below are retained for existing components and reading surfaces, not a universal public-page scale.
This utility is available for paragraph text on light reading surfaces. The public navy profile uses muted blue body text and its shared CSS spacing.
Small body text used for captions, metadata, and fine print. Still maintains good readability while being more compact.
Section intro text appears directly below H2 headings to provide additional context. Slightly larger than body text for emphasis.
Extra large section intro for "pop" sections that need extra prominence, like the homepage About section.
"This style is used for testimonials and pull quotes. The italic styling differentiates it from regular body text."
Current public bands use a clamp(24px, 4.5vw, 88px) horizontal gutter and a 1760px maximum interior container, with typical 72px desktop / 48px mobile section spacing. The contained UI recipes below remain available for reading areas and existing components.
Site-wide defaults for card geometry, image behavior, card structure, and CTA placement. Use these standards before creating new card variants or refactoring homepage cards.
| Card Type | Ratio | Usage |
|---|---|---|
| Speaker / profile cards | 4 / 5 |
Best default for headshots, speakers, portraits, and people cards. |
| Vertical media / reels | 9 / 16 |
Use for short-form video, story-style content, social previews, and reel previews. |
| Event cards | 3 / 2 |
Best default for standard event, article, venue, and content cards. |
| Video thumbnails | 16 / 9 |
Use for YouTube-style videos, recordings, recap videos, and cinematic media. |
| Venue / editorial photo cards | 3 / 2 |
Good default for polished editorial image cards. |
| Resource / compact cards | 4 / 3 |
Useful when cards need more height than 16:9 but less than vertical. |
| Sponsor / logo cards | fixed height, 2 / 1, or 3 / 1 |
Use logo-safe containers, not aggressive image crops. |
| Banner / feature strips | 2 / 1 or 21 / 9 |
Use for wide featured cards, announcement strips, and hero-style cards. |
All card images should use a fixed aspect-ratio container with width: 100% and object-fit: cover.
Use aspect utilities by card type. Do not casually mix ratios inside the same grid or section.
Cards should generally use a vertical flex layout so CTAs align consistently, even when card text lengths differ.
Use this structure for new cards unless a component has a documented reason to differ.
Mobile CTAs should be full-width for tap comfort. Desktop CTAs should be compact and content-sized unless the card is a dedicated CTA block.
Buttons do not scale proportionally with card size. Button dimensions come from button tokens.
--button-height-sm: 40px--button-height-md: 44px--button-height-lg: 48px--button-padding-x-sm: 14px--button-padding-x-md: 20px--button-padding-x-lg: 24px| Card Type | CTA Recommendation |
|---|---|
| Featured event card | Use a real button: Register, Get tickets, or View event. |
| Regular event card | Use compact button or subtle text CTA. |
| Mobile event card | Use a full-width button if registration is the main action. |
| Speaker card | Usually make the whole card clickable; no visible button needed. |
| Sponsor card | Usually no button; optional subtle Learn more →. |
| Blog / article card | Use a text CTA: Read more →. |
| Video card | Use a text CTA or play affordance: Watch recap →. |
| Host / sponsor CTA card | Use a strong full-width or prominent button. |
Use whole-card click behavior for lower-intent browsing surfaces such as speaker cards, blog cards, venue cards, video cards, and general event detail cards.
Use a real button for Register, Buy tickets, Apply, Submit event, Sponsor, and Join actions.
Use View details →, Learn more →, Meet speaker →, Read more →, and Watch recap → when the action is secondary.
4 / 5 for people and speaker cards.3 / 2 as the default for event, venue, article, and editorial cards.16 / 9 for video and cinematic media cards.Earlier homepage component explorations retained as a reference library. They are not the current homepage composition. Use the public profile above for the approved full-width direction; reuse an older recipe only when it fits a specific component’s job.
Earlier manual featured-event card families retained for comparison. Keep multiple viable layouts in play for different jobs: HTW anchor events, sponsor-hosted featured events, and fallback states. Color treatments are subvariants; layout and content budget should be evaluated on their own merits.
Start with the full field set, then remove or relocate fields based on the card surface, image contrast, and available space. Variants can have different spacing, but they should preserve the same decision hierarchy.
Host should be visible as recognition, not buried in clipped logistics. It can sit under the title, above the description, or as the lead detail line depending on card family.
Hawaii Tech Week
Hawaii Tech Week
The high-energy social anchor for the full Hawaii Tech Week community.
Hawaii Tech Week
Hawaii Tech Week
A curated leadership gathering across tech, capital, industry, and government.
Hawaii Tech Week
The current homepage About card is a single-card carousel. Earlier treatments are preserved here because they are useful references for readability, card density, and image dominance.
Meet founders, builders, investors, executives, and more from Hawaii and beyond.
Learn from experts across fields, from AI and aerospace to leadership and capital.
Recruit talent, deepen partnerships, unlock capital, and launch new initiatives.
Image-led cards used to show the distributed formats of the week. These should remain quiet, scannable, and mostly visual.
Final CTA cards. These are image-led action cards with button-only visible copy, so the CTA area must stay legible and visually consistent with primary and secondary button rules.
Visual preview of the reusable speaker card system driven by `components.speaker-card` tokens.
Retained card proportions for component recipes. Keep ratios consistent within a deck. Current full-width bands and speaker image-plus-copy cards follow their approved shared public components.
Production component: src/components/TestimonialCard.tsx. Used on the homepage carousel, host landing page, and future proof sections. The quote is required; avatar, company logo, name, title, and company are optional without breaking card dimensions.
/dev/testimonial-cards (dev only).
Homepage carousel uses the same card in a horizontal scroll rail.
Production samples plus edge cases: quote-only, missing assets, and long quote overflow.
Elevation system using box shadows to create visual hierarchy and depth. Use sparingly for best effect.
Consistent corner radii for buttons, cards, and containers.
Smooth, performant transitions that enhance UX without overwhelming. All animations respect prefers-reduced-motion.
Responsive breakpoints matching Tailwind's default system. Mobile-first approach.
Standardized z-index values to manage layering and avoid conflicts.
Version 3.0.0 token reference from docs/design-tokens.json. The additive publicSite profile documents current public composition; established UI and component keys remain available. The embedded offline fallback matches this edition.