How ateeq786316/banking-website works
Project type and purpose
• This is a full-stack “Online Banking System” educational project.
• The bank folder holds a React/Vite-based single-page application (SPA) for customer interactions (balance inquiry, deposit, withdrawal, transfer, bill payment, signup/login).
• The server folder contains a Node.js/Express backend with a Mongoose model (Bankuser.js) that persists user data in MongoDB.
File structure
• Top-level directories:
• bank/ (frontend)
• server/ (backend)
• documentation/ (design docs)
• Frontend structure (bank/src): React components for each banking feature plus a central App.jsx.
• Backend structure (server/):
• index.js – Express app entrypoint, routes, middleware.
• models/Bankuser.js – Mongoose schema for user accounts.
• Config/build files:
• bank/vite.config.js, package.json, .gitignore, eslint.config.js
• server/package.json
README
• Documentation folder contains a Word/PDF specification (“Online Banking System.docx/pdf”) that likely describes requirements and workflows.
Detailed breakdown of components (separate as many as practical)
• Frontend:
• App.jsx (root router)
• Home, Login, Signup, Balance, Deposit, Withdraw, Transfer, PayBill components
• Static assets (images)
• Backend:
• index.js (Express app, middleware, route registration)
• Controllers (implied inline in index.js or separate files) for each route
• Bankuser.js (Mongoose schema with fields: balance, transaction history, credentials)
• Database: MongoDB (hosted on localhost or cloud DB)
• (Optional) External identity/email abstraction—if the documentation mentions notifications.
Detail without over-complication
• Every React page component as part of the UI layer.
• Monolithic Express server as one service with multiple endpoints.
• Data flow for a sample use case (e.g., user login → fetch balance → render Balance.jsx).