How gestjava/dashboard works
This is a browser-based dashboard command center for displaying configurable web pages in dashboard slots, with an optional local proxy for sites that block iframe embedding. The principal workflow is configuring slot URLs, displaying them in iframes, and saving or restoring configuration; carousel rotation and admin controls support that workflow. The source excerpt is partial and the README is empty, so the graph omits undocumented UI details and shows only evidenced wiring.
Main entry points: app.js Dashboard controller · index.html Iframe slots · proxy-server.js HTTP proxy server
Components 15
Dashboard interface
- Dashboard page
index.html - Dashboard controller
app.js - Admin controls
app.js - Live clock
app.js - Toast notifications
app.js
Slot runtime
- Slot configuration
app.js - Iframe slots
index.html - Iframe scaling
app.js - Lazy loading
app.js - Carousel configuration
app.js - Carousel rotation
app.js - Browser LocalStorage
Embedding proxy
- HTTP proxy server
proxy-server.js
Other components
- Dashboard operator
- Target websites
Connections 16
- Dashboard operator → Dashboard page: uses
- Dashboard page → Dashboard controller: loads
- Dashboard controller → Admin controls: toggles
- Dashboard controller → Live clock: updates
- Dashboard controller → Toast notifications: shows
- Dashboard controller → Slot configuration: updates
- Slot configuration → Iframe slots: sets URLs
- Dashboard controller → Iframe scaling: updates
- Dashboard controller → Lazy loading: observes slots
- Dashboard controller → Carousel configuration: updates
- Carousel configuration → Carousel rotation: starts or stops
- Carousel rotation → Iframe slots: changes URLs
- Dashboard controller → Browser LocalStorage: saves and loads
- Iframe slots → Target websites: loads pages
- Iframe slots → HTTP proxy server: may load proxied URL
- HTTP proxy server → Target websites: fetches and relays