Skip to content

Flowcode Documentation Index

Last Updated: 2025-11-16 Documentation Version: 1.2.0 Scan Type: Exhaustive Full Rescan


Project Overview

  • Type: Monolithic Full-Stack Web Application
  • Primary Language: PHP 8.3 + TypeScript
  • Architecture: Multi-Tenant SaaS
  • Framework: Laravel 12 + Vue 3 + Inertia.js v2

Quick Reference

  • Tech Stack: Laravel 12 + Vue 3 + Filament 3 + Pinia + Tailwind CSS 3 + Vite
  • Entry Point: public/index.php (web), resources/ts/app.ts (frontend)
  • Architecture Pattern: Layered monolith with multi-panel admin
  • Codebase Size: 719 Vue components, 176 models, 98 controllers, 396 migrations

Generated Documentation

Core Documentation

Technical Documentation

  • API Contracts - All API endpoints, authentication, and data contracts
  • Data Models - 176 Eloquent models organized by domain

State & Progress


Existing Documentation

Authentication & Security

Business Decisions (ADRs)

Creator System

Domain Models Documentation

OPTT System

Indicators & Compliance

General System Features

Organizations

REMS (External Integration)

Releases & Changelog

Reporting

Testing

Assets

Other


Getting Started

For New Developers

  1. Environment Setup

    git clone https://github.com/salthq/flowcode.git
    cd flowcode
    composer install
    npm install
    cp .env.example .env
    php artisan key:generate
    php artisan migrate --seed
    

  2. Start Development

    npm run dev           # Frontend hot reload
    valet link flowcode   # Local server (Mac/Linux)
    valet secure flowcode # HTTPS
    

  3. Run Tests

    php artisan test      # All tests
    vendor/bin/pint       # Code formatting
    

For Feature Development

  1. Review Architecture Documentation for technical constraints
  2. Check API Contracts for existing endpoints
  3. Reference Data Models for domain understanding
  4. Follow patterns in existing codebase

For AI-Assisted Development

When creating PRDs or working with AI assistants: 1. Point to this index as the primary reference 2. Use Architecture for technical context 3. Reference specific domain docs as needed 4. Check existing patterns before introducing new ones


Documentation Maintenance

Generated by Exhaustive Scan

The following files were auto-generated on 2025-11-16: - project-overview.md - architecture.md - source-tree-analysis.md - development-guide.md - api-contracts.md - data-models.md - project-scan-report.json

Update Schedule

  • Major releases: Full rescan recommended
  • Significant feature additions: Deep-dive scan on affected areas
  • Routine maintenance: Keep existing docs current manually

Contribution

When adding new features: 1. Update relevant existing docs 2. Create new docs for major features 3. Add links to this index 4. Follow existing documentation patterns


  • Repository: github.com/salthq/flowcode
  • Main Branch: develop
  • CI/CD: GitHub Actions
  • Admin Panels: /admin-panel, /creator-panel, /org-panel
  • Health Check: /health
  • Monitoring: Laravel Pulse (production)

This documentation was generated using BMAD Method's Document Project Workflow (v1.2.0)