How shoutym/floodwatchsk_web works
1. This repository is a static web export, not a server app. The top-level index.html, map.html, modal.html, and sensor/[id].html pages, plus 404.html, +not-found.html, and _sitemap.html, indicate a prebuilt site meant to be hosted on a static platform such as GitHub Pages.
2. The main application is built with Expo / Expo Router. The _expo directory, especially _expo/.routes.json and _expo/static/js/web/entry-...js, is generated output that maps route definitions to the web bundle used at runtime.
3. The routing model is file-based and route-driven. The presence of sensor/[id].html shows a dynamic route for sensor detail pages, while index.html, map.html, and modal.html are static route endpoints. This is the primary navigation boundary in the system.
4. The (tabs) directory represents a route group / layout boundary rather than a public URL segment. Its index.html and map.html pages suggest a tabbed section of the app with multiple views sharing a common layout or navigation shell.
5. The web runtime is a single client-side JavaScript bundle loaded by the exported HTML pages. The HTML files serve as entry shells; the _expo/static/js/web/entry-...js bundle contains the actual app logic that hydrates and drives navigation in the browser.
6. assets/ is the repository’s static resource layer. Any images, icons, or other non-code assets referenced by the generated pages or the app bundle are expected to live here and are served directly by the static host.
7. sensor/[id].html is the clearest sign of a data-driven UI boundary. The app likely renders sensor-specific content based on the route parameter id, with the browser bundle responsible for reading that route and displaying the appropriate sensor view.
8. 404.html, +not-found.html, and _sitemap.html are part of the hosting and discoverability layer. 404.html supports static-host fallback behavior, +not-found.html covers app-level missing routes, and _sitemap.html helps search engines and route discovery.
9. CNAME and .nojekyll point to GitHub Pages-style deployment constraints. CNAME sets a custom domain, while .nojekyll disables Jekyll processing so the generated files and special route names are served as-is.
10. The overall data flow is simple: static HTML shell → loaded Expo web bundle → client-side route handling → route-specific views. There is no evidence here of a separate backend, API service, or database in this repository.
11. For an architecture diagram, the important boxes are: static host, generated HTML route pages, Expo web bundle, route group/layout structure, and static assets. The main boundary is between build-time generated artifacts and runtime browser execution.
12. The repository content is minimal, and the README.md only says Test, so the architecture should be treated as exported frontend output rather than a full source tree. Most of the interesting structure is encoded in the generated route files and the Expo artifacts.
Main entry points: entry-6fadacdbe3c40517a66130fb265f192f.js Web bundle · index.html Home page · map.html Map page · [id].html Sensor detail
Components 16
Deployment
Static hosting and publish-time constraints
- Static host · Static platform serving prebuilt pages and assets
- Custom domain · GitHub Pages domain binding
CNAME - No Jekyll · Prevents host-side rewriting of generated files
.nojekyll
Routes
Generated HTML entry points and route boundary pages
- Home page · Top-level exported landing page
index.html - Map page · Top-level exported map route
map.html - Modal page · Exported modal route shell
modal.html - Tabs home · Route-group index inside the tabs layout
(tabs)/index.html - Tabs map · Route-group map view inside the tabs layout
(tabs)/map.html - Sensor detail · Parameterised sensor page for sensor id
sensor/[id].html - App 404 · Application-level missing route page
+not-found.html - Host 404 · Static host fallback page
404.html - Sitemap · Generated sitemap for crawlers and route discovery
_sitemap.html
Runtime
Expo Router web bundle and routing metadata
- Route map · Generated route mapping used by the web export
_expo/.routes.json - Web bundle · Single browser bundle that hydrates and drives navigation
_expo/static/js/web/entry-6fadacdbe3c40517a66130fb265f192f.js - Tabs layout · Shared layout boundary for tabbed views
(tabs)
Assets
Static resources served by the host
- Assets · Static files referenced by the exported app
assets
Connections 33
- Static host → Custom domain: serves · Custom domain configuration is part of deployment
- Static host → No Jekyll: serves · Host must expose generated files without Jekyll processing
- Static host → Home page: serves · Entry shell loaded by the browser
- Static host → Map page: serves · Entry shell loaded by the browser
- Static host → Modal page: serves · Entry shell loaded by the browser
- Static host → Tabs home: serves · Route-group page served as a static endpoint
- Static host → Tabs map: serves · Route-group page served as a static endpoint
- Static host → Sensor detail: serves · Dynamic route exported as HTML
- Static host → App 404: serves · App-level fallback page
- Static host → Host 404: serves · Static host fallback page
- Static host → Sitemap: serves · Search/discovery artifact
- Home page → Web bundle: loads · HTML shell bootstraps the client bundle
- Map page → Web bundle: loads · HTML shell bootstraps the client bundle
- Modal page → Web bundle: loads · HTML shell bootstraps the client bundle
- Tabs home → Web bundle: loads · Route-group page bootstraps the client bundle
- Tabs map → Web bundle: loads · Route-group page bootstraps the client bundle
- Sensor detail → Web bundle: loads · Dynamic route page bootstraps the client bundle
- Route map → Web bundle: drives · Generated route metadata informs the runtime router
- Tabs layout → Tabs home: organizes · Shared layout boundary for tabbed routes
- Tabs layout → Tabs map: organizes · Shared layout boundary for tabbed routes
- Web bundle → Tabs layout: renders · Client runtime activates the tabbed layout
- Web bundle → Sensor detail: resolves · Client-side routing selects the sensor view by id
- Web bundle → Home page: hydrates · Browser runtime takes over the exported shell
- Web bundle → Map page: hydrates · Browser runtime takes over the exported shell
- Web bundle → Modal page: hydrates · Browser runtime takes over the exported shell
- Assets → Web bundle: referenced by · Bundle can reference static assets at runtime
- Assets → Home page: referenced by · Pages may reference exported assets
- Assets → Map page: referenced by · Pages may reference exported assets
- Assets → Sensor detail: referenced by · Sensor pages may reference static assets
- App 404 → Host 404: fallback · App fallback complements host fallback behavior
- Sitemap → Home page: indexes · Sitemap enumerates public route pages
- Sitemap → Map page: indexes · Sitemap enumerates public route pages
- Sitemap → Sensor detail: indexes · Sitemap enumerates public route pages