Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/apursley2012/dev.void/llms.txt

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

dev.void is distributed as a pre-built static site — the repository contains compiled Vite output (assets/, components/, pages/, index.html) rather than raw JSX source files. There is no package.json, no node_modules, and no build step required. To run it you simply open index.html directly or serve the folder with any static file server.
1

Check Prerequisites

You only need git to clone the repository. No Node.js or package manager is required to view the portfolio — it is already compiled.Verify git is installed:
git --version
If you want to serve the site over a local HTTP server (recommended for React Router’s client-side routing to work correctly), you can use any static server. Python’s built-in server, the serve npm package, or VS Code’s Live Server extension all work.
2

Clone the Repository

Clone dev.void from GitHub and navigate into the project folder:
git clone https://github.com/apursley2012/dev.void.git && cd dev.void
You will see the following top-level structure:
dev.void/
├── assets/          # Vite-compiled JS + CSS bundles
├── components/      # Compiled React component modules
├── pages/           # Pre-rendered static HTML pages
├── images/          # Screenshots and static assets
└── index.html       # App entry point — mounts the React root
The files in assets/ and components/ are Vite build output — compiled and minified ES modules, not raw JSX source files. There is no package.json or src/ directory in this repository. To make deep structural changes you would need access to the original JSX source and a Vite build environment. For text and data edits (names, taglines, copy), the compiled modules are directly editable as plain text.
3

Open the Site

Option A — Direct file open (simplest):Double-click index.html, or open it in your browser with File → Open File. The portfolio will load immediately. Note that React Router’s client-side navigation may not resolve deep URLs (e.g. /about) when opened via file:// — use Option B if you need full routing support.Option B — Local static server (recommended):Serve the folder with any static HTTP server. Using Python (no install required on macOS/Linux):
python3 -m http.server 8080
Then open http://localhost:8080 in your browser.Alternatively, if you have Node.js available, use npx serve:
npx serve .
You should see the full space-themed portfolio with the animated starfield background, the custom CometCursor comet cursor, and the AuroraHero hero section displaying the name Alex Vance.
4

Make Your First Customization — Change the Hero Name

The hero section is rendered by components/AuroraHero.js. The name Alex Vance is hardcoded in the compiled output as a string literal inside the <h1> element.Open components/AuroraHero.js in your editor and find the <h1> content:
// Locate this section in components/AuroraHero.js
// (search for the string "Alex Vance" in the file)
children: "Alex Vance"
Replace "Alex Vance" with your own name:
children: "Your Name"
Save the file and reload the page in your browser. Your name will appear in the gradient hero heading.You should also update the tagline just below the name. Find the <h2> element containing:
children: "Architecting nebulas of code in the digital void."
And replace it with your own tagline.
Because there is no dev server, changes require a manual browser refresh — there is no hot-reload. Simply save the file and press F5 or Cmd/Ctrl + R to see your changes.

​
What’s Next

All text and data edits — name, tagline, project titles, skill labels, work history, contact details — can be made directly in the compiled files under components/. Each component is a self-contained compiled module; search for the string you want to change and replace it in place. No build step is needed after editing.
Here are the recommended next steps after your first customization:
  • Profile Data — A complete guide to updating your bio, skills, project cards, work timeline, and contact details across all components.
  • Project Structure — Understand how the compiled assets/ and components/ files map to each section of the portfolio.
  • AuroraHero Component — Deep-dive into the hero section’s aurora blob animations, CTA buttons, and scroll indicator.
  • Color Palette — Swap out the aurora color tokens and Google Fonts families to create your own visual identity.

Build docs developers (and LLMs) love

Get started for freeTalk to us