Alvin Zilverstand — portfolio
A custom, bilingual static portfolio for VISTA college Heerlen. Dark project journal with project dossiers, repository links and a provisional SBB evidence index. No external fonts, tracking, framework, CMS, runtime API requests or production Node service.
Run locally
Requires Node 22 or newer. No dependency installation is necessary.
npm run dev
Open http://127.0.0.1:4173. Set PORT to change the port. The development server binds to loopback only.
npm test
npm run build
The build copies the five website files into dist/. It can be hosted at a domain root or a subdirectory. Hash-based routes mean no server fallback configuration is needed. Dutch is the default; ?lang=en#evidence opens English evidence navigation. Language switching preserves the current page.
Maintain content
See the codebase index for the file map and rendering dependencies.
Content editing stays on your computer. There is no public admin page or write API.
- Add a project: run
npm run project:add -- my-project. Open the newcontent/projects/my-project.jsonand replace the placeholder text. - Edit a project: open its file in
content/projects/. Text pairs are[Dutch, English]. Changenumberto change the display order; the first project is featured on the homepage. - Delete a project: delete its JSON file. Its project card and evidence-index entries disappear on the next preview refresh or build.
- Add/edit/delete an item: edit the project's
evidencearray. Copy an existing entry to add one, change its values to edit it, or remove the entry to delete it. An empty array[]is allowed. - Profile and processes: edit
content/settings.json.
An evidence item looks like this:
{
"label": ["Testverslag", "Test report"],
"path": "projects/my-project/tests.md",
"type": "MD",
"codes": ["B1-K1-W4"]
}
Use "directory": true for a folder. Paths are relative to the school repository. Keep project id values stable to preserve links. Use exactly three nodes for the system diagram. Project numbers and challenge numbers are strings.
Run npm run dev and refresh the browser to preview saved edits. Invalid content will prevent the preview content module from loading; run npm run content for a descriptive validation error. Run npm run build to validate and prepare publication. content.js is generated; do not edit it directly. npm run content regenerates it without building.
Only deploy dist/. Everything in the generated content is public, so keep credentials and private documents out of these files. Repository links remain pinned to the revision in content/settings.json; update it after reviewing a newer snapshot.
Finish the exam content
The interface is functional; the exam dossier is not yet complete. Summaries are based on the supplied school repository, not invented personal experience. Artifact paths were checked against the repository tree. DOCX contents were not reviewed and the source projects' test scripts were not executed.
Before submission, add your personal contribution and reflection for every case study, confirm solo/team context, include actual test results, and substantiate improvement claims. Add evidence for B1-K2-W1, W2 and W3 (collaboration, presentation and evaluation). The current mappings are suggestions, not assessment decisions. Ask the examiner which artifacts and authenticity statements VISTA requires. General subjects, electives and institution-specific requirements are outside this vocational index.
The source is SBB's 2024 qualification for Software Developer, code 25998: https://kwalificatie-mijn.s-bb.nl/Details/DownloadDocument/1963420
English process names are informal translations. Reviewed 9 November 2026.
Direct contact details, a CV, screenshots, assessed outcomes and personal reflections were not supplied, so the site does not invent them. Add these as real material becomes available. Project diagrams illustrate structure; they are not screenshots of running applications.
Host on Proxmox with Docker
See Docker hosting instructions for installation, network access, reverse proxies and content updates.
Run docker compose up -d --build from the repository on your Docker guest. Docker builds from the JSON source files; no manual build or Node installation is needed on the guest. The default binding is localhost only. Configure .env as described in the guide for LAN or proxy access.