joshuazobrist/iwent-demo

Purpose and delivery model

This repository is a prebuilt static web application, intended to be served directly as static files. There is no source tree or README; the deployable artifact consists of an HTML shell, hashed frontend assets, and geographic data.

Paths: index.html, assets/index-Sxwa3oPl.js, assets/index-C1SIfVyy.css.

Browser entry point

index.html is the application entry point. It loads the compiled JavaScript bundle and stylesheet from assets/, making the browser the primary runtime. The hashed filenames indicate a bundled production build with cache-friendly asset versioning.

Paths: index.html, assets/index-Sxwa3oPl.js, assets/index-C1SIfVyy.css.

Frontend application bundle

assets/index-Sxwa3oPl.js contains the application behavior, UI rendering, and client-side control flow. Because source modules are not present, changes to application logic require modifying or regenerating this compiled bundle from its unavailable upstream source/build environment.

Paths: assets/index-Sxwa3oPl.js, index.html.

Styling boundary

Presentation is isolated into the generated stylesheet loaded by the HTML entry point. The CSS is separately content-hashed from the JavaScript, allowing independent browser caching and deployment of visual changes.

Paths: assets/index-C1SIfVyy.css, index.html.

Geographic data boundary

Country geometry is supplied as a static GeoJSON dataset. The frontend bundle is expected to load or consume this file in the browser for map, geographic lookup, or country-level visualization functionality. This is the repository’s main application data asset and is separate from executable code.

Paths: data/countries.geojson, assets/index-Sxwa3oPl.js.

Hosting and deployment

GitHub Pages is the material infrastructure target. The Pages workflow publishes the static site; .nojekyll disables Jekyll processing so generated asset paths and files are served unchanged. No backend, database, API service, or server runtime is represented in the repository.

Paths: .github/workflows/pages.yml, .nojekyll, index.html.

Primary flow

A visitor requests index.html from GitHub Pages; the document loads compiled CSS and JavaScript; the JavaScript initializes the client-side application and uses the country GeoJSON as its geographic data input. Deployment publishes these same static artifacts without a build stage visible in this repository.

Paths: index.html, assets/index-Sxwa3oPl.js, data/countries.geojson, .github/workflows/pages.yml.