How infographicsuo/beyondtoxics works
Project type and purpose
• From the file tree and README (“BeyondToxics”), this is a static, client-side web application (“FERNS” folder) that visualizes environmental data (JSON files for counties and chemicals) in the browser.
File structure
• Top level:
• .gitignore
• README.md
• FERNS/ (all of the front-end code and data)
• FERNS/ contents:
• index.html – entry point
• ferns.js, styles.js – JavaScript modules
• ferns.css – styling
• OR_COUNTY.json, chemicals.json – static data sets
• No build scripts or server code: implies a simple static-site deployment.
Key insights from README
• Project name only (“BeyondToxics”) with no further tech stack notes, confirming a minimal client-only app.
• We can infer that a static file host or CDN is the intended deployment target.
Main components
a. User’s Web Browser (Client)
• Loads index.html
• Executes ferns.js and styles.js
b. Static File Host / CDN
c. (Optional) External Map API or Analytics Service
• If the app integrates any third-party map or telemetry—display as an external service node
Architectural patterns & principles
• Static SPA (Single-Page Application)
• Unidirectional data flow: JS fetches data → renders views
• Separation of concerns: HTML for structure, CSS for styling, JS for logic/data
Technologies & libraries
• Core: HTML5, vanilla JavaScript (ES modules), CSS
• Data format: JSON
• Deployment: any static file host or CDN (GitHub Pages, Netlify, S3, etc.)
• host1 [label="FERNS Assets"]
• }
Final advice
• Be very detailed: break out the JS modules, CSS, data files if needed.
• Keep it simple: static host → client → data flow is the core.