This guide walks you through getting developer.exe running locally, building it for production, and deploying it as a static site. By the end you will have a live dev server showing the arcade portfolio atDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/apursley2012/developer-exe/llms.txt
Use this file to discover all available pages before exploring further.
localhost:5173, a production-ready dist/ bundle, and a clear picture of how to make the site your own.
Prerequisites — You need the following tools installed before you begin:
- Node.js 18+ — the Vite build system and all dependencies require Node 18 or later.
- npm 9+ (or an equivalent package manager such as pnpm or yarn) — used to install dependencies and run the project scripts.
Install all project dependencies with npm. This pulls in React, Vite, Tailwind CSS, Framer Motion, React Router, and every other package declared in
package.json:Launch the Vite dev server. It starts on port 5173 by default and supports hot module replacement, so changes to components, styles, and pages reflect in the browser instantly without a full reload:
Open http://localhost:5173 in your browser. You should see the arcade attract screen with the synthwave grid scrolling, the HUD displaying
LEVEL: ATTRACT MODE, and the CRT scanline overlay active.Vite bundles and fingerprints all JS and CSS assets into
dist/assets/, copies the pre-rendered HTML stubs from pages/ into the output, and writes the root index.html. The entire dist/ folder is self-contained and ready to serve from any static host.The
dist/ output is compatible with any static hosting provider. Because developer.exe uses hash-based routing (#/), no server-side redirect rules are required — every visitor receives the same HTML file and React Router handles the rest in the browser.GitHub Pages — push the
dist/ contents to a gh-pages branch (or configure Pages to serve from dist/ in your repo settings). The .nojekyll file in the repository root disables Jekyll processing, which would otherwise ignore files and folders prefixed with an underscore and corrupt the Vite asset paths.Customization
Change the neon color palette
Change the neon color palette
The three core neon values are declared as CSS custom properties on Edit these hex values to retheme the entire site at once.
:root near the bottom of assets/main.css, just before the body rule:--neon-green controls the primary HUD text color and the cursor crosshair stroke; --hot-magenta drives the glitch pseudo-element offsets, the scrollbar thumb, and text selection highlights; --electric-cyan appears in the secondary HUD line, GlitchText counter-shadow, and focus ring borders.Note that the Tailwind extended palette tokens (text-neon-green, bg-neon-magenta, etc.) are compiled to literal hex values in assets/main.css. If you want those utility classes to also reflect a color change, you would need to update the Tailwind configuration in the original source and rebuild the project with Vite.Add a new route
Add a new route
Adding a route involves three coordinated steps:1. Create the page component. Add a new file in your source components directory, for example 3. Create the static HTML stub. Copy an existing file from the Also update the
pages/Gallery.jsx. Export a default React component that renders the page content.2. Register the route in the router. In your app’s root component (the file that renders the <HashRouter>), import the new component and add a <Route> inside <Routes>:pages/ directory (for example, pages/About.html) and save it as pages/Gallery.html. Update the two occurrences of the route path in the inline script:<title> tag to match the new page name. After running npm run build, Vite will include the new stub in the output alongside the existing pages.Swap out content
Swap out content
The source code for developer.exe has been compiled and minified by Vite. The raw If you want to make the content genuinely editable, the recommended approach is to extract the original source from the compiled output and restructure the data into separate JSON or JS module files that are imported by the page components, then rebuild with Vite. This gives you clean separation between data and presentation going forward.
.jsx source files are not present in the repository — only the compiled bundles in assets/main.js and assets/proxy.js exist. Content such as the home hero headline, the projects array, the skills data, and writing post metadata is embedded directly in assets/main.js as inlined JavaScript strings and object literals.To locate a specific piece of content, search the minified bundle for a distinctive text fragment. For example, to find the hero headline: