How club-unit/unit-frontend-cra works
Project type and purpose
• This is a single‐page application (SPA) built with Create React App and TypeScript.
• It implements a community or portal site with features like boards, posts, user profiles, applications, and forms.
• It has no backend code in this repo; it consumes external RESTful APIs.
File structure
• src/pages & src/components/pages – individual routes and page‐level components (404, index, posts, applications, forms, users).
• src/components/common – shared UI widgets (Navbar, Footer, AuthCards, ContentEditor).
• src/contexts – React Context providers (AuthProvider, NotificationProvider) for cross‐cutting concerns.
• src/hooks/api – custom React hooks that wrap API calls (usePosts, useApplications, useUser, etc.).
• src/utils & src/constants & src/types – utilities (fetcher, date formatting), constants (routes, pagination), and TypeScript types for API responses.
• Configuration & scripts – ESLint, Prettier, Husky (git hooks), Tailwind, Webpack (via CRA), CI/CD (buildspec.yml).
README
• Standard Create React App instructions—no custom architecture doc in README.
Detail vs simplicity
• 4 frontend layers separately if space allows.
• Do not over‐fragment—focus on high‐level flows and key modules rather than every single component file.