Skip to main content

Documentation Index

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

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

Starting Mystery Haunting in development mode gives you the full spooky experience in your browser — complete with Framer Motion page transitions, ghost particle effects, and the Creepster-font atmosphere — all with Vite’s hot module replacement (HMR) keeping every change reflected instantly without a full page reload. This is the fastest way to explore and iterate on the portfolio locally.

​
Start the Dev Server

From the project root, run: 
npm run dev
Vite will spin up a local dev server and print the address to your terminal. Open your browser to http://localhost:5173 to see the site live. Any changes you save to source files are reflected in the browser within milliseconds thanks to HMR — no manual refresh required.

​
Available Scripts

The project ships with three npm scripts for the full develop → build → preview workflow:
ScriptCommandDescription
devviteStart the development server with hot module replacement
buildvite buildBuild an optimised production bundle to dist/
previewvite previewServe the production build locally for final testing

​
Static Page Exports

The pages/ directory contains individual pre-rendered HTML entry points for every route in the portfolio. These files are used by Vite to generate separate pages for static hosting, enabling direct URL access to each section without relying on a catch-all redirect:
FileRoute
pages/Landing.html/landing — Landing page
pages/About.html/about — About section
pages/Projects.html/projects — Projects showcase
pages/Work.html/work — Work experience
pages/Skills.html/skills — Skills overview
pages/CaseStudies.html/case-studies — Case studies
pages/Blog.html/blog — Blog posts
pages/Testimonials.html/testimonials — Testimonials
pages/Contact.html/contact — Contact form

​
Testing the Production Build

Always run npm run preview after npm run build to verify the production bundle behaves correctly before deploying. The preview server mirrors a real static host and will catch any asset path or routing issues that don’t surface in dev mode.
npm run build && npm run preview

​
Deploying the Built Site

Once you’ve run npm run build, the dist/ folder contains a fully self-contained static site ready to deploy. It can be hosted on any static platform — GitHub Pages, Netlify, Vercel, or any CDN that serves HTML files. 
# Install the gh-pages helper if you haven't already
npm install --save-dev gh-pages

# Add this to your package.json scripts:
# "deploy": "gh-pages -d dist"

npm run build
npm run deploy

Build docs developers (and LLMs) love

Get started for freeTalk to us