How inosaint/ai works
What this project is (type + purpose)
From the file tree and README, this is a static website repository that serves as a portfolio/landing site: “A Collection of all my AI Projects.”
There is no backend (no server code, no API layer, no database). The “system” is primarily:
• Static HTML pages (index.html, projects/*/index.html)
• A shared stylesheet (styles.css)
• A directory structure that groups project pages under projects/
How to read the file structure architecturally
Top-level:
• index.html — likely the main landing page that links to sub-project pages
• styles.css — global/shared styling
• projects/ — a “section” containing per-project sub-sites/pages
• projects/smithy/index.html — a project page (explicit)
Runtime view (what happens in production)
• A user’s browser requests HTML/CSS/assets from a static host
• The landing page links to project pages under /projects/...
• The same CSS and public assets are reused across pages
Code/package view (how the repo is organized)
• “Site root” page
• “Projects” section
• Shared assets and styling
Optionally (but recommended for completeness):
Deployment view (how it gets published)
• Git repo → static hosting (GitHub Pages / Netlify / S3+CloudFront, etc.)
• CDN edge caching (if applicable)
Client-side (runtime)
• User
• Web Browser
• Loads and renders:
• index.html
• styles.css
• projects/smithy/index.html
• projects/hermes/* (whatever exists)
Hosting / Serving layer (runtime)
• Static Web Host
• Serves:
• /index.html
• /styles.css
• /projects/**
• /public/**
• CDN (optional but common)
• Caches static assets close to users
Repo structure (code view)
• Root Site Module
• index.html (main navigation/hub)
• styles.css (shared styling)
• Projects Module
• projects/smithy/index.html (Smithy page)
• projects/hermes/ (Hermes page/module)
• Static Assets Module
External dependencies (only if actually used)
If index.html or project pages reference external resources (not visible from tree), represent them explicitly once you confirm:
• External JS/CDN libraries (e.g., unpkg, jsdelivr)
• External APIs (e.g., OpenAI) — *not implied by this repo*, only add if the HTML actually calls them
Architectural patterns/design principles evident here
• Static-site architecture: no server-side compute, no DB
• Content modularization by directory: each project has its own folder under projects/
• Shared styling: styles.css suggests a single styling source used across pages
• Asset centralization: public/ indicates shared assets (common pattern for static sites)
Don’t overthink it: maximize component separation
• Separate “HTML pages” from “CSS” from “Assets”
• Separate “Home page” from “Project pages”
• Separate “Hosting origin” from “CDN edge” (if applicable)
• Explicit “Navigation” flows (user clicks link → request new HTML)
That level of separation is the most accurate representation of what this repo actually is.
• Open index.html and project pages to see:
• Do they all reference the same styles.css?
• Do they use JS files (none shown in tree) or external scripts?
• Do they load assets from public/?