Pranjali_Bhardwaj_portfolio

Inspiration

What it does

How we built it## About the Project – Portfolio

🧠 Inspiration

I created this Portfolio because I wanted a single place to showcase the diverse projects I’ve built — from full-stack clones to machine-learning pipelines.
Having studied Computer Science and worked across front-end, back-end, and ML, I realised that each project told a story: what I learned, how I solved problems, and where I could go next. So this portfolio is that story — my digital “home-base” for my work and skills.

🏗️ How I Built It

This portfolio is built using modern web technologies and a deployment workflow to keep it live and up to date:

Frontend: HTML, CSS, JavaScript (ensuring responsiveness so it works well on mobile and desktop).
Backend / Hosting: A lightweight server (server.js), bundled with tools so the site is optimised and deployed (e.g., via Vercel).
Content structure: Each project has a clear entry: what it is, what tech I used, a link to code (GitHub) and live demo if available.
Continuous workflow: As I finish new projects (e.g., my AI/ML projects, web apps, internships), I update this portfolio so it stays current.

💡 What I Learned

Working on the portfolio helped me sharpen several key skills:

Modular, maintainable web architecture so future additions are easy.
Deployment best-practices: hosting, performance optimisation, and responsiveness.
Crafting content for non-technical and technical audiences — making sure my projects are accessible, understandable, and compelling.
Version control and project organisation: making sure the portfolio itself is well-managed in GitHub, with clear commits, branches, and documentation.

🚧 Challenges Faced

A few of the hurdles I encountered:

Ensuring the portfolio looked great on all devices: mobile, tablet, desktop. Design decisions had to balance aesthetics and readability.
Keeping the portfolio up-to-date without it becoming a chore: integrating a workflow where adding a new project didn’t mean a major refactor.
Writing concise yet informative descriptions of each project: enough technical depth for recruiters/engineers, but also a high-level story for non-technical viewers.
Managing deployment and build issues: ensuring the server script (server.js) and bundling steps didn’t introduce latency or break responsiveness.

✨ Future Scope

Looking ahead, I plan to enhance the portfolio by:

Adding an interactive filter or tag system (so visitors can filter by “ML”, “Web Dev”, “Internships”).
Including a blog section where I reflect on my learning journey and post mini-case-studies of projects (e.g., “How I optimised model X”, “Why I chose architecture Y”).
Integrating analytics to understand visitor behaviour (which projects draw the most attention) and iterating accordingly.
Constantly updating it as I complete new roles (e.g., Software Engineering Internship at Google or Data Analyst role at Goldman Sachs) and build new projects (Web3, AWS, etc.).

Thank you for visiting my portfolio. I hope the projects help you understand who I am, how I learn, and what I build.
I’m always open to feedback, collaboration, and new challenges.