How silentsilas/playground works
Main Components
a) Frontend Layer:
• SvelteKit Application
• Main App Routes ((app) directory)
• Legacy Routes ((legacy) directory)
• Editor Route
• Projects Route
• 3D Scene Components (src/lib/components/scenes)
• UI Components (src/lib/components)
b) Server Layer:
• API Routes (/api)
• Poetry Endpoint
• Thoughts Endpoint
• Search Endpoint
• RSS Feeds
• Server-side Routes
c) Data Layer:
• Markdown Posts
• Poetry Collection
• Thoughts Collection
• Vector Embeddings Store
• Static Assets (images, textures)
Component Relationships
[Client Browser] ←→ [SvelteKit Frontend]
• ↓
[SvelteKit Frontend] ←→ [Server-Side Routes]
• ↓
[Server-Side Routes] ←→ [API Layer]
• ↓
[API Layer] ←→ [Data Layer (MD Files + Embeddings)]
[Markdown Files] → [Embeddings Generator] → [embeddings.json]
[Search Query] → [Vector Search] → [Results]
[.md files] → [SvelteKit SSR] → [Rendered Content]
Important Elements to Highlight
• The 3D scene system (World.svelte, Planet.svelte, etc.)
• The search functionality with vector embeddings
• Content management system (poetry and thoughts)
• RSS feed generation
• Theme toggling system
Technical Stack Indicators
• SvelteKit
• TypeScript
• Tailwind CSS
• Three.js (implied by 3D components)
• Markdown Processing
• Vector Embeddings
Additional Notes
• Separation between app, legacy, and editor routes
• How the static assets are served
• Different content license zones (MIT vs CC BY-NC-SA-4.0)
• Relationship between the editor and content generation