How devberringer/recipeweb works
Project type and purpose
• The folder names (e.g. “recipes”, “UserPage”, JSON files for breakfast/lunch/dinner/deserts) plus API and auth contexts indicate the app is a recipe-browsing and user-management portal.
File structure
• Top-level configs:
• package.json, tsconfig.json, vite.config.ts, ESLint/Prettier configs
• postcss.config.cjs, tailwind.config.js → CSS tooling
• Public vs. build vs. src:
• public/ contains static JSON (mealType, recipes) and assets used at runtime
• src/ contains all source code:
– api/ layer (api.ts, contracts.d.ts)
– components/ divided into pages (Home, Login, Recipes, UserPage, etc.), shared UI widgets, and static pages (About, Contact)
– contexts/ for global state (authContext, userContext, categoriesContext, recipeDraftContext)
– routes/ (React Router setup)
– types/, assets/ and main entry (main.tsx, index.css)
• build/ is the Vite production output: compiled JS/CSS, an index.html, and inlined JSON for meal data.
README
• The README contains only “test,” so we infer architecture from code rather than documentation.