TestLoom

Challenge

Exam preparation is usually fragmented. Notes live in one place, past papers in another, discussion happens somewhere else, and anything physical has to be manually re-entered before it becomes useful.

TestLoom tries to fix that by treating exam prep as a product system instead of a pile of utilities.

Approach

The platform combines OCR-driven question capture, organized question banks, adaptive quiz flows, forums, and progress analytics. The interesting part is not any single feature in isolation. It is the way the workflow connects:

• upload or scan material
• structure it into something searchable
• turn it into practice
• keep feedback loops visible

On the implementation side, the project uses a modern full-stack split: Nuxt and Vue on the frontend, Express and Node on the backend, MongoDB for storage, and TypeScript across the stack where it helps keep the surface area coherent.

Product shape

The repository shows real platform ambition without losing structure: OCR pipelines, analytics, study collaboration, auth, and deployment paths that can handle more than a demo.

The most convincing part of TestLoom is that it behaves like a system, not a feature showcase.

Why I keep it close

I keep it here because it brings product thinking, architecture, and execution into the same system. It is the kind of work where interface, backend, and workflow all have to pull in the same direction.