How papua-opensource/dapoer-papoea works
Main Components
a) Frontend Architecture:
• Static Site Generator (AstroJS) as the core
• Client-side Components
• Routing System
• Asset Management
b) Data Management:
• JSON Data Store
• Static Content
• Image Assets
[Client Browser] <---> [Static Host]
• v
[Build Process (AstroJS)]
[Pages] [Components] [Assets]
[Data Store (JSON)] [Static Files]
Component Relationships
a) Core Components:
• Layout System (src/layouts)
• Page Components (src/pages)
• Reusable Components (src/components)
• Data Sources (src/data)
b) Static Assets:
• Public Directory (public/gambar)
• Image Categories (buku, ilustrasi, menu-harian)
Specific Implementation Details
Key architectural elements:
[File-based Routing]
• v
[Pages Layer]
• Dynamic Routes ([category]/[slug])
• Static Routes (kata-pengantar, tentang)
• v
[Layout Layer]
• Base Layout
• Component Composition
• v
[Component Layer]
• Navigation (Navbar, ChapterNavigation)
• Content (Hero, ArrowCard)
• Structure (BaseHead, Footer)
• v
[Data Layer]
• chapters.json
• recipes.json
Build Process Flow
Build process:
[Source Files] -> [AstroJS Build] -> [Static Output]
[TailwindCSS] -> [Optimization] -> [Deployment]
Important Notes
• Static nature of the final output
• Clear separation between build-time and runtime components
• Where TailwindCSS and Preline UI integrate
• Entry points for content management
• How dynamic routing is handled