How alpharceus/portfilio_new works
Project type and purpose
• This is a single‐page/static front-end portfolio website. There is no backend or server-side code in the repository—just HTML, CSS, JavaScript, and static assets (JSON data, a PDF resume, images, etc.). Its purpose is to present blogs, projects, papers, and other personal information in a dynamic, interactive way.
File structure
• Top-level:
• readme.md – minimal placeholder
• src/ – root of the static site
• Within src/:
• index.html, projects.html, papers.html – entry points/pages
• css/ – stylesheet files (styles.css, portfolio-pages.css)
• js/ – client-side scripts (main.js, projects.js, papers.js, star-map.js, terminal.js)
• assets/ – data/asset files (blogs.json, projects.json, papers.json, schedule.json, resume.pdf)
• No build or deployment scripts in the repo (likely hand-deployed to GitHub Pages, Netlify, etc.).
README for additional insights
• The README simply names the project (“portfolio_new”) without extra details. All architectural clues come from the file tree.
a. Main components
• Browser (Client) – loads HTML, CSS, JS
• Static File Server/CDN – hosts HTML/CSS/JS and asset files
• Static Assets Store – JSON data, resume PDF, images, other media
b. Relationships & interactions
• Browser sends HTTP GET requests to the Static File Server to fetch HTML, CSS, JS.
• As each page loads, the JavaScript modules fetch JSON files (via Ajax/fetch) from the same server to populate dynamic content (blog list, project list, papers list, star map, terminal interactions).
c. Architectural patterns & principles
• Static site (no application server)
• Separation of concerns:
– HTML for structure
– CSS for styling
– JS modules for data loading and interactive features
• JSON files treated as a pseudo‐API (data layer)
d. Key technologies
• HTML5, CSS3
• Vanilla JavaScript (modular scripts in src/js/)
• JSON for data
• Static hosting (GitHub Pages, Netlify, AWS S3/CloudFront, etc.)