How n1kolozz/tbc-final-project works
What this project is (type + purpose)
SheltMe is a static, multi-page marketing/informational website (no backend in this repo) intended to present a platform concept that connects “shelter givers” with “shelter seekers.”
Key evidence:
• README explicitly says: *“This project is a static website and does not require any server-side setup.”*
• File tree: only HTML, CSS, SCSS, images, fonts; no JS app framework, no server code, no API, no database.
How the repository is structured (what components exist)
From the file tree, the components are:
Static assets
• images/ (logos, gallery images, favicon, etc.)
• fonts/ (custom fonts, if used)
External libraries (runtime dependencies, likely via CDN in HTML)
Per README:
• Bootstrap 5.3.3
• Animate.css 4.1.1
• Font Awesome (implied by classes)
These should appear as external dependencies “loaded by browser.”
Because it’s static, the “system” is basically:
User’s Browser
→ loads HTML pages
→ which reference compiled CSS and assets
→ and also pull external CDN libraries
→ navigation moves between HTML documents.
Runtime / Deployment View (C4 Container-ish, but static-site version)
Shows what runs where: Browser, static files, external CDNs.
Code / Build View
Shows how source SCSS is organized and becomes deliverable CSS.
This avoids cramming build-time and run-time concerns into one picture.
Client / Runtime
• End User
• Web Browser
• HTML Documents
• index.html
• pages/About-page.html
• pages/Services-page.html
• pages/News-page.html
• pages/Contact-page.html
• pages/Registration-page.html (UI-only)
• pages/Sign-in-page.html (UI-only)
• Styles
• css/styles.css (compiled)
• Static Assets
• images/*
• fonts/*
• Bootstrap
• Animate.css
• Font Awesome
Build / Source
• SCSS Source
• scss/styles.scss (entry)
• scss/pages-styles/_variables.scss
• scss/pages-styles/_mixins.scss
• scss/pages-styles/_reset.scss
• scss/pages-styles/_landing-page.scss, _about-page.scss, etc.
• SCSS Compiler (tooling not in repo, but implied; label it “Sass compiler (external tool)”)
• Output:
• css/styles.css
• css/styles.css.map
Step 4 — Highlight architectural patterns present
• Multi-page static site (MPA) rather than SPA
• Separation of concerns:
• Structure: HTML
• Styling: SCSS partials → compiled CSS
• Assets: images/fonts
• Page-scoped SCSS partials (_about-page.scss, _news-page.scss, etc.)
• Shared design tokens/utilities (_variables.scss, _mixins.scss, _reset.scss)
Feature pages as UI surfaces
• Registration/Sign-in are important *screens* but not “services.”
“Form UI only; no persistence/auth API in this repository.”
• scss/styles.scss
• scss/pages-styles/_variables.scss, _mixins.scss, _reset.scss
• page partials _landing-page.scss, _about-page.scss, etc.
• css/styles.css
• css/styles.css.map
That will be the most accurate representation of what exists in the repo.