How dvdferrando/dividimweb works
Project Type and Purpose
• This is a static‐site web project (“dividimweb”) hosted on Firebase Hosting.
• There is no dedicated backend or database service in this repo—only static assets in the public/ folder and configuration for hosting and CI/CD.
File Structure Analysis
• Top‐level config files:
• .firebaserc and firebase.json: Firebase CLI settings and hosting rules.
• package.json / package-lock.json: NPM metadata and any build or deployment scripts.
• CI/CD directory:
• .github/workflows/: two workflows (firebase-hosting-pull-request.yml, firebase-hosting-merge.yml) that automate builds and deployments.
• Public assets:
• public/: HTML, CSS, JS, images, and other static resources served by Firebase Hosting.
• No functions/, src/, or backend folder implies pure static hosting.
Key Components
a. Developer Environment
– Local code repository (GitHub)
– NPM scripts or build tool (if any)
b. Continuous Integration / Continuous Deployment (CI/CD)
– GitHub Actions workflows (.github/workflows)
– Firebase CLI step that authenticates and deploys
c. Firebase Hosting
– Hosting service that serves files from the public/ directory
d. End User
– Web browser accessing the published site
Component Relationships and Data Flow
• Developer pushes commits to GitHub.
• On pull request or merge, GitHub Actions triggers:
• Checkout code
• Install dependencies (npm ci)
• (Optional) Run build step
• Run firebase deploy to Firebase Hosting
• Firebase Hosting updates the live site with files from public/.
• End user’s browser requests pages/assets from Firebase Hosting, which returns the static files.
Architectural Patterns and Principles
• “Infrastructure as Code” for hosting config (firebase.json + .firebaserc).
• GitOps/CI‐driven deployment (GitHub Actions → Firebase).
• Single responsibility: static assets separated from CI/CD and hosting config.