Research software portfolio

Research tools, workflow systems and interactive methods.

A curated view of the systems behind my academic and technical work: ProtocolDock, browser-based task delivery, LaTeX writing infrastructure, participant workflows, governance records, data exports and analysis support.

Core technical identity

Research software that follows the actual research workflow

The portfolio is organised around the same idea that drives ProtocolDock: research work should not be split across scattered documents, spreadsheets, task links, email threads, consent files, and fragile exports.

Full-stack platform development React, Vite, Tailwind, Node, Express, Prisma, PostgreSQL, authentication, admin tooling and deployment planning.
Research workflow design Study setup, participant routes, consent, forms, eligibility screening, bookings, exports, versioning and governance records.
Academic writing infrastructure In-browser LaTeX projects, compilation, citations, source management, comments, version history and PDF output.
07

Block 17: Contraband Empire

An isometric risk-management logistics game concept built around covert routes, heat, inspections, co-opted buildings and systemic network exposure.

Game designIsometricRisk systemsGodot
Featured build

ProtocolDock

ProtocolDock is the main software artefact: a hosted research workspace for study management, writing, participant workflows, task delivery, governance and structured research administration.

protocoldock.com
ProtocolDock Dashboard Studies Write Forms Consent Exports
Study workspace Live project record with writing, forms, consent, tasks and exports linked.
Study setup Consent Forms Task Export
Branching formsEligibility, declarations, questionnaires
JavaScript taskBrowser task builder and preview
CSV exportsResponses, events, metadata
Audit trailVersions, roles, governance trace

What it demonstrates

ProtocolDock demonstrates end-to-end software design in a research context: database modelling, role-based access, public participant routes, researcher dashboards, writing infrastructure, versioning, exports and admin controls.

  • Study-owned signup flows with consent, forms, eligibility and participant routes.
  • JavaScript task builder for self-contained browser-based research tasks.
  • Usage-limited free data collection for small projects, pilots and early-stage work.
  • LaTeX writing environment with compile routes, citations, assets, source ZIP and version history.
  • Governance and operational records that remain attached to the project.
Capabilities

Portfolio areas

01

Study and participant workflow

Structured study records, participant-facing routes, consent linkage, eligibility screening, branching forms, booking records and exports.

Study lifecycleConsentFormsCSV
02

JavaScript task builder

Browser-based task delivery intended to make smaller studies and pilot tasks possible without stitching together external tools.

JavaScriptTasksTrialsExports
03

ProtocolDock Write

LaTeX project creation, import, source editing, citations, assets, PDF compilation, comments, reviewer routes and version history.

LaTeXPDFBibLaTeXVersioning
04

Governance infrastructure

Ethics records, consent versions, roles, audit trails, maintenance notices, institutional seat structures and admin visibility.

GovernanceRolesAuditAdmin
05

Experimental demos

Interactive research demos that translate psychophysics, gaze timing and visual instability into accessible browser experiences.

PsychophysicsTimingCanvasUX
06

Research analysis tooling

Eye-tracking, scanpath, fixation, saccade, trial-quality and export workflows developed around actual research datasets.

PythonMATLABEye trackingQC
Why this matters

The software work is part of the research profile

My research asks how people make structured judgements from brief perceptual evidence. My software work has a parallel concern: how researchers manage structured evidence across time, files, participants, documents, and governance records.

That overlap is the point. The same person building experimental tasks, writing tools and data exports is also the person who has to understand why the workflow must be defensible later.

Interactive Lab Try the gaze timing challenge, workflow builder and visual instability demo. Launch demos