URS - Roosloot.com

Version: 1.5
Date: March 8, 2026
Author: Rens Roosloot

1. Purpose

This document captures the user requirements for roosloot.com.

The site goal is to present personal work in a clear, safe, fast, and maintainable way.

In scope:

Public static website in site/
Home, projects hub, project detail pages, visuals hub, work page, contact section
Dutch/English language toggle
Shared visual style and reusable template
V-model documentation set and rendered public docs in site/docs/
Project-level documentation entry pages for major game and visual sets
Automated IQ/OQ verification evidence for release decisions

Out of scope:

FR-01: The site shall provide a homepage with concise introduction and featured content.
FR-02: The site shall provide a dedicated projects hub (projects.html) with categorized project listings.
FR-03: The site shall provide dedicated detail pages per project where relevant.
FR-04: The site shall provide a work section/page with professional links and references.
FR-05: The site shall provide contact access via email.
FR-06: The site shall support Dutch and English text for all user-facing content.
FR-07: The language preference shall persist across pages via local storage.
FR-08: The brand element in the top-left shall always navigate to index.html.
FR-09: The project shall maintain a V-model documentation chain (URS.md -> FS.md -> DS.md) plus supporting verification/risk documents (RISK_ASSESSMENT.md, TEST_PLAN.md, IQ.md, OQ.md, AGENTS.md).
FR-10: Each controlled markdown document shall have a rendered HTML mirror in site/docs/ for public reference.
FR-11: Any new functionality shall update all affected documentation in the same change.
FR-12: The site shall provide a dedicated visuals.html hub for interactive visual experiments and their detail pages.
FR-13: The public docs area shall expose project-level documentation entry pages for major project families such as games and visuals.

NFR-01 (Security): No client-side secrets or API keys shall be present.
NFR-02 (Security): Third-party embeds/scripts shall be avoided unless explicitly approved.
NFR-03 (Performance): The site shall remain static-first, lightweight, and fast-loading.
NFR-04 (Maintainability): Shared patterns shall be centralized (styles.css, i18n.js, templates/site-template.html).
NFR-05 (Accessibility): Navigation and interactive controls shall remain keyboard-usable and labeled.
NFR-06 (UX): Content shall be scannable with clear hierarchy and card-based grouping.
NFR-07 (Traceability): Requirements, functional behavior, design decisions, risk controls, and verification evidence shall remain traceable across URS/FS/DS/Risk/Test/IQ/OQ.

Static HTML/CSS/JS only (no CMS, no runtime backend).
One shared style sheet (site/styles.css) and shared i18n helper (site/i18n.js).
Dedicated projects hub with segmentation:
- Software & AI
- Home Automation
- Photography
- Visuals
- LEGO
Homepage kept focused with featured cards and links to full overviews.
Dark visual theme with subtle animated background and gradients, with readable typography.

AC-01: All pages load without JavaScript errors in modern browsers.
AC-02: Language toggle updates labels/content and persists between page loads.
AC-03: Projects navigation points to projects.html consistently.
AC-04: Header brand links to index.html on every page.
AC-05: Core pages remain readable and responsive on mobile widths.
AC-06: All controlled markdown docs are mirrored in site/docs/ and remain synchronized.
AC-07: IQ/OQ automated checks pass for release candidates.
AC-08: Functional changes include corresponding updates in impacted specification and verification documents.
AC-09: visuals.html, site/docs/index.html, and project-level docs entry pages remain reachable and internally consistent.

Visual requirement clarification: site/visuals-ascii-star-runner.html shall support a side-view parallax mountain scene with a UFO craft, optional ASCII mountain texturing, and adjustable mountain groove length/width controls.
UX requirement clarification: the UFO craft shall keep a fixed horizontal position and terrain-follow vertically, while mountain and foreground layers preserve clear depth separation.
Content requirement clarification: page copy shall describe the visual as a homage to the Amiga / Commodore 64 demoscene aesthetic.

Exploration requirement clarification: the repository may host a hand-built browser game prototype page for validating new interaction concepts before public navigation integration.
Prototype requirement clarification: a local co-op shared-control platformer concept shall support two players controlling one character on one keyboard using split inputs and at least one control-remap event.
Prototype media requirement clarification: game audio may be generated procedurally in-browser (Web Audio API) without external audio asset files.

Navigation requirement clarification: site/visuals.html shall act as the public hub for visual experiments, separate from the general projects hub.
Documentation information-architecture clarification: site/docs/index.html shall route visitors through project-level documentation entry pages instead of repeating all game/visual specs directly on the hub.
Visual project clarification: standalone visual experiments may keep their own rendered documentation subtree within site/ when linked from the docs hub.