How ecotrust/marco-portal2 works
Main Components
a) Frontend Layer:
• Static Assets (CSS, JavaScript, Images)
• Bootstrap-based UI components
• jQuery and other frontend libraries
• Ocean Story visualization components
b) Backend Layer:
• Django Web Framework
• Wagtail CMS
• Multiple Django Apps (portal, data_catalog, ocean_stories, etc.)
• Celery Task Queue
c) Data Storage:
• PostgreSQL Database
• Redis (for Celery and caching)
• Media Storage (for uploaded files)
d) External Services:
• Services
• Data Manager
• Authentication System
[Client Layer]
• ↑↓
[Web Server (Apache)]
• ↑↓
[Application Layer]
• Django/Wagtail
• Portal Apps
• Asset Pipeline
• ↑↓
[Service Layer]
• Celery Workers
• Redis
• PostgreSQL
Key Relationships
• Request flow from client through web server to application
• Data flow between Django apps and database
• Asset compilation and serving pipeline
• Task queue workflow with Celery and Redis
• Media file handling
• Data processing flow
Specific Implementation Details
• Home
• Ocean Stories
• Data Catalog
• Calendar
• News
• Pages
• Base
Connections between:
• Wagtail CMS and content management
• Static/Media file serving
• Database interactions
• Cache layer
• Task processing
Additional Elements
Annotations for:
• Development vs Production environments
• Security layers
• Backup systems
• Asset compilation pipeline
• Docker/Vagrant development setup