How ahnayef/react-neub-spring-routine works
Project type and purpose
• This is a single-page, static ReactJS web application (no separate backend).
• Purpose: Display academic schedules (routines) for different semesters and weekends.
File structure
• Top-level:
• index.html – host page
• package.json / pnpm-lock.yaml – dependencies and build scripts
• vite.config.js – build tool configuration
• public/ – static assets served at root (robots.txt, favicon, etc.)
• src/ – application source
• main.jsx – React entry point
• Components/ – UI subdivided by feature:
– Home.jsx, Error404.jsx
– Cr/Cr.jsx (Curriculum?) + cr.css
– Routine/… JSON files + Routine.jsx + RoutineBox reusable component
– Weekend/Weekend.jsx
• assets/ – fonts, images, PDFs
• No server code, all data (JSON + PDFs) is local.
Key insights from README
• Built with ReactJS
• Deployed to Netlify (static hosting)
• Core feature: display downloadable and interactive schedule.
Main components & their relationships
A. Browser (Client)
• Requests index.html from CDN/Netlify
• Downloads bundled JS/CSS
B. React App (bundle.js)
• main.jsx bootstraps ReactDOM → App Router
• Routes load Home, Routine, Weekend, Cr, Error404
C. Components layer
• Presentation components (JSX + CSS)
• Data layer: JSON files under src/Components/Routine
• Utility styles under src/utility
D. Static assets
• src/assets: images, fonts, PDFs
• public folder: meta, favicon, robots.txt
E. Build & Deployment
• Vite bundles assets, outputs dist/
• Netlify serves the dist directory via CDN
Architectural patterns & principles
• Component-based UI (React)
• Static site generation workflow (Vite → Netlify)
• Separation of concerns:
– Presentation (JSX + CSS)
– Data (local JSON)
– Assets (pdf/images)