Data & code offboarding checklist (Raes Lab, VIB)

Live site: https://raeslab.github.io/offboarding/ · Repository: https://github.com/raeslab/offboarding

A static website where lab members who leave can confirm that all of their research data and code has been handed over properly. They fill in the questionnaire, download a timestamped PDF report, and send it to their supervisor. The site is part of the lab's off-boarding procedure.

• No backend. The site is plain HTML/CSS/JavaScript in docs/, hosted on GitHub Pages.
• Resume later. Answers are saved automatically in the browser's localStorage, so people can close the tab and continue later on the same computer and browser.
• Private. Nothing is sent anywhere. Only the PDF that the user downloads leaves their computer.
• VIB look & feel. It uses VIB colours, the VIB logo and VIB's body font Nunito Sans. All of these are vendored, so there are no CDNs at runtime.

Screenshots

The questionnaire. The sidebar shows your progress and the items that are still open.

If items are still open when you export, the site lists them first. You can still download the PDF.

The form also works on a phone.

All screenshots use made-up demo data. To regenerate them, run npm run screenshots and then uv run python scripts/render_pdf.py docs/img/report.pdf --scale 2. Keep only report-p1.png.

What is asked

1. General
   • Name, u-number, VSC account (or "I don't have one"), supervisor and last working day.
   • Explicit confirmation that no research data is left on the person's personal OneDrive.
   • Explicit confirmation that no data or code is left in private GitLab repositories. Projects must be moved to the raeslab namespace by a maintainer.
2. Projects (repeatable). For each project:
   • Name, and who takes over (if known).
   • Locations of raw data, processed data and code. Location types are Tier1, Tier2-staging, GitLab or Other (Other must be specified). Each location needs a path or URL. A category can have several locations, or be marked "Not applicable".
   • Four quick Yes/No questions. The detailed fields only appear for "Yes", which keeps the form fast:
     • Sensitive / personal data (GDPR)? → where the pseudonymisation keys are stored.
     • Anything published? → type, repository, DOI/accession, licence (one row per output).
     • Specific retention or deletion requirements? → retention period and deletion requirements.
     • Depositions required? → whether they are all done (Yes/Partially/No), and a comment if not.
3. Code checklist (covers all repositories)
   • Each repository has a README.md.
   • Software versions are pinned (renv / venv / conda / containers).
   • Example data is included.
   • Each item is answered Yes / Partially / No / N/A. Any answer other than "Yes" needs an explanation in the comments field.

Validation is soft. Missing or odd answers (e.g. a u-number that does not match u + 7 digits) appear as open items in the sidebar and inline. The PDF can still be exported, but open items are highlighted in orange and listed at the end of the report.

The PDF file is named Offboarding_<Name>_<u-number>_<YYYY-MM-DD>.pdf. It contains the date and time of generation on the first page and in the footer of every page.

Repository layout

docs/                     ← the website (GitHub Pages root)
  index.html
  css/style.css
  js/config.js            ← all texts, options, tooltips, patterns (edit here)
  js/model.js             ← data model + validation (no DOM; unit-testable)
  js/pdf.js               ← PDF report (jsPDF + autotable)
  js/logo.js              ← VIB logo as vector paths for the PDF
  js/app.js               ← UI, autosave, export
  assets/                 ← VIB logos + favicons (from vib.be)
  img/                    ← README screenshots (tests/make_screenshots.js)
  vendor/jspdf/           ← jsPDF + jspdf-autotable (MIT)
  vendor/fonts/           ← Nunito Sans TTFs (SIL OFL)
scripts/fetch_vendor.py   ← (re)downloads everything in docs/vendor and docs/assets
tests/                    ← Playwright end-to-end tests + tiny static server

Development environment (VS Code dev container)

The repository includes a dev container with these tools:

• Debian 13
• uv with Python 3.14
• Node 24
• Playwright with Chromium
• Claude Code

Requirements: Docker Desktop and VS Code with the Dev Containers extension (ms-vscode-remote.remote-containers).

To set it up:

1. Open the folder in VS Code.
2. Run Dev Containers: Reopen in Container from the Command Palette (Ctrl+Shift+P).
3. Wait for the first build. It takes a few minutes. Afterwards, uv sync and npm install run automatically.

Task	Command
(Re)vendor third-party files	uv run python scripts/fetch_vendor.py
Serve the site on :4173 (forwarded to the host)	npm run serve
End-to-end tests	npm test
Sample PDFs without a browser	npm run pdf:samples
README screenshots → docs/img/	npm run screenshots
Render PDFs to PNG for review	uv run python scripts/render_pdf.py test-results/samples/*.pdf
Lint Python	uv run ruff check scripts

Commit uv.lock and package-lock.json after the first uv sync / npm install.

Run locally

Any static file server will do:

node tests/serve.js            # http://localhost:4173
# or
python -m http.server 4173 -d docs

Opening docs/index.html directly from disk (file://) also works. In that case the browser blocks loading the font files for the PDF, so the PDF falls back to Helvetica. Over http(s), Nunito Sans is embedded.

This is the beginning of the README. Read the rest at the original. Read the full README ↗