How neetunabbu/nabeela-portfolio works
Project type and purpose
• This is a static personal portfolio website built with HTML, CSS, and JavaScript, hosted on Netlify.
• It showcases projects, skills, work history, certifications, and provides a contact form powered by Formspree.
• External assets include a resume PDF on Google Drive and links to GitHub and LinkedIn.
File structure
• Top level:
• NabeelaResume.pdf (external link collateral)
• README.md (project overview, tech stack, links)
• index.html (single‐page application entry)
• style.css (custom styles, alongside Bootstrap)
• script.js (front‐end logic for contact form submission)
• No backend or database code—this is purely front‐end with integrations to external services.
Insights from the README
• Frontend: HTML5, CSS3, Bootstrap 5, JS (ES6)
• Backend (not in this repo): PHP/Laravel, Node.js (for other projects)
• Uses Formspree for contact form handling
• PDF assets and certificates hosted on Google Drive
• Hosted and served by Netlify
Main components
a. Client (User’s browser)
b. CDN/Static‐Site Hosting (Netlify)
c. Static assets:
• index.html, style.css, script.js
• References to Bootstrap’s CDN
d. External services:
• Formspree API (contact form endpoint)
• Google Drive (resume & certificates)
• Social/code links (GitHub, LinkedIn)
Relationships and data flow
• User → requests index.html from Netlify → browser renders HTML/CSS/JS
• script.js → HTTP POST → Formspree → returns success/failure to browser
• User clicks “View Résumé” → browser navigates to Google Drive link
Architectural patterns & principles
• Separation of concerns: Static UI vs. external form‐processing service
• Single‐page layout: All content in index.html, styled and made dynamic by CSS/JS
• CDN usage: Offloading hosting and delivery to Netlify and Bootstrap CDN
• Externalized assets: PDF and form logic delegated to specialized services