How cisneros-f/bocadillos works
Bocatas is a browser-based sandwich-ordering app with a team ordering view and an administrator view. Users load their team’s daily menu, place or update an order, and see unpaid balances; administrators manage whether ordering is open, mark orders paid, and collect outstanding balances. Both views send actions through the app’s API caller. A service worker caches the app shell for offline launch, while order data remains network-only. The excerpts show the client-side workflows, but not the backend implementation or the HTML wiring.
Main entry points: app.js Team order view · sw.js Service worker
Components 14
Team ordering
- Team order view
app.js - Team code and name
app.js - Daily menu and order
app.js - Unpaid balances
app.js
Administration
- Admin dashboard
app.js - Order controls
app.js - Payment tracking
app.js
App runtime
- API caller
app.js - Service worker
sw.js - Cached app shell
sw.js
Other components
- Team member
- Administrator
- Apps Script API
- Browser local storage
Connections 17
- Team member → Team order view: uses
app.js - Team order view → Team code and name: loads code
app.js - Team order view → Daily menu and order: renders
app.js - Team order view → API caller: requests data
app.js - Team order view → API caller: submits order
app.js - Team order view → Unpaid balances: renders
app.js - Team code and name → Browser local storage: reads and writes
app.js - Administrator → Admin dashboard: uses
app.js - Admin dashboard → API caller: loads dashboard
app.js - Admin dashboard → Order controls: dispatches actions
app.js - Admin dashboard → Payment tracking: dispatches actions
app.js - Admin dashboard → Browser local storage: reads code
app.js - Order controls → API caller: sends actions
app.js - Payment tracking → API caller: sends actions
app.js - API caller → Apps Script API: posts actions
app.js - Service worker → Cached app shell: caches assets
sw.js - Team order view → Service worker: registers
app.js