Skip to content

[Frontend]: Replace placeholder pages with data-driven implementations #40

@Hanseooo

Description

@Hanseooo

Priority Area Type

Problem

Core authenticated pages still render placeholder/static states and are not fully connected to backend data/actions.

Context

  • Reference: docs/FUTURE_ISSUES_BACKLOG.md
  • Affected pages:
    • frontend/atla/src/pages/HomePage.tsx
    • frontend/atla/src/pages/TripsPage.tsx
    • frontend/atla/src/pages/ExplorePage.tsx
    • frontend/atla/src/pages/ProfilePage.tsx

Requirements

  • Connect pages to live API hooks/queries.
  • Implement key actions: view trips, navigate to trip detail, profile update flow, and explore search results.
  • Add consistent loading, empty, and error states.
  • Keep auth guards and route behavior intact on desktop/mobile layouts.

Acceptance Criteria

  • Pages render live data (not static placeholder copy) using current backend APIs.
  • Main CTA flows are functional and navigable.
  • Error and empty states are user-friendly and consistent.
  • Typecheck/build pass and no route guard regressions.

Dependencies

Out of Scope

  • New product features unrelated to replacing placeholder data

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions