How mohankk40/frontendpages works
Project type and purpose
• There is no backend code, API, database, or build pipeline—only static assets meant to be served to a browser.
File structure
• Top-level HTML files represent individual pages (Grid, Tech Doc, Tribute, Cat Site, Coffee Shop, Form).
• Corresponding CSS files live alongside them; each page references its own stylesheet.
• No “src” or “assets” folder—every file sits at the root.
• No configuration/build scripts means these files can be dropped into any static web server or CDN.
README for additional insights
• The README simply calls it “My Front End Websites,” confirming the static-site nature.
a. Main components
• User’s Web Browser (Chrome/Firefox/etc.)
• Static Web Server or CDN (e.g., GitHub Pages, Netlify, Apache, Nginx)
• Static File Storage (HTML + CSS files)
b. Relationships & interactions
• The browser issues HTTP GET requests for HTML pages.
• The server returns the requested HTML along with CSS files.
• The browser renders the HTML + CSS to produce the visual page.
• User clicks/hyperlinks navigate between pages, triggering further GETs.
c. Architectural patterns/design principles
• Simple Client-Server model (no middle tier).
• Static hosting—everything is pre-built, no run-time processing.
• Each page is self-contained: one HTML + one CSS.
d. Key technologies
• HTML5 (structure)
• CSS3 (styling)
• HTTP/HTTPS (transport)
• (Optional) GitHub Pages or other static-site host
Detailed guidance
• Start your drawing with the Browser on the left, the Server/CDN in the middle, and the File Store on the right.
• The HTML files together in one container labeled “Pages” and all CSS files in another labeled “Stylesheets.”