# Team Meetings Our regular meeting cadence keeps everyone aligned without overwhelming calendars. ## Recurring Meetings ### Daily Standup - **When:** Weekdays, 9:30 AM - **Duration:** 15 minutes - **Format:** Each person shares: what they did, what they are doing, any blockers - **Where:** #standup Slack channel (async option available) ### Sprint Planning - **When:** Every other Monday, 10:00 AM - **Duration:** 1 hour - **Purpose:** Review backlog, estimate, and commit to sprint work ### Retr…
API Design Standards
# API Design Standards Our REST API follows consistent conventions for predictability and developer experience. ## URL Structure ``` GET /api/v1/resources # List POST /api/v1/resources # Create GET /api/v1/resources/:id # Read PATCH /api/v1/resources/:id # Update DELETE /api/v1/resources/:id # Delete ``` ## Response Format All responses follow this envelope: ```json { "data": { }, "meta": { "total": 42, "page": 1, "per_page": 20 } } ``` ## Error Responses ```json { "error": { "code": "VALIDATIO…
New Hire Onboarding
# New Hire Onboarding Welcome to the team! This guide will walk you through your first week. ## Day 1 Checklist - Set up your development environment - Get access to GitHub, Slack, and project management tools - Meet your onboarding buddy - Read through the Engineering Handbook section ## Day 2-3 - Clone the main repositories - Run the project locally - Complete the starter task assigned to you - Attend team standup ## First Week - Ship your first PR - Familiarize yourself with the codebase arc…
Deployment Process
# Deployment Process We deploy to production multiple times per day using a continuous deployment pipeline. ## Environments | Environment | Branch | URL | Auto-deploy | |-------------|--------|-----|-------------| | Development | `dev` | dev.example.com | Yes | | Staging | `staging` | staging.example.com | Yes | | Production | `main` | example.com | Yes (with checks) | ## Pipeline Stages 1. **Build** — Compile TypeScript, bundle assets 2. **Test** — Unit tests, integration tests, E2E tests 3. *…
Development Setup
# Development Environment Setup Follow these steps to set up your local development environment. ## Prerequisites - **Node.js** v20+ (recommend using `nvm`) - **Docker** and Docker Compose - **Git** 2.40+ - **VS Code** (recommended editor) ## Quick Start ```bash # Clone the repo git clone git@github.com:team/project.git cd project # Install dependencies npm install # Copy environment config cp .env.example .env.local # Start the database docker compose up -d postgres redis # Run migrations npm …
Incident Response
# Incident Response When things go wrong, follow this process to resolve incidents quickly and learn from them. ## Severity Levels | Level | Description | Response Time | |-------|-------------|---------------| | **P0** | Full outage, data loss | Immediate | | **P1** | Major feature broken, many users affected | **Golden rule:** Mitigate first, investigate later. Get the service back up before digging into root cause.
Code Review Guidelines
# Code Review Guidelines Code reviews are a core part of our engineering culture. Every change goes through review before merging. ## For Authors ### Before Requesting Review 1. **Self-review** your diff before requesting review 2. **Write a clear PR description** explaining what changed and why 3. **Keep PRs small** — aim for under 400 lines changed 4. **Add tests** for new functionality 5. **Ensure CI passes** before requesting review ### PR Description Template ```markdown ## What Brief desc…
Welcome to the Wiki
# Welcome to the Team Wiki This is your team's central knowledge base. Here you'll find documentation on processes, engineering practices, and everything you need to get up to speed. ## How to Use This Wiki - **Browse** using the sidebar navigation, organized by category - **Search** for docs by title or content using the search bar - **Share** links to specific docs — each page has a unique URL ## Contributing Docs are managed through the CMS data API. To add or edit content, use the Visimade …