How 44dhi/busrides works
Project type and purpose
• This is a Next.js–based web frontend (“Bus-Rides-Ghost-Theme”) that acts as a headless client for a Ghost CMS backend and delivers a multi-language (en/fr) content site with SSR/SSG, static assets, and search.
File structure
• Top-level directories:
• pages/ → Next.js routes (SSR/SSG entry points, dynamic routes for posts, tags, authors, search, 12-days section, learning paths, parking lot).
• components/ → UI layer following atomic design (12-days, molecules, organisms, templates, stylesheets).
• Ghost-API/ → wrapper modules for Ghost Content API and search API.
• helpers/, locales/, markdown/ → utility functions, i18n, static markdown for learning-paths & parking-lot pages.
• public/ → static assets (images, logos, thumbnails).
• server.js, next.config.js → custom Next.js server and build/runtime configuration.
• CI/CD config: .github/workflows/, azure-pipelines.yml, buildspec.yml, .ebextensions/ → GitHub Actions, Azure Pipelines, AWS EB deployment.
Elements
• Clear labels: Browser, Next.js Server, Ghost CMS API, Search API, Static CDN, CI/CD Pipelines
• Browser → Next.js (page requests)
• Next.js → Ghost Content API (data fetch)
• Next.js → Search API (search fetch)
• Browser → CDN (static assets)
• CI/CD → Next.js Server (deploy)
• Blue rectangles for compute (Next.js Server, Ghost API)
• Yellow parallelogram for static asset store/CDN
Additional notes
• Localization branching (en/fr) under the Next.js routing component.
• Call out configuration files (next.config.js, server.js, .ebextensions) as part of the deployment/configuration block.