teambeat2 Svelte Themes

Teambeat2

Teambeat retrospective tool rewritten entirely in SvelteKit and Svelte 5

Download

TeamBeat - Collaborative Retrospectives

A modern, real-time collaborative retrospective tool built with SvelteKit 5 and SQLite.

Features

  • Real-time Collaboration - SSE-powered real-time synchronization for 40+ concurrent users
  • Authentication System - Local username/password authentication with session management
  • Board Series Management - Organize retrospectives in series with role-based access control
  • Multi-phase Workflow - Structured meeting phases with facilitator controls
  • Card Management - Create, edit, group, and vote on retrospective cards
  • Smart Voting System - Configurable vote allocation with facilitator dashboard
  • Scene Management - Control meeting phases with customizable permissions
  • Presence Tracking - See who's actively participating in real-time
  • Timer System - Meeting timers with extension voting capabilities

Architecture

  • Frontend: SvelteKit 5 with custom design system (LESS)
  • Backend: SvelteKit API routes with TypeScript
  • Database: SQLite with Drizzle ORM
  • Real-time: Server-Side Events (same port as HTTP)
  • Authentication: Session-based with secure cookies

Quick Start

# Install dependencies
npm install

# Set up database
npm run db:migrate

# Start development server
npm run dev

The application will be available at http://localhost:5173

Docker Deployment

Quick Docker Start

Use the provided docker-compose.yml for easy deployment:

# Build and start the application
docker-compose up --build

# Run in background
docker-compose up -d --build

The application will be available at http://localhost:3000 with the database persisted in ./db/teambeat.db.

Manual Docker Build

# Build the Docker image
docker build -t teambeat .

# Create database directory
mkdir -p ./db

# Run the container
docker run -d \
  --name teambeat \
  -p 3000:3000 \
  -v $(pwd)/db:/db \
  -e DATABASE_URL=/db/teambeat.db \
  teambeat

Docker Configuration

The Dockerfile uses a multi-stage build:

  • Stage 1: Install dependencies
  • Stage 2: Build the application
  • Stage 3: Create optimized runtime image with Node.js

Key features:

  • SQLite database mounted at /db directory
  • Non-root user for security
  • Health checks for container monitoring
  • Automatic database migration on startup
  • Port 3000 exposed by default

Environment Variables

  • DATABASE_URL: Path to SQLite database file (default: /db/teambeat.db)
  • PORT: Application port (default: 3000)
  • NODE_ENV: Environment mode (set to production in container)

Volume Mounts

  • /db: Database directory (required for data persistence)
  • /app/logs: Application logs (optional)

Database Commands

# Generate migration from schema changes
npm run db:generate

# Apply migrations
npm run db:migrate

# Open database studio
npm run db:studio

Project Structure

src/
├── lib/
│   ├── server/
│   │   ├── db/              # Database schema and connection
│   │   ├── repositories/    # Data access layer
│   │   ├── sse/             # Server-Side Events handling
│   │   └── auth/            # Authentication & sessions
│   ├── components/          # Reusable UI components
│   │   └── ui/              # Base UI components
│   ├── stores/              # Client-side state management
│   ├── utils/               # Shared utilities
│   └── assets/              # Static assets
├── routes/
│   ├── api/                 # REST API endpoints
│   ├── board/[id]/          # Board interface
│   ├── login/               # Authentication pages
│   └── register/
├── app.html                 # Root HTML template
└── app.less                 # Global styles

API Endpoints

Authentication

  • POST /api/auth/register - Create account
  • POST /api/auth/login - Sign in
  • POST /api/auth/logout - Sign out
  • GET /api/auth/me - Get current user
  • PUT /api/auth/profile - Update user profile
  • PUT /api/auth/change-password - Change password
  • DELETE /api/auth/delete-account - Delete user account

Board Series

  • GET /api/series - List user's series
  • POST /api/series - Create new series
  • GET /api/series/[id] - Get series details
  • PUT /api/series/[id] - Update series
  • DELETE /api/series/[id] - Delete series
  • GET /api/series/[id]/users - Get series users
  • POST /api/series/[id]/users - Add user to series

Boards

  • GET /api/boards - List user's recent boards
  • POST /api/boards - Create new board
  • GET /api/boards/[id] - Get board details
  • PUT /api/boards/[id] - Update board
  • DELETE /api/boards/[id] - Delete board
  • POST /api/boards/[id]/clone - Clone board
  • PUT /api/boards/[id]/scene - Change current scene
  • PUT /api/boards/[id]/setup-template - Setup board template

Scenes & Columns

  • GET /api/boards/[id]/scenes - Get board scenes
  • POST /api/boards/[id]/scenes - Create scene
  • PUT /api/boards/[id]/scenes/[sceneId] - Update scene
  • DELETE /api/boards/[id]/scenes/[sceneId] - Delete scene
  • PUT /api/boards/[id]/scenes/reorder - Reorder scenes
  • GET /api/boards/[id]/columns - Get board columns
  • POST /api/boards/[id]/columns - Create column
  • PUT /api/boards/[id]/columns/[columnId] - Update column
  • DELETE /api/boards/[id]/columns/[columnId] - Delete column
  • PUT /api/boards/[id]/columns/reorder - Reorder columns

Cards & Voting

  • GET /api/boards/[id]/cards - Get all cards for board
  • POST /api/boards/[id]/cards - Create new card
  • PUT /api/cards/[id] - Update card content
  • DELETE /api/cards/[id] - Delete card
  • PUT /api/cards/[id]/move - Move card between columns
  • PUT /api/cards/[id]/group - Group cards together
  • PUT /api/cards/[id]/group-onto - Group card onto another
  • POST /api/cards/[id]/vote - Toggle vote on card
  • GET /api/boards/[id]/voting-stats - Facilitator voting dashboard

Real-time Features

  • GET /api/sse - Server-Side Events endpoint
  • PUT /api/boards/[id]/presence - Update user presence
  • POST /api/boards/[id]/timer - Start/vote on timer
  • DELETE /api/boards/[id]/timer - Stop timer

Templates

  • GET /api/templates - Get available board templates

SSE Events

The application uses Server-Side Events streamed on the same port as the web application for real-time updates:

  • card_created - New card added
  • card_updated - Card content changed
  • card_deleted - Card removed
  • vote_changed - Vote count updated
  • scene_changed - Meeting phase changed
  • timer_update - Timer status changed
  • presence_update - User activity changed
  • board_updated - Board settings changed
  • columns_updated - Column configuration changed
  • comment_added - New comment added
  • user_joined - User joined board
  • user_left - User left board

Development Status

This is a functional MVP implementation covering all core retrospective features:

  • Authentication and user management
  • Board series organization with roles
  • Real-time card creation, editing, and voting
  • Multi-phase meeting workflow
  • Drag-and-drop card organization
  • Facilitator controls and voting dashboard
  • SSE-powered sync collaboration
  • Timer system with extension voting
  • Presence tracking

Future Enhancements

  • AI-powered card grouping
  • Team health check system
  • Action item tracking with assignments
  • Resolution carryover between boards
  • Enhanced rich text editing (replace textarea)
  • Mobile-responsive improvements
  • SSO/OAuth integration

Built according to CLAUDE.md development guidelines emphasizing explicit over implicit code, libraries over custom solutions, and human-maintainable architecture.

License

MIT License. See LICENSE file for details.

The DiceBear avatar style Adventurer is a remix of: Adventurer by Lisa Wischofsky, licensed under CC BY 4.0.

Top categories

tailwinddaisyuiadmin templatepopupmdsvexportfolioblogformecommerceuicarouselauthdarkseoimagerouting
Loading Svelte Themes