How kevicole/fullstack-starter works
Project Type and Purpose
• This is a full-stack web application starter project.
• Backend: Java Spring Boot service exposing REST endpoints for Inventory and Product management.
• Frontend: React application (with Redux “ducks” pattern) that consumes those endpoints.
• Sample-data and import script are provided to seed/refresh the database.
File Structure
• Top-level:
• sample-data/ (import.sh + JSON data)
• starter/ (Spring Boot backend)
• ui/ (React/Redux frontend)
• starter/src/main/java/com/starter/fullstack:
• api/ → DTOs (Inventory, Product, UnitOfMeasurement)
• dao/ → data access classes
• rest/ → Spring MVC controllers
• config/ → Boot config, security config+properties
• StarterApp.java → main entry point
• ui/src:
• components/ → reusable React components (forms, tables, modals)
• containers/ → layout + view containers per route
• ducks/ → Redux modules (actions + reducers)
• middleware/, reducers/, constants/, hooks/, themes/
README for Additional Insights
• Confirms Spring Boot + Gradle for backend; NodeJS + npm for frontend.
• Instructions to build/run each side separately.
• Sample-data import seeds the backing DB.
• Break the backend into:
• Entry point (StarterApp)
• Configuration modules (StarterConfig, WebSecurityConfig)
• API layer (InventoryController, ProductController)
• Data layer (InventoryDAO, ProductDAO)
• Persistence (DB + sample data script)
• Break the frontend into:
• UI Components (forms, modals, tables)
• Containers (page/layout components)
• State management (ducks: actions + reducers, middleware)
• Routing (if any) + constants + themes
• Third-party frameworks (Spring Security, Redux Thunk or Saga if used)