Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/apursley2012/digital-domain/llms.txt

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

Digital Domain ships as a fully pre-built static site — the compiled assets/ directory is already committed to the repository alongside the component files and HTML entry point. This means you can deploy immediately to GitHub Pages or any static host without installing dependencies or running a build step. Follow the steps below to get from a fresh clone to a live site.

​
Prerequisites

Before you begin, make sure you have the following installed:
  • Git — to clone the repository
  • A static file server (optional) — to preview the site locally before deploying. Any tool that can serve static files works, for example npx serve (requires Node.js) or the VS Code Live Server extension.

​
Deploy to GitHub Pages

1

Clone the repository

Clone the Digital Domain repository from GitHub and change into the project directory:
git clone https://github.com/apursley2012/digital-domain.git && cd digital-domain
2

Push to your GitHub Pages branch

The repository root is already deployable. Push it to a gh-pages branch (or configure GitHub Pages to serve from the main branch root) in your repository settings:
git push origin main
GitHub Pages will serve index.html from the repo root. The .nojekyll file in the root disables Jekyll processing, ensuring assets/ paths resolve correctly.

​
Preview Locally

1

Clone the repository

git clone https://github.com/apursley2012/digital-domain.git && cd digital-domain
2

Serve the site with a static file server

Because the site uses ES modules loaded via <script type="module">, you must serve it over HTTP rather than opening index.html directly as a file:// URL. Any local static server works:
npx serve .
This starts a server at http://localhost:3000 (or the next available port). Open the URL in your browser to see the site.
The repository already includes a pre-built assets/ directory (assets/main.js, assets/proxy.js, and assets/main.css) alongside the component ES modules. No npm install or build command is required — the project source used to produce these files is not committed to the repository.

​
Customising Content

All page logic is compiled into assets/main.js. Because assets/main.js is the final Vite bundle, you should not edit it directly — it is minified and not intended for hand-editing. To change the navigation links, you can edit components/Layout.js. The nav items are defined in the sd array near the top of the file — each entry has a path and a label property that controls what appears in the top nav bar: 
const sd = [
  { path: "/", label: "Home" },
  { path: "/about", label: "About Me" },
  { path: "/projects", label: "Projects" },
  // ... additional routes
];
For deeper customisation (page content, routing, styling), you would need access to the original Vite source that produced the assets/ bundle. The compiled output in this repository does not include the original JSX source files.
The pages/*.html stubs allow direct navigation to specific routes (for example, bookmarking pages/About.html) by setting window.location.hash to the correct route before React boots. You can add additional stubs for any new routes you introduce by following the same pattern.

Build docs developers (and LLMs) love

Get started for freeTalk to us