← All project stories

Case study / 2026

Portfolio Website Delivery

A public professional portfolio built and maintained with an AI-assisted development workflow.

HTMLCSSJavaScriptViteGitHub ActionsCloudflare PagesCodex

01 / Context

The problem

The portfolio needed accurate public content, readable project evidence, reliable contact paths, and repeatable releases within a free-hosting constraint.

The website brings Microsoft ecosystem projects and professional background into a public portfolio.

02 / Contribution

What I built

Directed an AI-assisted workflow to build and maintain a static portfolio, review changes, run automated checks, and publish through GitHub and Cloudflare Pages.

The design decision

A static multipage site keeps delivery simple and avoids an application database or paid runtime services.

Scope

  • Public project and professional-background pages
  • Browser-based project search and dialogs
  • Email draft helpers without a server-side form
  • Production build, automated checks, and deployment verification

03 / Structure

How it works

A static website with AI-assisted implementation and human direction over content, scope, and release decisions.

  • Vite builds HTML, CSS, and native JavaScript modules
  • A shared renderer prerenders page content for direct navigation and no-JavaScript reading
  • GitHub Actions validates the build; Cloudflare Pages publishes the static output
  • Contact helpers encode draft recipients, subjects, and bodies without sending messages

Through the workflow

  1. Visitor reads a project or service page
  2. Browser interactions help explore project details
  3. Visitor chooses an email provider and reviews a draft
  4. Owner updates source, verifies the build, and releases through GitHub

04 / Operation

Controls and upkeep

  • Escaped text at HTML rendering boundaries
  • Content Security Policy and response security headers
  • Source and private files excluded from the static deployment package
  • Automated checks for routes, links, privacy, encoding, and 404 behavior

Keeping it useful

Maintain public facts in source control, review dependency advisories separately, validate each release, and verify the published pages. A passing build is not a comprehensive security clearance.

05 / Result

The outcome

Established a maintainable public portfolio with repeatable validation and static deployment.

The portfolio is live with shareable pages, project discovery, and contact options that let visitors review an email before sending.

Discuss a similar project
Inside the project