Live portfolio
Portfolio Website
A public showcase for practical AI-assisted software projects.
A public project showcase for my AI-assisted coding work, teaching tools, simulations, dashboards, and technical writing.
Project cards
Detail pages
Vercel preview
Why I built it
I wanted a small, public front door for real projects without turning the portfolio itself into a giant catch-all application.
What it does
- Introduces my current technical work in a compact project-gallery format.
- Links visitors to live standalone apps when a public demo exists.
- Keeps extra context on short project detail pages inside the portfolio.
Tech stack
Next.jsReactTypeScriptVercelGitHubAI-assisted development
Build / Deployment
- App type
- Portfolio / project showcase
- Code location
- Standalone GitHub repo
- Front end
- Next.js, React, TypeScript
- Deployment
- Vercel from GitHub / preview deploy workflow
- Public URL
- Current portfolio root
- Notes
- Links out to standalone apps rather than absorbing their source code.
Architecture / How it works
- The portfolio website is a standalone web project. It uses Next.js and React for the site itself, while the showcased apps can use their own stacks.
- Some projects are Vite apps, some are Python or Streamlit tools, and the genetic algorithm project includes C++, WebAssembly, and a web front end.
- The important architectural choice is separation: this website describes and links to projects, but does not absorb all of their source code.
What I built
- A compact homepage that introduces my work and surfaces real projects quickly.
- Reusable project cards driven by structured project data.
- Individual detail pages for projects that deserve more explanation.
- External links to standalone apps where public demos exist.
- A deployment workflow through GitHub and Vercel.
What I learned
- A portfolio site works better when it shows real things instead of vague ambitions.
- Keeping standalone apps separate prevents the portfolio from becoming bloated.
- Project cards need to be short, but detail pages can explain architecture, history, and tradeoffs.
- Deployment details matter because “I built this” is more credible when the live app, source structure, and workflow are clear.
Current status
The portfolio is live as a Vercel-backed showcase site and is being refined before final public launch polish.
Next steps
- Replace placeholder visuals with real screenshots as projects mature.
- Connect production domain settings only after final review.
- Keep project data current as standalone demos go public.