How xaminezh/criot-club-website works
Project type and purpose
• From the README (“site web de CRiot FSBM… centraliser les informations… mettre en valeur ses projets”) and the file tree, this is a purely static, multi‐page website for a robotics & IoT club.
• There is no dynamic backend, only HTML files, CSS stylesheets, media assets (images, video), and a PPTX for reference.
File structure
• Top-level HTML entry points: index.html, about.html (2about.html), members.html, activities.html, join.html, thanks.html.
• CSS files scoped per page (about.css, members.css, etc.) plus a few global styles (index.css, activities.css).
• A directory “activities formations/events and formations” holding sub-pages, CSS, videos (video.mp4).
• A “pics” directory for images and a PPTX slide deck under website.pptx.
• No server-side code, build scripts, or deployment manifests – it’s hand-crafted static content.
Key components to surface
a. Client (web browser)
b. Hosting environment (e.g., static web server or CDN)
c. Static assets:
• HTML pages grouped by section (About, Members, Activities, Join, Thanks)
• CSS stylesheets (per-page and global)
• Media files (images in /pics, video.mp4)
• Presentation (website.pptx)
d. Optional services (if used): DNS provider, SSL/TLS termination, analytics (e.g., Google Analytics), CDN endpoints
Relationships & data flows
• Browser issues HTTP GET requests to the hosting/CDN for each HTML file.
• Each HTML references one or more CSS files and media assets; the browser fetches these in parallel.
• Assets are served directly from the static file server or CDN.
• Navigation between pages is client-driven via standard hyperlinks.
Architectural patterns & design principles
• “Static-site” pattern: no server-side rendering, purely client-side consumption of pre‐built assets.
• Clear separation of content (HTML), presentation (CSS), and static media (images/video).
• File naming and directory conventions reflect site sections and sub-sections.
Essential architecture
• No need to over-complicate with microservices or databases – this is a classic static site.
• Flow: Browser ↔ Static Server.
• Files by purpose to reflect the directory structure.