How nathanvogel/relations-watch works
Main System Components
a) Frontend Layer:
• React/TypeScript Single Page Application
• Key modules:
• Graph Visualization (D3.js)
• Entity Management
• Relationship Management
• User Interface Components
• State Management (Redux)
b) Backend Layer:
• ArangoDB with Foxx Services
• Graph API Service
• Reverse Proxy (Nginx)
c) External Services:
• Wikidata Integration
• Firebase (for hosting)
Component Relationships
[Frontend (React/TS)] ←→ [Nginx Reverse Proxy] ←→ [ArangoDB Foxx Services] ←→ [ArangoDB Graph Database]
• ↕ ↕
[Firebase Hosting] [Wikidata API]
Detailed Component Breakdown
• Blue rectangles for frontend components
• Green rectangles for backend services
• Yellow diamonds for databases
• Grey rectangles for external services
Frontend (React/TypeScript):
[Components] → [Features/Redux] → [API Layer]
• ↑ ↕ ↕
[D3 Graph] ← [State Management] → [Utils]
Backend (ArangoDB/Foxx):
[Nginx Reverse Proxy]
• ↓
[Graph API Service]
• ↙ ↘
[Entities] [Relations]
• ↓
• [ArangoDB Store]
Important Details
a) Frontend Architecture:
• Redux store structure
• Component hierarchy
• Routing system
• Internationalization (i18n)
• Styled-components theming
b) Backend Architecture:
• API endpoints
• Data models
• Graph structure
• Migration system
Technical Stack Callouts
• TypeScript/JavaScript
• React
• Redux
• D3.js
• ArangoDB
• Foxx Services
• Nginx
• Styled-components
Development Environment
A separate section showing:
• Local development setup
• Production deployment
• API configuration options
• Database setup
This system design should reflect the collaborative nature of the platform while emphasizing the technical architecture that enables efficient relationship visualization and management.