How sheikhjunaid07/architect-template works
Project type and purpose
• This is a static, client-side architecture portfolio template built with only HTML and CSS.
• No backend, no database, no JavaScript or dynamic processing.
File structure
• Top-level assets:
• index.html — entry point for the site.
• css/ — contains presentation styles (aboutPage.css, contactPage.css, navbar.css, projectPage.css, style.css).
• images/ — asset directory with subfolders (bg-images, members, projects-images).
• No build scripts, no server-side code.
Extract insights from the README
• Confirms “Architecture website template created in Only HTML and CSS.”
• Implies a purely static artifact to be hosted on any HTTP server or CDN.
Main components
a. User (Browser)
b. HTTP Server (or CDN)
c. Static Files Storage
• HTML file (index.html)
• CSS files (css/*.css)
• Image assets (images/*)
d. (Optional) Deployment Host/Service (e.g., GitHub Pages, Netlify)
Relationships and interactions
• The User’s browser issues HTTP GET to the Server for “/index.html.”
• The Server responds with HTML; the browser parses links to CSS and image resources.
• For each CSS or image URL, the browser issues additional GET requests.
• The Server returns the static assets directly from storage.
Architectural patterns/design principles
• Separation of concerns: HTML for structure, CSS for styling, images for media.
• Static hosting: no runtime server logic, high cacheability.
Relevant technologies
• HTTP/HTTPS
• HTML5
• CSS3 (modularized per page/component)
• Static file server or CDN hosting
Detail
• Caching headers or CDN distribution if relevant.
• That styling and media are decoupled from structure.