How kingsdigitallab/kings-past works
Main System Components
a) Frontend Layer
• SvelteKit Application
• Routes & Pages
• Components
• Static Assets
• Search Functionality (Pagefind)
b) Data Layer
• Supabase (PostgreSQL)
• Content Management
• Markdown Files
• Frontmatter
• Schema.org Data Models
c) Integration Layer
• API Endpoints
• Database Clients
• External Services
Component Relationships
a) Frontend Architecture (Top Layer):
[Client Browser] → [SvelteKit App]
• [Static Pages]
• [Dynamic Routes]
• [Components]
• [Search Index]
b) Data Flow Architecture (Middle Layer):
[Markdown Content] ←→ [SvelteKit SSG] ←→ [Supabase]
• ↓
• [Static Assets]
c) Database Architecture (Bottom Layer):
[Supabase PostgreSQL]
• [People]
• [Organizations]
• [Places]
• [Events]
• [Donations]
• [Moments]
• [Themes]
Specific Implementation Details
• Blue Rectangles: Core Components
• Green Rectangles: Data Stores
• Yellow Diamonds: Integration Points
• Red Hexagons: External Services
• Purple Circles: Static Assets
Key Relationships to Highlight
• Static site generation process
• Demonstrate the search functionality flow
• How the MapLibre GL integration works with place data
Technical Stack Indicators
Technology badges or labels for:
• SvelteKit
• Supabase
• MapLibre GL
• Pagefind
• Schema.org
• Mdsvex
Data Flow Patterns
• Content generation flow
• API request patterns
• Search query flow
• Data integration
• Static asset delivery