How rishit30g/personal-portfolio works
Project type and purpose
• This is a static, single‐page personal portfolio website.
• It consists of HTML, CSS, JavaScript and image assets, and is meant to be deployed (for example) on GitHub Pages or any static‐hosting service.
• It uses a third‐party service (EmailJS) for contact form submissions, and includes external CDNs (FontAwesome, icons8) and a Google Drive link for the resume.
File structure
• Top‐level files and directories:
• index.html – the single HTML entry point
• style.css – stylesheet for layout and styling
• script.js – JavaScript for dynamic behavior (form submission, interactive effects)
• CONTRIBUTING.md & README.md – documentation
• No backend code or database folders; this is a pure frontend project.
README for additional insights
• Describes sections (Home, About, Services, Skills, Contact, Footer).
• Instructs how to replace placeholders with personal data, integrate a favicon, FontAwesome kit, EmailJS service and template IDs, and a Google Drive resume link.
Main components
a. Frontend (Browser)
• index.html
• style.css
• script.js
b. Static Web Host
• GitHub Pages (or any static‐hosting service) serving the files
c. External Services
• EmailJS API (for contact form submissions)
• Google Drive (resume link)
Relationships and interactions
• User’s browser requests index.html, CSS, JS and images from the static host.
• script.js, upon form submit, performs an HTTP POST to the EmailJS endpoint (using Service ID, Template ID, UserID).
• The resume link points to a Google Drive hosted PDF.
Architectural patterns and design principles
• Single‐Page Static Application: separation of content (HTML), styling (CSS), and behavior (JS).
• CDN‐backed assets to reduce hosting load and increase performance.
• External API integration pattern for contact form (EmailJS).
• No server‐side code—ideal for simple personal branding sites.