How redeifabbri/seratest works
Project Type and Purpose
• This is a static, content‐rich website (a “JAMstack”/static site) for the Collegium Seraphicum organization.
• No traditional backend or database—just HTML pages, CSS/JS assets, image and document files—all served statically.
• Continuous deployment via Netlify from the GitHub repo.
Key Parts of the File Structure
• Top level:
• HTML entry points (index.html, Rolunk.html, Galeria.html, etc.)
• package.json + node_modules (dev toolchain)
• x86_64-*-simple-http-server binaries for local testing
• src/
– documents/ (PDFs, DOCXs)
– pictures/ (galleries, logos)
– scripts/ (gallery logic, slideshows, navigation)
– style/ (layout-*.css, design.css)
– svg/
• README describes CSS split (layout vs. design) and page structure (header, navbar, content, footer).
Main Components
A. Developer Environment
• GitHub repo (source)
• Local dev server (simple-http-server binary invoked via runnner.js)
• Node/npm toolchain (linting, bundling if any)
B. CI/CD Pipeline
• Netlify build process (pulls from GitHub, runs any build scripts, publishes to CDN)
C. Static Hosting / CDN
• Netlify’s edge network (serving HTML, CSS, JS, assets globally)
D. End User (Browser)
• Requests HTML
• Loads CSS and JS
• Fetches images and documents as needed
Relationships and Data Flows
• Developer → (git push) → GitHub
• GitHub → (webhook) → Netlify Build
• Netlify Build → (deploy) → CDN / Static File Store
• Browser ↔ CDN (HTTP GET pages, assets)
• Optionally Browser ↔ Local Dev Server (during development)
Architectural Patterns & Principles
• JAMstack: Pre-built markup and assets delivered over CDN
• Single Responsibility: Each folder holds a specific asset type (scripts, style, pictures, documents)
• Separation of Concerns: CSS layout vs. design, JS classes vs. page logic
Technologies & Frameworks to Label
• HTML5 pages (no framework)
• Vanilla JS modules (gallery, slideshow, navigation)
• CSS (modular layout-*.css + design.css + color_swatch.css)
• Netlify (CI/CD + CDN)
• simple-http-server (local dev)
• GitHub (source repository)
Essentials to Capture
• Clear separation: Dev environment vs. CI/CD vs. Hosting vs. Client
• Asset types and their folders under one “Static Assets” component