How viccode88/fssa_web works
Project type and purpose
• From the README (“國立鳳山高級中學學生會網站”) and the file tree (all .html, .css, .js, and static config files), this is a purely static website for a high-school student council. There is no backend code or database—only client‐side assets and hosting artifacts.
File structure
• Top level files:
• .html pages: index.html, about.html, contact.html, departments.html, events.html, documents.html
• Styles: style.css, about.css, contact.css, departments.css, events.css
• Script: script.js
• SEO/host config: robots.txt, sitemap.xml, webmap.xml, google…html
• _headers: likely used if deployed to a static host that supports custom headers (e.g. Netlify)
• No src or backend folders—this confirms a front-end only project.
Key insights from the README
• The site is maintained by successive student groups.
• No mention of dynamic features, databases, or API endpoints.
a. Main components
• User’s Browser (Client)
• Static File Host/CDN (e.g. GitHub Pages, Netlify, AWS S3 + CloudFront)
• Static Assets: HTML, CSS, JavaScript
• External Service(s): Google site-verification / Analytics (googlee9732a20410aa1a1.html)
b. Relationships and interactions
• Browser requests index.html (or other pages) from the Static Host
• Host serves HTML, CSS, JS directly (optionally via CDN caching)
• script.js may make in-page DOM updates or call external analytics
• Browser loads external service snippet (Google analytics)
c. Architectural patterns / design principles
• Presentation layer only—no application server or database
• CDN + static-site hosting for simplicity, scalability, and low maintenance
• Separation of concerns: one CSS per page for modular styles, central style.css for shared styling
d. Technologies & frameworks
• Plain HTML5 + CSS3 + vanilla JavaScript
• Static-site hosting (GitHub Pages / Netlify / AWS S3, etc.)
• External analytics/verification via Google
Elements
• Clear labels: e.g. “User Browser,” “Static File Host/CDN,” “Git Repository (source),” “External Analytics”