How ashutri0/tei works
Project type and purpose
• This is a purely static, multi‐page website (“tei”) composed of HTML pages (index.html, about.html, contact.html, etc.), CSS stylesheets, JavaScript, images, and a few PDF assets.
• There is no application server or database—everything is served as static files.
File structure
• Top‐level: individual HTML pages and a README.
• assets/ holds all static resources:
• assets/css/ → stylesheet files (404.css, product.css, style.css, responsive.css, etc.)
• assets/js/ → client scripts (script.js, product.js)
• assets/images/ → image files and a brands subfolder
• assets/certificate and input/ → PDF documents (GST CERTIFICATE.pdf, brand PDF)
• products-page/ → dynamic‐looking product HTMLs, but still static.
Main components
• Client Web Browser
• Static File Host (e.g., Nginx, Apache, GitHub Pages, S3 + CloudFront)
• File Storage (HTML, CSS, JS, Images, PDFs)
• Optional CDN layer for assets
Relationships and data flow
• The Browser issues HTTP(S) GET requests to the Static Host.
• The Host retrieves corresponding files from File Storage (or CDN cache) and responds with HTML, CSS, JS, images, or PDFs.
• The Browser renders HTML, applies CSS, executes JS, and fetches images/PDFs as needed.
Architectural patterns and design principles
• Multi‐Page Application (MPA) style—each page is a standalone HTML.
• Clear separation of concerns:
• HTML for structure/content
• CSS for styling/responsiveness
• JS for interactivity (product filtering, scripts)
• Asset organization to facilitate caching and CDN distribution.
Relevant technologies/frameworks
• Static web server (Nginx/Apache/GitHub Pages)
• CDN (e.g., CloudFront, Cloudflare) for assets/ CSS/JS/images
• Browser (Chrome, Firefox) executing script.js, product.js