How hellogithub-team/geese works
Project type and purpose
• This is a full-stack, server-rendered React application built with Next.js and styled with Tailwind CSS. It powers the “HelloGitHub” community portal (“Geese”), where users browse, search, comment on, bookmark, and rate beginner-friendly open-source projects.
File structure
• Top-level config: Dockerfile, server.js, ecosystem.config.js for PM2, GitHub Actions workflows, ESLint/Prettier, Yarn.
• “pages/”: Next.js routes driving both SSR and SSG.
• “components/”: Reusable UI widgets (buttons, dialogs, navbar, etc.).
• “services/”: A thin client-side service layer that wraps HTTP calls to the HelloGitHub backend API.
• “public/”: Static assets (images, fonts, favicon, JSON locales for i18n).
• “data/” & “docs/”: Markdown docs, help content, images.
• Configuration for i18n (next-i18next.config.js), sitemap, postcss, Tailwind, TypeScript.
Insights from the README
• The app is deployed at hellogithub.com, with features centered around open-source project discovery and community interaction.
• No internal database code—data comes from an existing HelloGitHub API.