Engineering Portfolio & Deployment Pipeline

Context: Independent website
Period: 2026 · Published site
Focus: Software Engineering
Tools / methods: Hugo / Wowchemy · SCSS · GitHub · Netlify

Engineering question

A technical portfolio must remain readable, maintainable, and safe to update without interrupting an existing deployment.

My work

  • Customized a Hugo/Wowchemy static site for projects, experience, and research.
  • Adopted branch-based Git workflows and Netlify build/deployment processes.
  • Iteratively improved responsive presentation and content organization.

Technical approach

The publishing pipeline separates authoring from production release: local edits → feature branch → Git commit → remote preview → review → production merge. Static generation avoids a bespoke application backend for standard professional content.

Engineering considerations

Website deployment and technical documentation work; future features and proposed demonstrations are not treated as implemented.

Evidence and maturity

Deployed personal website with version-controlled content and deployment configuration.

Public scope

Only public-facing site code and content are linked.

Shivam Vashishtha
Shivam Vashishtha
Engineer

Electrical Engineering and Computer Science student working across power, AI, energy systems, and emerging technologies.