do.dev Documentation Hub

Welcome to the do.dev monorepo documentation. This directory contains all technical documentation organized by category for easy navigation.

🚨 CRITICAL - READ FIRST

Before doing ANY work on this project, you MUST read these documents:

  1. TENETS.md - Core development principles that guide every decision
  2. development/GIT_PREFERENCES.md - Git workflow (commit = git add -A, NEVER push without permission)
  3. development/TYPESCRIPT_BEST_PRACTICES.md - TypeScript guidelines (ESSENTIAL for Vercel deployment)
  4. architecture/CONVEX_MULTI_PROJECT_ARCHITECTURE.md - Multi-Convex architecture (REQUIRED for any Convex work)

📂 Documentation Structure

🏗️ Architecture

System design, architecture decisions, and structural documentation.

🔐 Authentication

Everything related to authentication, authorization, and user management.

🛠️ Development

Development guidelines, standards, and best practices.

🌐 Infrastructure

Deployment, hosting, and infrastructure configuration.

Features

Feature-specific documentation and implementation guides.

🗄️ Archive

Older documentation kept for historical reference.

🚀 Quick Start Guides

For New Developers

  1. Read the Git Preferences
  2. Review TypeScript Best Practices
  3. Understand the Project Structure
  4. Check Codebase Status

For Authentication Work

  1. Start with Authentication README
  2. Review Convex Multi-Project Architecture
  3. Follow relevant setup guides in the authentication folder

For Deployment

  1. Read Vercel Deployment Guide
  2. Configure environment variables per authentication docs
  3. Test TypeScript compilation locally first

📊 Documentation Stats

  • Active Documents: 44 (was 52)
  • Archived Documents: 16
  • Categories: 5 main categories + archive
  • Last Major Cleanup: January 26, 2025
  • Cleanup Results: Archived 14 outdated documents (27% reduction)
    • Completed migrations: 5 docs
    • Resolved issues: 3 docs
    • Superseded designs: 4 docs
    • Bug reports: 1 doc
    • Duplicate content: 1 doc

🔍 Finding Documentation

By Topic

By Task

💡 Documentation Guidelines

  1. Keep docs close to code - Feature docs in feature folders when possible
  2. Use clear naming - Descriptive filenames in CAPS_WITH_UNDERSCORES.md
  3. Update when changing code - Documentation is part of the PR
  4. Archive don't delete - Move outdated docs to archive folder
  5. Cross-reference - Link between related documents

Remember: Good documentation is as important as good code. Keep it updated! 📚

On this page