How sudoarun/mermato works
Project Type and Purpose
• This is a front-end-only static site boilerplate for a coding assessment.
• It consists of three assets—HTML, CSS, and JavaScript—and a GitHub Actions workflow to publish the site (via Jekyll) to GitHub Pages.
• There is no backend or database; the system serves static files to end users’ browsers.
Key Components
a. Developer Environment
• Local workspace where index.html, style.css, and script.js are authored and tested in a browser.
b. Version Control / Repository
• GitHub repo containing the code files and the .github/workflows/jekyll-gh-pages.yml CI config.
c. CI/CD Pipeline
• GitHub Actions workflow that runs on pushes to the main branch, builds (if necessary), and publishes to GitHub Pages.
d. Hosting Layer
• GitHub Pages serves the static site over HTTPS.
e. End-User Browser
• Fetches and renders the HTML, CSS, and JS.
Interactions and Data Flow
• Developer → (git push) → GitHub Repo
• GitHub Repo → (trigger) → GitHub Actions Workflow
• GitHub Actions → (deploy) → GitHub Pages
• End-User Browser ← (HTTP GET) ← GitHub Pages
• Browser parses index.html, loads style.css and script.js, and executes client-side logic.
Architectural Patterns and Principles
• Static-First Architecture: no server-side rendering at runtime—everything is prebuilt and served as flat files.
• CI/CD: automated build-and-deploy via GitHub Actions.
• Separation of Concerns: HTML for structure, CSS for styling, and JS for behavior, each in its own file.