FS

Volledige gerenderde weergave van FS.md.

Laatst gesynchroniseerd: 13 april 2026

FS - Roosloot.com

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

1. Purpose

This Functional Specification (FS) translates URS.md requirements into explicit, testable functional behavior.

2. Scope

In scope:

  • Static website behavior in site/
  • Page navigation and content behavior
  • Language toggle behavior
  • Documentation page behavior (docs/)
  • Visual hub/detail behavior

Out of scope:

  • Backend services
  • User authentication/authorization
  • CMS workflows

3. Functional Behavior

FS-01 Homepage

  • The homepage (site/index.html) shall provide:
    • concise introduction
    • featured projects section
    • work section
    • contact section

FS-02 Projects Hub

  • site/projects.html shall list project categories and link to project detail pages.

FS-03 Visuals Hub

  • site/visuals.html shall list visual experiments and link to their detail pages.

FS-04 Project Detail Pages

  • Each listed project or visual shall have a reachable detail page or target URL.

FS-05 Work Content

  • site/work.html and homepage work cards shall provide professional links and internal work navigation.

FS-06 Contact

  • Contact entry points shall include a working mailto: link.

FS-07 Global Navigation

  • Header links shall navigate to:
    • index.html#about
    • projects.html
    • work.html
    • index.html#contact
  • Brand shall always link to index.html.

FS-08 Language Toggle

  • A language toggle shall be available on all primary pages.
  • Toggle shall switch NL/EN content bound to i18n keys.
  • Selected language shall persist via localStorage.

FS-09 Documentation Pages

  • site/docs/index.html shall provide entry points for core docs, game docs, and visual docs.
  • Major project documentation sets shall expose one public entry page per project where relevant, including site/docs/swapbound.html and site/voxel-cutaway-world/docs/index.html.
  • Rendered documentation pages shall be reachable in site/docs/:
    • urs.html
    • fs.html
    • ds.html
    • risk-assessment.html
    • test-plan.html
    • iq.html
    • oq.html
    • agents.html

FS-10 Deployable Boundary

  • All production runtime functionality shall resolve from within site/.
  • Reusable authoring templates may live outside site/, but they shall not be exposed as public website pages.

FS-11 Documentation Change Control

  • Functional scope changes shall update impacted V-model docs in the same change:
    • URS.md
    • FS.md
    • DS.md
    • RISK_ASSESSMENT.md
    • TEST_PLAN.md
    • IQ.md
    • OQ.md
    • AGENTS.md
  • Updated markdown docs shall be rendered to matching pages in site/docs/ via npm run docs:render.

FS-12 Verification Execution

  • Release-candidate changes shall be verified through automated checks:
    • npm run test:e2e
  • IQ and OQ outcomes shall be reflected in IQ.md and OQ.md.

4. Functional Traceability

  • FR-01 -> FS-01
  • FR-02 -> FS-02
  • FR-03 -> FS-04
  • FR-04 -> FS-05
  • FR-05 -> FS-06
  • FR-06 -> FS-08
  • FR-07 -> FS-08
  • FR-08 -> FS-07
  • FR-09 -> FS-09, FS-11
  • FR-10 -> FS-09, FS-11
  • FR-11 -> FS-11, FS-12
  • FR-12 -> FS-03, FS-04
  • FR-13 -> FS-09

5. Acceptance Notes

Each FS item shall be linked to one or more OQ and/or IQ checks in OQ.md and IQ.md.

6. Change Addendum (2026-02-25)

  • site/visuals-ascii-star-runner.html shall render a layered parallax scene (sky/clouds, far mountains, mid mountains, ASCII foreground terrain).
  • The UFO craft shall remain horizontally fixed and adjust vertical position relative to foreground terrain height.
  • Controls shall include ASCII density, parallax speed, hill height, flight clearance, follow response, ASCII mountain toggle, mountain groove length, and mountain groove width.
  • Mountain groove rendering shall remain visually stable during scrolling (no obvious jitter/flicker under normal parameter ranges).

7. Change Addendum (2026-02-25, Game Prototype Branch)

  • site/swapbound/game.html may implement a hand-built local co-op prototype separate from published project navigation while gameplay mechanics are still being validated.
  • The prototype functional scope includes split-control character movement, checkpoints/respawn, one movable block puzzle, one switch/bridge interaction, one control-remap trigger, and one exit/win condition.
  • Prototype test features may include developer-facing room jump controls to accelerate manual iteration without affecting the core mechanic.

8. Change Addendum (2026-03-08, Visuals and Docs IA)

  • site/visuals.html shall serve as the public hub for visual experiments, including site/voxel-cutaway-world/index.html.
  • site/docs/index.html shall link to project-level documentation pages instead of repeating individual game/visual spec links directly in the hub cards.
  • Project-local documentation pages may be published outside site/docs/ when they belong to a standalone project subtree and remain reachable from the docs hub.
Terug naar home