How arnesh03/bankie-webapp works
Project type and purpose
• From the file tree (.prettierrc, index.html, script.js, style.css) and README we see this is a pure front-end single-page demo web application (“Bankie-WebAPP”) with no separate backend or database. It runs entirely in the browser and is hosted as static assets (for example on Netlify). Its purpose is to demonstrate net-banking features (login, logout, loan, transfer, delete account, sorting, date display) using four hard-coded demo accounts.
File structure
• index.html: the HTML entry point and UI skeleton
• style.css: presentation layer, styles for buttons, forms, transaction history
• script.js: all business logic and data model (the demo accounts array, login/logout timer, transfer/loan/delete/sort functions, DOM updates)
• .prettierrc and README.md: tooling config and documentation
There are no “backend” or “database” directories or files—logic and “data” live in script.js and in browser memory.
README for additional insights
• It defines the user flows and features (login, logout timer, loan limit, transfer, delete, sorting, day display).
• No mention of external APIs or services.
• Hosting is via Netlify (static site).
Elements
• Clear labels: “Browser”, “index.html (UI)”, “style.css (Styling)”, “script.js (Logic & Data)”, “Netlify (Static Host)”
– From Netlify → Browser (HTTP GET of index.html, CSS, JS)
– From Browser UI → script.js (event handlers)
– From script.js → DOM (updates UI)
– From Browser → User (UI rendered)