How joguarino/festa-tracker works
1. This repository is a small static website, not a traditional backend service. The architecture is centered on HTML entry pages, shared styling, and client-side JavaScript that reads local JSON content.
2. The top-level pages are the main user-facing boundaries:
- index.html is likely the landing page.
- diretta.html is a dedicated “live” or real-time view.
- percorso.html is a route/route-map style view.
- programma.html is a program/schedule view.
3. The css/ directory is the shared presentation layer. It likely contains global layout and page-specific styling used by the HTML pages to keep the experience consistent.
4. The js/ directory is the behavior layer. Since there is no backend code in the tree, any dynamic behavior is probably implemented in browser-side scripts: loading data, updating DOM content, switching views, and formatting page-specific information.
5. The JSON files are the main data source for the site:
- percorso.json likely supplies structured route/path data for percorso.html.
- programma.json likely supplies schedule/event data for programma.html.
These files suggest a data-driven front end where page content is populated from local assets rather than an API.
6. diretta.ref looks like a reference artifact for the live page, possibly used as a fixture, expected output, or sample data. It suggests diretta.html may be compared against or generated from reference content during development or testing.
7. The data flow is simple and mostly one-way:
- Browser loads an HTML page.
- The page loads shared CSS and page-specific JavaScript.
- JavaScript reads the local JSON assets or embedded reference content.
- The DOM is rendered/updated entirely on the client side.
There is no visible server-side processing path in the repository.
8. The repository has a lightweight CI/CD boundary in .github/workflows/static.yml. That strongly suggests GitHub Actions is used to validate or publish the static site, likely to a static hosting target such as GitHub Pages or another static deployment destination.
9. The .vscode/ directory is development tooling only. It affects local editor setup, not runtime architecture.
10. From an architecture-diagram perspective, the key components are:
- Static web pages as entry points
- Shared CSS for presentation
- Client-side JS for interactivity and rendering
- Local JSON/reference files as content inputs
- GitHub Actions as the automation layer for build/deploy checks
11. The main boundary to emphasize is that content and logic live in the repository itself, and the browser is responsible for assembling the final UI. There is no evidence of a database, API server, authentication layer, or external application backend.
Main entry points: js Scripts · static.yml Static CI · diretta.html Live · percorso.html Route
Components 12
Pages
User-facing HTML entry points that render the site in the browser.
Assets
Shared presentation, scripts, and local content files consumed by the pages.
- Styles · Shared presentation layer for layout and page styling.
css - Scripts · Browser-side behavior for loading data and updating the DOM.
js - Route data · Local data source for the route/path page.
percorso.json - Program data · Local data source for the schedule/program page.
programma.json - Live ref · Reference artifact associated with the live page.
diretta.ref - README · Repository overview and usage notes.
README.md
Connections 19
- Home → Styles: styles · Loads shared styling.
- Home → Scripts: behavior · Uses browser-side scripts for interactions and rendering.
- Live → Styles: styles · Loads shared styling.
- Live → Scripts: behavior · Uses browser-side scripts for live view updates.
- Live → Live ref: reference · Uses or compares against the live reference artifact.
- Route → Styles: styles · Loads shared styling.
- Route → Scripts: behavior · Uses browser-side scripts for route rendering.
- Route → Route data: data · Reads local route content.
- Program → Styles: styles · Loads shared styling.
- Program → Scripts: behavior · Uses browser-side scripts for schedule rendering.
- Program → Program data: data · Reads local schedule content.
- Scripts → Route data: loads · Client-side code consumes route data.
- Scripts → Program data: loads · Client-side code consumes program data.
- Static CI → Home: deploy/check · Validates or publishes the static site.
- Static CI → Live: deploy/check · Validates or publishes the static site.
- Static CI → Route: deploy/check · Validates or publishes the static site.
- Static CI → Program: deploy/check · Validates or publishes the static site.
- README → Home: documents · Explains the site entry points and usage.
- VS Code → Scripts: dev setup · Supports local development of the client scripts.