Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/apursley2012/windows-xp-developer/llms.txt

Use this file to discover all available pages before exploring further.

The Windows XP Developer Portfolio is a static React SPA with no backend dependencies. The steps below take you from an empty directory to a fully running local development server, then walk through the one-file content customization workflow you will use to make the portfolio your own.
The GitHub repository at apursley2012/windows-xp-developer contains the compiled Vite build output deployed to GitHub Pages — not the original Vite source project. It has no package.json, no src/ directory, and no vite.config.js. The development workflow below applies to the original Vite source project that produced this output. If you want to run or extend the portfolio locally, you will need to reconstruct (or obtain) the source project and run these commands against that codebase.

​
Run locally

1

Check prerequisites

You need Node.js 18 or later and a package manager. Confirm your versions before cloning:
node -v   # should print v18.x.x or higher
npm -v    # or: yarn -v / pnpm -v
If Node is not installed, download it from nodejs.org or use a version manager such as nvm or fnm.
2

Clone the repository

Clone the project from GitHub and move into the project directory:
git clone https://github.com/apursley2012/windows-xp-developer.git && cd windows-xp-developer
This clones the compiled static output. The steps below assume you are working with the original Vite source project. If you are only browsing the deployed output, you can open index.html directly or push the repo to GitHub Pages as-is.
3

Install dependencies

In the original Vite source project, install all required packages with your preferred package manager:
npm install
This resolves React, Vite, React Router v6, Framer Motion, Tailwind CSS, and all peer dependencies listed in package.json.
4

Start the development server

Launch the Vite dev server with hot-module replacement:
npm run dev
Vite will print a local URL — by default http://localhost:5173 — and open it automatically. You should see the Windows XP desktop background with the Taskbar at the bottom of the screen.
5

Build for production

When you are ready to deploy, generate an optimised static bundle:
npm run build
Vite compiles and minifies everything into the dist/ folder. The output mirrors the structure of the deployed repo — index.html, assets/, and components/ — ready to be pushed to a GitHub Pages branch or any static host.
6

Preview the production build

Before deploying, you can serve the dist/ output locally to catch any build-time differences:
npm run preview
This spins up a lightweight static server at http://localhost:4173 (by default) that serves the production bundle exactly as a static host would.

​
Customize your content

All portfolio content — your name, biography, project list, skills, work history, case studies, articles, and testimonials — is stored as plain JavaScript arrays and objects defined directly inside the page components. In the compiled output these live inside assets/main.js; in the original Vite source they are colocated inside each JSX page file. To update the content in the original source project, open the relevant page file and search for the data arrays. Common patterns to look for: 
// Skills page
const skills = [
  { name: "React", level: 90 },
  { name: "TypeScript", level: 85 },
  // ...
];

// Projects page
const projects = [
  {
    title: "My Project",
    description: "A short description.",
    stack: ["React", "Node.js"],
    url: "https://github.com/you/project",
  },
  // ...
];

// About / Home page
const bio = {
  name: "Your Name",
  tagline: "Full-stack developer & open-source contributor",
};
Use your editor’s global search (Ctrl+Shift+F / Cmd+Shift+F) and search for const skills, const projects, const workHistory, or const testimonials to jump straight to each data definition.

​
Pages and their data shapes

PageData variable to edit
Home / Aboutbio, name, tagline
Projectsprojects array
Skillsskills array
Work HistoryworkHistory array
Case StudiescaseStudies array
Articlesarticles array
Testimonialstestimonials array
ContactcontactLinks / email string
After editing, save the file and the Vite dev server will hot-reload the page instantly. When you are happy with the content, run npm run build to produce a fresh production bundle.

Build docs developers (and LLMs) love

Get started for freeTalk to us