Education platform

Briquette LMS

A multi-tenant learning system for a bioinformatics course, shaped around roles, modules, submissions, and live communication.

Scope
Product, platform, and delivery
Role
Principal end-to-end author
Stack
React · TypeScript · Express · Drizzle · PostgreSQL · Socket.io

The problem

A technical course needed one dependable place for administrators, teachers, and students to move through content, work, feedback, and communication without losing the thread.

Decisions

  • Model roles and tenant boundaries before polishing screens.
  • Keep course modules, submissions, grading, and communication in one understandable flow.
  • Treat security, backups, and operational runbooks as part of the product.

Evidence

  • Distinct experiences for admin, teacher, and student responsibilities.
  • Module-scoped communication, materials, assignments, submissions, and feedback.
  • Typed full-stack architecture with tests, audits, and deployment documentation.

What I learned

  • A learning product is an orchestration problem before it is a component problem.
  • The most useful interface is often the one that makes the next responsibility obvious.

Keep going?

Let’s talk about the real problem.

Start a conversationjacksonochoa135@outlook.com