Skip to main content

Engineering project

Portfolio Generator

A full-stack application that converts structured Microsoft Word resumes into responsive portfolio websites.

C#ReactTypeScript.NET AspireASP.NET CoreOpen XMLAzureGitHub Actions

Project overview

The context behindthe final result.

A closer look at the goals, decisions, and technical thinking that shaped the project.

The application turns a structured Word document into reusable portfolio data rather than requiring users to manually rebuild the same information in a website editor.

A React workflow guides the user from upload through review, theme selection, preview, and export while the ASP.NET Core backend handles document parsing and generation.

Key features

What the projectneeded to accomplish.

Core capabilities delivered for Portfolio Generator.

01

Document-processing API

ASP.NET Core endpoints receive Word files, extract structured resume information, and return normalized data.

02

Guided upload workflow

A multi-step React interface helps users upload a document, review extracted data, and select a theme.

03

Isolated live preview

Generated templates render inside an iframe so their styles remain isolated from the application shell.

04

Dynamic theme system

Multiple layouts can consume the same structured resume data without duplicating content.

05

Local service orchestration

.NET Aspire coordinates application services, endpoints, and configuration during development.

06

Automated deployment

GitHub Actions builds and deploys the application to Azure App Service.

Application workflow

From resume to portfolio website

The user uploads a structured resume, reviews the parsed data, selects a presentation theme, previews the result, and exports the completed site.

  1. 01

    Upload

    Upload a structured .docx resume.

  2. 02

    Parse

    Extract resume content with ASP.NET Core and Open XML.

  3. 03

    Generate

    Convert document content into structured portfolio data.

  4. 04

    Theme

    Choose a layout and visual presentation.

  5. 05

    Preview

    Review the generated website in an isolated preview.

  6. 06

    Export

    Download the completed portfolio website.

Technical highlights

The systems behindthe interface.

Selected architectural and implementation decisions that shaped the project.

01

ASP.NET Core

Minimal API endpoints handle uploads, document parsing, and structured response data.

02

React and TypeScript

The frontend coordinates upload, review, theme selection, preview, and export.

03

Open XML

DocumentFormat.OpenXml reads structured content from Microsoft Word files.

04

Theme engine

Layout templates remain separate from resume data, allowing multiple presentations from one source.

05

.NET Aspire

Aspire simplifies local orchestration and configuration across application services.

06

GitHub Actions

CI/CD workflows build the frontend and backend and deploy the application to Azure.

Challenges

The difficult partsshaped the better decisions.

The constraints and implementation problems that required the most thought.

01

Reading Word documents

Resume documents needed to be interpreted consistently and converted into predictable structured data.

02

Isolating generated themes

Generated website styles had to be previewed without leaking into or breaking the application interface.

03

Coordinating multiple services

The React frontend, ASP.NET Core backend, and deployment workflow required consistent endpoint and configuration management.

Future direction

Still evolving.Still worth refining.

Potential next steps identified through the current implementation.

  1. 01

    Add custom block editors

  2. 02

    Support font customization

  3. 03

    Add one-click Netlify deployment

  4. 04

    Expand the theme library

Explore what comes next

Need something with similar depth?

Custom software projects are scoped around the workflow, users, and technical requirements involved.