How rahulhanje/cba-tech-repo works
Project Type & Purpose
• Type: Static front-end demo/tutorial repository (no backend, no database).
• Purpose: A set of standalone HTML pages illustrating JS concepts (variables, loops, arrays, functions, events, async, TypeScript defaults, etc.).
File Structure
• Root:
– README.md
– 27_4b_…_master.zip (archive)
• /javascript:
– .vscode/ (editor configs)
– ~20 .html demo pages (EventDemo.html, arrayexample.html, internaljsdemo.html, etc.)
– .js files (script.js, varibles.js, defltParm.js)
– defltParm.ts (TypeScript example)
– a few .txt and NotesJS files.
No backend folder, no package.json, no build scripts beyond the single .ts file.
Relationships & Data Flow
1. Developer edits files in VS Code → commits to GitHub
2. (Optional) CI builds .ts → .js, lints, then deploys
3. Hosting serves .html + .js assets over HTTP(S)
4. User’s browser fetches pages → JS runs in-page
5. User interacts with UI (clicks, keys) → event handlers in the scripts fire
Patterns & Tech
• Pattern: Static site (no runtime server), modular demos per HTML page
• Tech:
– HTML5 pages with inline/external JS
– TypeScript (single demo) → compiled to JS