How xoanvx/marcus-barber works
Project type and purpose
• This is a purely static, multi-page front-end website (HTML + CSS) with no backend logic.
• The project is laid out as a brochure-style site (home, login/register pages, about us, services, products, policies, order history, claims, careers, locations).
• It’s intended to be served from a static-hosting platform (e.g., GitHub Pages) and viewed in the browser.
File structure
• Each top-level folder (INICIO, LOGIN, NOSOTROS, etc.) represents one HTML page plus a page-specific style.css.
• There is a shared CSS file (styleHeaderFooter.css) for the common header/footer.
• An image directory (imag/) holds static assets.
• No JS, no server or API directories—this is client-only.
Pulling insights from the README
• The author is linking pages via hyperlinks but experiencing CSS-loading issues on GitHub Pages (index.html placement).
• There are no documented back-end dependencies or build steps.
a. Client (Web browser)
b. Static hosting layer (GitHub Pages or any web server/CDN)
c. Static asset store containing:
• Individual pages (INICIO/index.html, LOGIN/login.html, …)
• Per-page CSS files (style.css under each folder)
• Shared CSS (styleHeaderFooter.css)
• Images (imag/)
Relationships and interactions
• The browser issues HTTP(S) requests to the hosting layer.
• The hosting layer serves requested HTML/CSS/image files.
• Hyperlink navigation between pages is handled purely by the browser (no API calls).
Architectural patterns and design principles
• Static site architecture: no server-side code, no database.
• Separation of concerns:
• Per-page CSS for page-specific styling
• Shared CSS for common layout elements (header/footer)
• Content grouped by feature/page in its own directory.
Key technologies and libraries
• HTML5
• CSS3
• GitHub Pages (or equivalent static host)
• No JavaScript frameworks, no backend frameworks.