Skip to project content

StudEd

A subscription-based educational platform for Sri Lankan students in Grades 1–11 and O/L and A/L programmes, powered by Go microservices, a React and TypeScript frontend, and GraphQL and gRPC APIs.

Role
Contributor — Course Service and mobile frontend
Category
Cloud-native learning platform
Timeline
July 2026 – August 2026
StudEd learning platform landing page
StudEd interactive learning wave
StudEd learner pricing plans

Project overview

01

The challenge

Contribute across a distributed, cloud-native platform while keeping service contracts reliable and ensuring that content-rich learning experiences remained clear, responsive, and touch-friendly on mobile devices.

02

The outcome

Across 23 commits, I expanded the Course Service and its gateway integration, improved enrollment and error-state handling, delivered mobile navigation and safe-area-aware layouts, and optimized interactive learning tools across the public and authenticated experiences.

Deliverables

  1. 01Course Service domain models and persistence
  2. 02gRPC-to-GraphQL gateway integration
  3. 03Responsive mobile learning experiences
  4. 04Enrollment and workflow reliability improvements
  5. 05Visualization submodules and code-quality standards

Project access

github.comStudEdA subscription-based educational platform for Sri Lankan students in Grades 1–11 and O/L and A/L programmes, powered by Go microservices, a React and TypeScript frontend, and GraphQL and gRPC APIs.View live demo

Contributors

  • Malin Dhamsara
  • Waruna Udara
  • Vidun Thamuditha Perera
  • Gehan Malshan

Technical details

Cloud-native learning platform

StudEd is a subscription-based educational platform designed for Sri Lankan students from Grades 1–11 through O/L and A/L. Its architecture supports a modern learning experience while keeping the system maintainable, independently deployable, and ready to scale as its content and user base grow.

Domain-focused Go microservices

The backend is divided into focused Go services rather than a single monolith. An API Gateway exposes the primary GraphQL interface, while dedicated Auth, Course, Progress, Gamification, AI, Payment, Notification, and Upload services own their respective domains and communicate through clearly defined contracts.

Course Service and API integration

My backend contribution focused on core Course Service components, including database migrations, lesson and wave data models, and repository access layers. I also updated the course-domain Protobuf and gRPC contracts, integrated the Course Service client into the API Gateway, and connected its operations to GraphQL schemas and resolvers.

Mobile learning experience

On the React, TypeScript, and TanStack Router frontend, I built the mobile navigation drawer and safe-area-aware layout chrome for educator and student shells. I optimized the Wave Player, quizzes, code blocks, physics simulations, landing page, course catalogue, student portal, and leaderboard for smaller screens and touch interaction.

Workflow reliability and visualizations

I corrected enrollment flows so unenrolled students could inspect and join courses directly, added clear error states across educator and student workflows, and configured the Math-to-Manim, 3Dmol.js, tscircuit, and Matter.js visualization submodules. I also applied consistent formatting standards across the codebase.

Platform engineering

The wider platform combines Kubernetes orchestration, OpenTofu infrastructure definitions, GitOps delivery, observability, cloud security, and local cloud emulation. Together, these practices support an environment that is easier to develop, deploy, monitor, and evolve as independent services grow.

Tech stack

  • Go
  • React
  • TypeScript
  • TanStack
  • GraphQL
  • Kubernetes
  • OpenTofu

Final thoughts

StudEd became a practical lesson in building a product across service boundaries rather than treating the backend and frontend as separate concerns. Delivering reliable course data, gateway contracts, mobile navigation, interactive learning tools, and cloud-native infrastructure required each layer to evolve as part of one coherent platform.

What I learned

  1. 01

    How to design and extend Go microservices through explicit domain models, repository layers, Protobuf contracts, and gateway integrations.

  2. 02

    How to adapt complex learning interfaces and interactive visualizations for touch input, safe areas, and constrained mobile screens.

  3. 03

    How Kubernetes, infrastructure as code, GitOps, observability, and local cloud emulation support dependable cloud-native development.