How ayuen91/may-first-lines-of-code works
Project Type and Purpose
• This is a personal portfolio and static demo site bundling several small “amateur” projects (HTML/CSS/JS frontends and standalone Python scripts).
• There is no running backend server or database—everything is served as static files. The README is purely instructional for committing to GitHub.
File Structure Analysis
• Top‐level:
• .vscode, .DS_Store, README.md
• portfolio website/ → static HTML/CSS/JS for the main portfolio
• projects amateur/ → subfolders for each demo (HangManGame in Python, calculator, login page)
• python projects/ → flat collection of standalone Python scripts
• radio button/ → another simple HTML demo
• test.js → likely a utility or experiment script
• No build scripts or server configs—this is purely static content (plus downloadable/runnable Python files).
Insights from README
• Focus is on version control via Git + GitHub.
• Implies using GitHub (possibly GitHub Pages) to host the portfolio.
Components
a. Developer Workstation
– Editing files (HTML, CSS, JS, Python).
– Git client for commits.
b. Version Control System (GitHub)
– Repository stores all project files.
– GitHub Actions (optional) or GitHub Pages for deployment.
c. Static Hosting / CDN
– (e.g., GitHub Pages or an S3 bucket + CloudFront) delivers static assets.
d. End-User Browser
– Requests index.html, downloads CSS & JS, interacts with frontend.
– Python demos are downloaded and run locally by users.
e. Optional Local Python Runtime
– For users who clone/download the Python scripts to run them.
Relationships and Data Flows
• Developer → pushes commits → GitHub repository
• GitHub → (via Pages or CI/CD) → deploys static files → Hosting/CDN
• Browser → HTTP GET → Hosting/CDN → serves HTML/CSS/JS
• Browser → local runtime → runs JS demos in‐browser
• User (optionally) → downloads Python scripts → runs on local Python interpreter
Architectural Patterns & Principles
• Separation of Concerns:
• Frontend assets (HTML/CSS/JS) under portfolio website/
• Demo front-ends in projects amateur/
• Python scripts in python projects/
• Static Hosting Model: no dynamic server, content is immutable files.
• GitOps Deployment: commits to Git trigger deployment to hosting.
Technologies & Frameworks
• HTML5, CSS3, JavaScript (vanilla) for all frontends
• Python 3.x for standalone scripts
• Git & GitHub (possibly GitHub Pages) for version control & hosting