How anishkasinghal/grove works
Grove is a student-life dashboard spanning academics, tasks, habits, study, journaling, finance, calendar, stats and settings. The browser boots by loading state, then routes views to renderers; user actions are handled by the event layer and state persists locally. The backend exposes account and user-data APIs backed by PostgreSQL, but the README marks frontend authentication and persistent sync as work in progress. The map retains documented modules whose detailed implementation is unsampled; edges are limited to visible or explicitly documented relationships.
Main entry points: app.js Express API · index.js Server startup · router.js View routing · db.js Postgres pool
Components 17
Student Dashboard
- App boot
js/main.js - View routing
js/router.js - Dashboard modules
js/render.js - View actions
js/events.js - Shared state
js/state.js - Local persistence
js/db.js - Date utilities
js/utils.js - Sign-in UI
js/auth.js
API and Accounts
- Express API
server/app.js - Token security
server/auth.js - User defaults
server/defaults.js - Runtime config
server/config.js - Server startup
server/index.js
Persistence
- Postgres pool
server/db.js - PostgreSQL
Other components
- Student
- Google OAuth
Connections 20
- Student → View routing: selects views
js/router.js - App boot → Local persistence: loads data
- App boot → View routing: routes after load
js/main.js - View routing → Dashboard modules: renders view
js/router.js - View routing → View actions: wires view
js/router.js - View actions → Shared state: updates state
- Dashboard modules → Shared state: reads dashboard data
js/render.js - Dashboard modules → Date utilities: uses date helpers
- Sign-in UI → Express API: requests auth
- Sign-in UI → Local persistence: reloads data
- Server startup → Runtime config: loads settings
server/index.js - Server startup → Postgres pool: creates pool
server/index.js - Server startup → Express API: creates app
server/index.js - Server startup → Postgres pool: runs migration
server/index.js - Postgres pool → Runtime config: validates connection
server/db.js - Postgres pool → PostgreSQL: queries
server/db.js - Express API → Token security: uses auth helpers
server/app.js - Express API → User defaults: loads data defaults
server/app.js - Express API → PostgreSQL: reads and writes
server/app.js - Express API → Google OAuth: OAuth sign-in
README.md