How jgmacedo/cha-com-senhor-frontend works
Project type and purpose
• This is a full-stack web application (“Chá com o Senhor”) for daily spiritual devotions, based on a Next.js 15 frontend and a Java Spring Boot REST API backend.
• Purpose: deliver daily devotional content (Bible verses + commentary), with separate user and admin experiences, authentication, profile management and content management.
File structure
• Top-level directories
– app/: Next.js App Router pages and layouts
– components/: reusable React UI components (shadcn/ui base under ui/, admin-specific under admin/)
– contexts/: React Context providers (auth, theme)
– hooks/: custom hooks (use-mobile, use-toast)
– lib/: API client, health-check and utility functions
– public/: static assets
• Config and scripts
– next.config.mjs, tailwind.config.ts, postcss.config.mjs, tsconfig.json: build and styling config
– vercel.json: Vercel deployment settings
• Project_memorial.md and readme.md contain documentation and architecture overview.
README for additional insights
• Frontend stack: Next.js, React, TypeScript, Tailwind CSS, shadcn/ui, next-themes
• Backend stack: Java Spring Boot (REST API), Spring Security with JWT, Spring Data JPA, relational database
• Deployment: Frontend on Vercel, Backend on a production server
• Key features: user/devotional flow, admin panel, authentication and authorization with roles
Detail
– App Router (app folder), Layout (layout.tsx), Pages (/page.tsx), UI Components (components/ui), Admin Components (components/admin), Context Providers (contexts/auth, theme)
• On the backend side, call out:
– Authentication module (Spring Security + JWT filter)
– Devotional service layer, Verse repository (Spring Data JPA)
– REST controllers for user, devotional, verse, health-check (lib/health-check aligns with a /health endpoint)
• Environments
– Development (localhost:3000, local Java server:8080) vs. Production (cha-com-senhor.vercel.app, backend server URL)