How swanand33/my-portfolio works
Project type and purpose
• This is a static, front-end personal portfolio website.
• Its goal is to showcase professional journey, skills, and projects in a responsive, modern UI/UX.
• It uses only HTML, CSS, JavaScript, image assets, and is hosted on Netlify (with form-submission support).
File structure
• Top-level files:
• index.html – entry point, main markup
• styles.css – all styling
• script.js – any interactive behavior
• img/ – folder of image assets
• netlify.toml – Netlify configuration (forms, redirects)
• package.json – (optional) metadata, local dev scripts
• No backend code, no server. It’s fully static and delivered via CDN.
README for additional insights
• Highlights ‘Responsive Web Design’, ‘Netlify (Hosting & Form Submissions)’
• Emphasizes contact form and social-media integrations.
• No mention of build tools beyond package.json; assume direct deploy.
Main components and interactions to capture
a. User’s web browser (client)
– Fetches HTML/CSS/JS & images
– Renders the site; runs script.js
– Submits contact form via Netlify’s form endpoint
– May click out to external social media sites
b. Static hosting environment (Netlify CDN)
– Hosts all static assets
– Serves index.html, CSS, JS, images over HTTPS
– Provides Form-Submission API (serverless form handling)
c. External services
– Social media platforms (GitHub, LinkedIn, Twitter)
– Analytics if any (not currently included but could be added)
Relationships / data flows
• Browser → CDN: GET index.html, styles.css, script.js, image assets
• Browser (script.js) → CDN: GET any additional assets
• Browser → Netlify Form API (POST) → Netlify backend
• Browser → External service URLs (social media links)
Architectural patterns / design principles
• Static-site architecture (JAMstack style)
• Separation of concerns: HTML for structure, CSS for style, JS for behavior
• CDN for global distribution and performance
• Serverless-enabled form handling (no custom backend)