How sykoramade/incidentdice works
File structure
• index.html: the single-page UI and application logic (likely includes embedded or linked JavaScript).
• incident_matrix.csv: the data file containing the dice outcomes or incident matrix.
• README.md: minimal project description.
README for additional insights
• There are no back-end services or additional instructions. Everything is expected to run in the client (browser) against a static CSV.
Main components and their relationships
a. Client (Browser):
• Loads index.html and any associated JS/CSS assets.
• Renders the UI (dice roller interface).
• Fetches incident_matrix.csv (via an HTTP GET request to the static server).
• Processes the matrix and displays roll results.
b. Static File Server:
• Hosts index.html and incident_matrix.csv.
• Serves all assets over HTTP or HTTPS.
c. Data Store:
• incident_matrix.csv acts as a simple lookup table. No database engine is involved.
Data flow:
Browser → HTTP GET index.html
Browser → HTTP GET incident_matrix.csv
Browser (JS) → Reads CSV, applies randomization logic → Updates UI
Architectural patterns and design principles
• Single-Page Application (SPA) style, but without a framework.
• Clear separation: Presentation layer (HTML/JS/CSS) vs. Data layer (CSV).
• No server-side logic: “server” is purely a static asset host.