How divelarde/palagunitaan works
Palagunitaan is a heritage-contribution and discovery platform with role-based review and administration. The principal workflow is contributor submission, validation, and publication, followed by public browsing, map, and timeline discovery. The graph also includes authentication, editorial history, and documented blog/highlight/admin branches. Evidence is limited to the supplied excerpts and SOURCE INDEX; unsampled subsystems are represented at their existing directory paths, without speculative internal call links.
Main entry points: App.js Application router · axios.js HTTP client · reviewService.js Review workflow · heritageEntryModel.js Heritage entries
Components 27
Web client
- Application router
client/src/App.js - HTTP client
client/src/api/axios.js
Identity and access
- Client auth state
client/src/context/AuthContext.js - Auth routes
server/routes/authRoutes.js - Authentication service
server/services/authService.js - User records
server/models/userModel.js
Heritage workflow
- Entry submission
client/src/pages/SubmitEntryPage.js - Entry API
server/routes/heritageEntryRoutes.js - Entry controller
server/controllers/heritageEntryController.js - Entry processing
server/services/heritageEntryService.js - Heritage entries
server/models/heritageEntryModel.js - Review dashboard
client/src/pages/ValidatorDashboardPage.js - Review routes
server/routes/reviewRoutes.js - Review controller
server/controllers/reviewController.js - Review workflow
server/services/reviewService.js - Editorial history
server/models/editorialActionModel.js
Discovery and media
- Browse and detail
client/src/pages - Map exploration
client/src/pages/MapPage.js - Timeline view
client/src/pages/TimelinePage.js - Blog publishing
server/controllers/blogPostController.js - Featured highlights
server/controllers/highlightController.js
Administration
- Admin dashboard
client/src/pages/AdminDashboardPage.js - Admin routes
server/routes/adminRoutes.js - Content management
server/controllers/adminContentController.js - Notifications
server/services/notificationService.js - MySQL pool
server/config/db.js
Other components
- Platform user
Connections 34
- Platform user → Application router: uses
client/src/App.js - Application router → Client auth state: provides auth
client/src/App.js - Application router → Entry submission: routes to
client/src/App.js - Application router → Review dashboard: routes to
client/src/App.js - Application router → Admin dashboard: routes to
client/src/App.js - Application router → Browse and detail: routes to
client/src/App.js - Client auth state → HTTP client: uses
client/src/context/AuthContext.js - Application router → HTTP client: uses services
- Auth routes → Authentication service: delegates
- Authentication service → User records: reads and writes
server/services/authService.js - Entry submission → Entry API: submits via
- Entry API → Entry controller: routes to
server/routes/heritageEntryRoutes.js - Entry controller → Entry processing: delegates
server/controllers/heritageEntryController.js - Entry processing → Heritage entries: reads and writes
server/services/heritageEntryService.js - Entry processing → Heritage entries: persists entry
server/services/heritageEntryService.js - Review dashboard → Review routes: reviews via
- Review routes → Review controller: routes to
server/routes/reviewRoutes.js - Review controller → Review workflow: delegates
server/controllers/reviewController.js - Review workflow → Heritage entries: updates status
server/services/reviewService.js - Review controller → Editorial history: reads history
server/controllers/reviewController.js - Review workflow → Editorial history: records action
server/services/reviewService.js - Review workflow → Notifications: notifies decision
server/services/reviewService.js - Heritage entries → MySQL pool: queries
server/models/heritageEntryModel.js - Editorial history → MySQL pool: queries
server/models/editorialActionModel.js - User records → MySQL pool: queries
server/models/userModel.js - Browse and detail → HTTP client: fetches content
- Map exploration → HTTP client: fetches map data
- Timeline view → HTTP client: fetches timeline
- Application router → Blog publishing: loads blog service
client/src/App.js - Application router → Featured highlights: loads highlight service
client/src/App.js - Admin dashboard → Admin routes: uses admin API
- Admin routes → Content management: mounts content routes
server/routes/adminRoutes.js - Content management → MySQL pool: queries content
- Application router → Admin routes: mounts API