How avnishsinha/ecowattch works
Project type and purpose
• ecoWattch is a static “brochure-style” website for a CS capstone project. There is no dynamic backend or database—just HTML pages and assets hosted on the NAU CES Share Servers.
File structure
• Top-level files: LICENSE, README.md, two PDFs (Requirement Specification, Technological Feasibility).
• HTML pages: index.html (home), about.html, archive.html, demo.html, team.html, timeline.html.
• Static assets folder: img/ (images used by the pages).
README for additional insights
• Confirms that this is version 1.0.1 of a static website, with future enhancements planned (UX refinements, performance).
• No mention of a server-side component or API—pure front end.
a. Client Browser
b. Static Web Server (NAU CES Share Servers)
c. Static Assets Storage (HTML files, img folder, PDF docs)
d. External Links/Services (GitHub repo, MIT License URL)
Relationships and interactions
• Client sends HTTP GET requests to the Web Server
• Server responds with HTML, images, PDFs
• Client renders pages, follows external links to GitHub or MIT license page
• (Future) potential enhancements: separate CSS/JS hosting, analytics service
Architectural pattern and design principles
• Static-site architecture—no application server or database
• Separation of concerns:
• Content (HTML)
• Assets (images, docs)
• Metadata (README, license)
• Can be extended later with a JAMstack approach (e.g., add client-side JS, CDN, headless CMS)
Technologies & frameworks
• Core: HTML5, potentially CSS/JS (not yet in tree)
• Hosting: NAU CES Share Static Hosting
• Version control: GitHub
• Documentation: PDF requirement/feasibility analyses
Essential elements
• Clear labels on each component (Browser, Web Server, Assets, External Links)