How govtechmy/hansards-front works
Project Type and Purpose
• Full-stack web application (front-end only) built with Next.js and React.
• Purpose: render dashboards, charts, geo-maps, and data catalogs by fetching Hansards data from a separate back-end service.
• Key features: server-side rendering/static generation (SSG/SSR), internationalization, interactive charts/maps, client-side hooks and contexts, and a small internal API layer (Next.js API routes).
File Structure and Key Components
a. Presentation Layer
– /pages (Next.js routing: UI pages and API endpoints under /pages/api)
– /components (reusable UI building blocks: Button, Modal, Chart-Header, Map components)
– /dashboards & /data-catalogue (higher-level page compositions)
– /charts (chart primitives: bar, line, heatmap, choropleth, etc.)
– /public & /styles (static assets and CSS/Tailwind styling)
b. Application Logic Layer
– /lib/api.ts (client for BE communication)
– /lib/routes.ts & /lib/schema (route definitions + data schemas)
– /hooks (useData, useCache, useMap, etc.)
– /lib/contexts (analytics, slider, window contexts)
– /pages/api (Next.js serverless endpoints: count, revalidate)
– next.config.js + next‐i18next.config.js (framework configuration + i18n)
c. Data Layer
– External Hansards back-end (NEXT_PUBLIC_API_URL)
– Tinybird analytics endpoint (/lib/tinybird.ts)
Architectural Patterns and Design Principles
• File-based routing (Next.js)
• Separation of concerns:
– Presentation (components, charts)
– Data‐fetching (hooks + lib/api)
– State management (React Contexts + hooks)
• Static‐first strategy: heavy use of build‐time JSON imports (geojson)
• API abstraction in lib/api.ts + route definitions in lib/routes.ts
• DRY styling via Tailwind + CSS modules