How ozblind/ozblind_fe works
Project type and purpose
• This is a single-page web application (SPA) frontend built with React, Vite, and TypeScript (“OZBLIND Frontend”).
• It provides UI for browsing and interacting with posts, notifications, jobs, bookmarks, and user settings. It communicates with backend REST APIs and several third-party services (e.g., GitHub API, remote job APIs).
File structure
• Top-level config: Docker Compose, Vite config, environment files, linting/config scripts.
• src/ layout:
• src/pages – route components (Page layer)
• src/router – route definitions and guards
• src/layouts – page wrappers (MainLayout, RootLayout)
• src/components – reusable UI pieces (Board, Post, Sidebar, Toast, etc.)
• src/api – HTTP clients for backend and external services
• src/hooks – custom React hooks encapsulating business logic & data fetching
• src/store – global state stores (auth, toast)
• src/utils, src/constants, src/types – shared utilities, constants, type definitions
• Deployment: Docker Compose for local dev; Vercel for production hosting.
Key insights from the README
• Application runs inside a Docker container via docker-compose up --build
• The frontend endpoint is served at localhost:5173
• Environment variables configure the API base URL
• No explicit backend code here—the app relies on remote services