This guide takes you from zero to a running development server and shows you exactly where to put your own content. You do not need to touch any component code for basic customization — all portfolio data lives in five plain JavaScript files.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/apursley2012/sys.witch-v2/llms.txt
Use this file to discover all available pages before exploring further.
Fork the repository
Go to https://github.com/apursley2012/sys.witch-v2 and click Fork in the top-right corner. This creates a copy of the repo under your own GitHub account, which you will later use for GitHub Pages deployment.
Start the dev server
Launch the Vite development server:Vite starts on http://localhost:5173 by default. The server supports hot module replacement — any changes you save to data files or components will reflect instantly in the browser without a full reload.
Open the portfolio
Visit http://localhost:5173 in your browser. You will land on the animated portal home screen. Use the navigation bar (or the full-screen mobile menu) to explore all seven sections:
- Portal — animated home with
PortalRingsigil - Origin — about / timeline
- Conjured Works — projects grid
- Arcana — skills by category
- Tomes — writing and articles
- Ritual Reports — case studies
- Cast Message — contact form and social links
Replace placeholder content
Thedata/ directory is the only place you need to make changes for basic customization. Each file exports a plain JavaScript array — open it, edit the objects, save, and the UI updates immediately.
| File | What it controls |
|---|---|
data/projects.js | Projects section — title, description, tech stack, links, and the associated sigil ID |
data/skills.js | Skills section — skill name, category, proficiency level, and display color |
data/writing.js | Writing section — article titles, summaries, channel tags, and external URLs |
data/caseStudies.js | Case Studies section — in-depth case study documents with problem, process, and outcome fields |
data/sigils.js | SVG sigil path map keyed by sigil ID — advanced, only needed if you want to add new sigil shapes |
Build for production
When you are ready to deploy, generate the static production bundle:dist/ directory. The output is a fully static site — upload the contents of dist/ to any static host, or push to your gh-pages branch to deploy via GitHub Pages.