How keevingfu/creative works
Project Type and Purpose
• From the structure (“frontend/”, “api/”, “docker-compose.yml”, “init-mongo.js”), we see this is a full-stack web application.
• The “api/” folder contains an Express server plus models; “frontend/” holds static assets and a simple Node server; MongoDB is initialized via “init-mongo.js”; there is an n8n workflow for automation.
File Structure
• Top-level:
• api/ – backend code (models/creative.js, server.js)
• frontend/ – UI assets (html/, css/, server.js)
• n8n_workflow/ – workflow automations
• creativedoc/ – documentation
• docker-compose.yml & Dockerfiles – container definitions
• init-mongo.js – DB initialization
• setup.sh, deploy.sh – environment and deployment scripts
• Patterns: clear separation of concerns (presentation vs. data vs. automation).
Extract Architecture Insights from README
• The README is minimal, but the file layout and scripts point to:
• A multi-container deployment via Docker Compose
• A Node.js/Express REST API
• A MongoDB database
• A simple Node-based static file server for the frontend
• n8n for workflow or integration tasks
Main Components
a. User’s Web Browser (UI)
b. Frontend Web Server (frontend/server.js + static files)
c. Backend API Server (api/server.js + models)
d. MongoDB Database (initialized via init-mongo.js)
e. n8n Workflow Engine (n8n_workflow)
f. Deployment Orchestrator (docker-compose + setup.sh, deploy.sh)
Relationships & Data Flows
• Browser → HTTP requests → Frontend Server (serves HTML/CSS/JS)
• Frontend Server → REST API calls → API Server
• API Server → Database driver → MongoDB
• n8n → triggers API endpoints or database hooks → Workflow tasks
• docker-compose → brings up Frontend, API, MongoDB, n8n as separate containers
Architectural Patterns & Technologies
• Layered, client-server pattern
• RESTful API
• Micro-services style via separate containers
• Data persistence with MongoDB
• CI/CD or deployment scripting with shell scripts
• Containerization (Docker, Docker Compose)