Skip to content

Webpage UI: Homepage #2125

@henryajisegiri

Description

@henryajisegiri

Overview

All section components have already been built. This ticket covers assembling them into the homepage layout, wiring up data/props, and ensuring correct spacing, ordering, and responsive behaviour across all three breakpoints.

Figma Links


Background

The following components exist and are ready to use:

Component Description
NavBar Logo, nav links, search (CTRL+K), theme toggle, log in
HeroSection Headline, primary + secondary CTAs
InstallPanel Tab switcher, code block, package manager dropdown
SearchBlock Search input + popular term pills
EventList / EventCard Upcoming events with dates and CTAs
CommunityPostCard Post title, date, tags, author avatar + badge
CodeSnippetBlock Syntax-highlighted C++ example
CommunityJoinCard Yellow card with 4 action rows + CTA button
FeatureGrid "Why Boost?" tiles
BarChart Version history chart
TestimonialCarousel Pull quote + author + navigation arrows
ContributorList Avatar, name, role badge, short bio
Footer Nav links + social icons

Props / Data Wiring

Each component should receive real data via props, however, use mock data for the implementation

  • CommunityPostCard — map over post data array (title, date, tags, author)
  • EventCard — map over events array (title, description, date)
  • ContributorList — map over contributors array (name, role, bio, avatar)
  • TestimonialCarousel — pass testimonials array + handle prev/next state
  • BarChart — pass version labels + download count data

Acceptance Criteria

  • All components render in the correct order per breakpoint, as defined in the Figma designs
  • Footer layout adapts correctly across all breakpoints
  • No layout overflow or clipping at 320px, 768px, 1280px, 1440px
  • All props wired with mock data
  • Tested in Chrome, Safari, Firefox
  • All components function as implemented individually; cards within card blocks and buttons are clickable
  • Light and dark mode render correctly for all components

Out of Scope

  • Building or modifying individual components (separate tickets)
  • Live data fetching — use mock data for now

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions