Aug — Oct 2025 · ISTAD final project

CamboStack

A Q&A forum for ISTAD students & mentors

CamboStack is a Stack Overflow–style forum for the ISTAD community. Students post coding questions, mentors and classmates answer them, and the best answers rise to the top through voting, reputation and badges. It supports English and Khmer.

Demo video published by ISTAD

REST endpoints
129
lines of Java
9.2k
TypeScript files
330+
team commits
590+

01The problem

Why we built it

ISTAD students had no shared place to ask technical questions. Answers were lost in chat groups, mentors repeated the same explanations, and nobody could search what had already been solved. We wanted a searchable, moderated knowledge base that rewards people for helping each other.

02Frontend

Inside the UI

The main screens of the Next.js app and the components each one is built from. Pick a screen to see its layout and where its data comes from.

cambostack.app
<Navbar />
<HeroSection />
<VisualPreview />
<FeatureSection />
<StatsSection />

Landing page for guests with an animated hero, an overview of the platform and a sign-up call to action.

Data

  • I18nContext
  • next-themes

03How it's built

Follow one request

CamboStack is a monolith: one Next.js app talking to one Spring Boot API. Scroll to follow a request through every layer.

01 / 07 · The user

A student opens a question

Everything starts in the browser. The UI switches between English and Khmer and between light and dark themes without a reload.

GET cambostack.app/question/how-to-use-useeffect

Follow one request

Spring Boot API · one app/api/v1

Zooming in on the API

One app, split by feature

cambostack-api · Spring Boot14 modules · 1 PostgreSQL

  • Users & profiles
  • Questions
  • Answers
  • Comments
  • Votes
  • Reputation & badges
  • Tags
  • Bookmarks
  • Follows
  • Notifications
  • Search
  • Media
  • Reports
  • Drafts
  1. git tag v1.2.0
  2. GitHub Actions
  3. Docker Hub
  4. Google Cloud VM

04Features

What you can do on CamboStack

  • Ask & answer

    A rich TipTap editor with headings, code blocks with syntax highlighting, images, links and @mentions.

  • Drafts & scheduled posts

    Save a question as a draft or schedule it. A background job publishes due drafts every minute and indexes them for search.

  • Search

    Elasticsearch-powered search across questions, alongside tag filtering and trending questions.

  • Voting & reputation

    Upvotes and downvotes on questions and answers move the author's reputation. Reputation unlocks the right to vote.

  • Badges & leaderboard

    Gold, silver and bronze badges reward contributors, and a top-contributors leaderboard ranks the community.

  • Accepted answers

    The question author marks the answer that solved the problem, so readers find it first.

  • Social layer

    Follow users, bookmark questions, mention mentors and get notified in real time.

  • Moderation

    Users report content, and admins approve or reject reports, pin questions and post announcements.

  • Accounts

    Register, verify by email or OTP, and log in through Keycloak. Students can request mentor or graduate status.

05Tech stack

What it's built with

Frontend

  • Next.js 15 (App Router, Turbopack)
  • React 19
  • TypeScript
  • Tailwind CSS v4
  • shadcn/ui + Radix
  • Redux Toolkit
  • SWR + Axios
  • NextAuth (Keycloak)
  • TipTap editor
  • next-intl (EN / KM)
  • Framer Motion

Backend

  • Java 21
  • Spring Boot 3.5
  • Spring Data JPA
  • Spring Security (OAuth2 resource server)
  • Keycloak Admin Client
  • MapStruct
  • Lombok
  • Bean Validation
  • Spring Scheduling
  • Spring WebSocket (STOMP)
  • springdoc OpenAPI

Data & services

  • PostgreSQL
  • Elasticsearch 8
  • MinIO
  • Spring Mail + Thymeleaf

Delivery

  • Docker
  • GitHub Actions
  • Docker Hub
  • Google Cloud VM

06Under the hood

How a few parts work

Registering a user across two systems

  1. 1The API creates the account in Keycloak first and gets back its Keycloak id.
  2. 2It then saves a local user and an empty profile in PostgreSQL, linked by that id.
  3. 3Keycloak sends the verification email.
  4. 4If any local step fails, the API deletes the Keycloak user again, so the two systems never drift apart.

Casting a vote

  1. 1The API rejects votes on your own post.
  2. 2It checks reputation: 15 points to upvote, 125 to downvote.
  3. 3Repeating the same vote does nothing. Switching from up to down reverts the old reputation change before applying the new one.
  4. 4Voter and author are saved in one transaction, so reputation always matches the votes.

Publishing a scheduled question

  1. 1A question saved with a publish time stays a draft.
  2. 2Every minute, a scheduled job finds drafts whose time has passed.
  3. 3Each one is published in PostgreSQL and then indexed into Elasticsearch asynchronously, so search stays fast without slowing the job.

07Shipping

From commit to production

  1. 01The frontend is packaged as a multi-stage Docker image.
  2. 02Pushing a version tag such as v1.2.0 starts a GitHub Actions workflow.
  3. 03The workflow builds the image, pushes it to Docker Hub and deploys it to a Google Cloud VM over SSH.
  4. 04The API was served at api.cambostack.codes with Swagger docs, and the site at cambostack.app.

08My role

Presenting CamboStack

I presented CamboStack on behalf of our team, showing the audience what we built, why it matters and how it works. These are the parts of the project I walked them through.

  1. 01

    The problem

    Why ISTAD students needed one searchable place to ask questions instead of losing answers in chat groups.

  2. 02

    The platform in action

    Asking and answering questions, voting, accepting the best answer, earning badges and climbing the leaderboard.

  3. 03

    How it's built

    The path of a request from the Next.js frontend through Keycloak login to the Spring Boot API and PostgreSQL.

  4. 04

    Our teamwork

    How we split the features across frontend and backend and brought them together through one shared REST API.

CamboStack was built by a team of ISTAD Full-Stack Web Development students. We split the work by feature across the frontend and backend and integrated through the shared REST API documented in Swagger.