How ast4rt3/centralized_sas_repository works
1. The repository is a multi-app portal monorepo. The top-level “SAS Portal” is the central entry point, and apps/ contains specialized modules that are either standalone static apps or Google Apps Script-backed web apps.
2. The main portal shell lives at the repo root (index.html, app.js, styles.css, manifest.json, serviceWorker.js, version.json) and is mirrored under www/. That strongly suggests a static front-end bundle with a deployable copy in www/ for hosting targets that expect a web root.
3. A central configuration file, systems.json, likely drives the portal’s navigation and module registry. In architecture terms, this is the routing/launch boundary: the shell reads config, then opens systems or embeds them, rather than hardcoding every destination.
4. The portal is described as using integrated iFrames for module switching. So the main data flow is “portal shell → configuration → embedded module view,” which keeps the shell isolated from the internal implementation of each sub-app.
5. Aurora.js appears to be a shared client-side runtime/helper layer for the portal UI. It likely sits under the portal shell and supports common behaviors such as layout, module loading, or update/version handling.
6. The platform is built as a PWA. The root serviceWorker.js, manifest.json, and version.json indicate offline caching, installability, and a versioned update mechanism. The same pattern is repeated in apps/attendance-scanner/ with its own sw.js and manifest.json, so the scanner is an independent PWA boundary.
7. apps/attendance-viewer/ and apps/mailer/ are Google Apps Script applications. Each has a Code.gs server-side script plus a client app.js, HTML, and CSS, which means the UI is served from Apps Script and the server logic runs inside Google’s ecosystem rather than in a separate Node backend.
8. Those GAS-backed apps are the clearest backend integration points in the repo. Their boundary is “browser UI ↔ Apps Script runtime ↔ Google services,” which is distinct from the static portal shell that mostly acts as a launcher and presentation layer.
9. The README calls out announcement media, weather integration, and a TV-optimized immersive mode. Architecturally, that means the portal has a presentation subsystem for dashboards/tickers and external content embeds, separate from the administrative and data-management modules.
10. Security and admin behavior are concentrated in the portal/modules rather than in a centralized backend service. The README mentions login and confirmation gates for administrative actions, so authorization appears to be enforced within the Apps Script or client flow depending on the module.
11. Deployment is static-host oriented: .github/workflows/static.yml, vercel.json, env.example.js, and DEPLOYMENT_ENV.md point to environment-specific build/deploy configuration rather than a long-running server process. The architecture is therefore mostly client-side, with selective server-side logic in Google Apps Script.
12. In diagram terms, the main boundaries are: static portal shell; config-driven module launcher; standalone PWA module for attendance scanning; and Apps Script-backed CRUD/reporting apps for attendance viewing and mailing. Those are the primary subsystems and data paths to represent.
Main entry points: app.js Portal logic · index.html Portal UI · www/index.html Web root · attendance-scanner/index.html Scanner UI
Components 22
Portal shell
Static SAS Portal entry point and shared runtime
- Portal UI · Main portal landing page
index.html - Portal logic · Portal shell behavior and module launching
app.js - Portal styles · Shared portal presentation
styles.css - Aurora · Common UI/runtime helpers for the portal
Aurora.js - Systems map · Config-driven module registry and navigation
systems.json - Portal manifest · Installable app metadata
manifest.json - Portal SW · Offline caching and update support
serviceWorker.js - Version · Portal version marker used for update handling
version.json
Deploy mirror
Web-root copy of the portal for static hosting targets
- Web root · Mirrored portal entry for hosting
www/index.html - Mirror logic · Mirrored portal script bundle
www/app.js - Mirror styles · Mirrored portal styles
www/styles.css - Mirror SW · Mirrored offline/update worker
www/serviceWorker.js
Attendance scanner
Standalone PWA module for scanning
- Scanner UI · Standalone attendance-scanner entry page
apps/attendance-scanner/index.html - Scanner SW · Scanner offline cache boundary
apps/attendance-scanner/sw.js - Scanner manifest · Scanner installability metadata
apps/attendance-scanner/manifest.json
Attendance viewer
Google Apps Script web app for attendance viewing
- Viewer backend · Server-side viewer logic in Google Apps Script
apps/attendance-viewer/Code.gs - Viewer UI · Browser client for attendance viewing
apps/attendance-viewer/app.js
Mailer
Google Apps Script web app for messaging
- Mailer backend · Server-side mailer logic in Google Apps Script
apps/mailer/Code.gs - Mailer UI · Browser client for the mailer app
apps/mailer/app.js
Ops
Deployment and environment wiring
- Static deploy · GitHub Actions static hosting pipeline
.github/workflows/static.yml - Vercel config · Hosting and deployment settings
vercel.json - Env template · Example environment wiring for deployments
env.example.js
Connections 21
- Portal logic → Systems map: loads registry · Portal shell reads module configuration
- Portal logic → Aurora: uses runtime · Shared helper/runtime layer
- Portal UI → Portal logic: boots · Portal page starts shell logic
- Portal UI → Portal styles: styles · Portal presentation bundle
- Portal logic → Portal SW: registers · Portal shell enables offline/update behavior
- Portal manifest → Portal UI: describes · Installable portal shell metadata
- Portal SW → Version: checks version · Update coordination boundary
- Portal logic → Web root: mirrors · Deployable copy of the portal shell
- Web root → Mirror logic: boots · Mirrored portal entry starts mirrored script
- Web root → Mirror styles: styles · Mirrored portal presentation
- Mirror logic → Mirror SW: registers · Mirrored offline/update behavior
- Portal logic → Scanner UI: launches · Portal opens scanner as an embedded or standalone module
- Portal logic → Viewer UI: launches · Portal opens viewer module
- Portal logic → Mailer UI: launches · Portal opens mailer module
- Scanner UI → Scanner SW: registers · Scanner PWA boundary
- Scanner UI → Scanner manifest: describes · Scanner install metadata
- Viewer UI → Viewer backend: calls · Browser client talks to Apps Script backend
- Mailer UI → Mailer backend: calls · Browser client talks to Apps Script backend
- Static deploy → Web root: deploys · Static pipeline publishes hosted portal copy
- Vercel config → Portal UI: hosts · Hosting target for static portal
- Env template → Portal logic: configures · Environment-specific portal wiring