How activist-org/activist works
Project type and purpose
• This is a full-stack, open-source activism platform (“activist.org”) comprised of:
• A Nuxt 3/Vue 3 SPA/SSR frontend (TypeScript, Tailwind CSS, i18n)
• A Django REST API backend (multiple Django “apps” for auth, communities, content, events, utils)
• A PostgreSQL database and Redis for caching/session support
• Containerized deployment (Docker Compose), CI/CD pipelines (GitHub Actions, Netlify), and integrations (Plausible analytics, Weblate, Matrix chat).
File structure
• Top-level directories:
• backend/ → Django project subdivided into core, authentication, communities, content, events, utils, management commands, settings, migrations, tests
• frontend/ → Nuxt 3 project with pages/, components/, composables/, stores/, test suites (Vitest, Playwright), configuration files (nuxt.config.ts, tailwind.config.ts)
• .github/ & workflows → CI definitions for backend, frontend, i18n, security scans
• docker-compose.yml + Dockerfiles → local dev orchestration
• Architectural patterns:
• Django’s MVC (apps as modules) feeding a REST API
• Nuxt’s filesystem-based routing and component hierarchy
• Clear separation of concerns: UI vs. business logic vs. data layer
• Deployment/infra artifacts: Docker Compose, Netlify site for frontend, Django admin & Swagger UI, external translation service (Weblate), analytics (Plausible).
Extract extra insights from the README
• Tech stack recap: Django 5, Nuxt 3, Vue 3, Tailwind 3, PostgreSQL, Docker, Netlify, Vitest, Weblate, Plausible
• Features/modules: Organizations, Events, Resources, Discussions, Tasks, Affiliations, Votes
• CI: GitHub Actions for linting, tests, security scans, E2E
• Developer tools: pre-commit hooks, Matrix chat, Figma designs
a. Main components:
• Client (browser/mobile)
• Frontend (Nuxt 3 Server + SPA)
• API Gateway / REST API (Django)
• Data stores: PostgreSQL, Redis
• Media storage (local mount or S3-style)
• External services: Plausible, Weblate, Matrix, Figma (design), GitHub Actions, Netlify
• Docker Compose orchestrator / containers
b. Relationships and data flow:
• Client → Frontend (HTTP/HTTPS)
• Frontend → Django API (JSON over HTTP)
• Django → PostgreSQL (SQL)
• Django → Redis (caching, sessions)
• Frontend & Django → External services (analytics, i18n, chat)
• CI pipelines → Build & deploy Frontend to Netlify, Backend Docker images
c. Architectural patterns & design principles:
• Monolithic Django API with modular apps (separate “subsystems” for auth, communities, content, events)
• Component-driven UI (Vue components + composables)
• Containerization for isolation & reproducible dev/test/prod environments
• Clear separation: presentation vs. business vs. persistence layers
• Automated CI/CD and security scanning
d. Key technologies & libraries:
• Frontend: Nuxt 3, Vue 3, TypeScript, Tailwind, Headless UI, Playwright, Vitest
• Backend: Django REST Framework, PostgreSQL, Redis, Docker, pre-commit, Celery? (if used)
• DevOps: Docker Compose, GitHub Actions, Netlify, OWASP ZAP, Zap local scans
• i18n: Nuxt I18n + Weblate
• Analytics: Plausible
Elements
• Blue for UI/browser components
• Green for application servers/services
• Orange for data stores
• Gray for external third-party services
Detail without over-splitting
• I18n pipeline: source code → Weblate → localized assets delivered by frontend.
• Management/CI flow: GitHub Actions → Docker images → deploy to Netlify (frontend) & hosting (backend).
• Testing layers: Vitest (frontend), Pytest (backend), Playwright E2E.