How pinaka-pani-18/javascript-projects works
Project type and purpose
• This repository is a collection of 50+ standalone, static, client-side web mini-apps (beginner to advanced) built with plain HTML, CSS and JavaScript.
• Each “Project-NN” folder contains exactly the assets needed to run that mini-app: index.html, style.css, index.js, plus occasional images or sound files. There is no server-side code, no build/configuration files (e.g. package.json), and no database—these are purely static front-end demos, some of which call third-party browser APIs (geolocation, weather, dictionary, Text-to-Speech, etc.).
File structure
• Top-level folders:
• .vscode (editor settings)
• Project-01 through Project-50 (each a self-contained static app)
• A root “Project” folder duplicating basic template
• README.md
• Key patterns:
• Each mini-app follows the same 3-file pattern (HTML CSS JS), optionally with images/ sounds subfolders.
• No shared libraries or common code—each folder is independent.
• Assets are all static; there is no build pipeline or backend.
README for additional insights
• The README enumerates each project’s purpose (e.g. “Random Joke Generator”, “Weather App”, “Dictionary App”, “Drum Kits”)
• It highlights which mini-apps will use browser APIs or external REST APIs (weather, dictionary, geolocation, text-to-speech, etc.).
Detailed capture of essential elements
• Don’t just show “Frontend”—break it down into “HTML (structure)”, “CSS (presentation)”, “JS (logic)”
• Per-app assets folder (images/sounds) for Projects 04, 08, 11, 14, 15, 17, etc.
• Browser Web APIs separately from third-party REST APIs.