How rwaddin/shabib works
Project Type and Purpose
• This is a Nuxt.js–based universal (SSR/SSG) Vue.js application. It delivers a static or server-rendered website, hosted via Firebase. There is no separate “backend” code in this repo; content is pre-rendered or served by Nuxt’s Node server and ultimately published to Firebase Hosting.
Key File-Structure Analysis
• Top-level configuration:
• nuxt.config.js – central Nuxt configuration (routing mode, modules, plugins, build settings)
• firebase.json & .firebaserc – Firebase Hosting configuration
• package.json & package-lock.json – NPM scripts, dependencies
• Directories:
• pages/ – Vue views; automatically become routes
• components/ – reusable Vue components (Dad.vue, Mom.vue, etc.)
• assets/ – uncompiled static assets (images, styles)
• static/ – static files mapped 1:1 to site root
• store/ – Vuex store modules for global state
• (optional) layouts/, plugins/ – not present but referenced in README
Architectural Patterns
• Component-based UI: pages orchestrate layouts and import components
• Vuex for centralized state management
• SSR/SSG pipeline: Nuxt generates HTML on the server or at build time
• Deployment pipeline: NPM scripts → build/generate → Firebase deploy
Main Components & Interactions
a. Developer Environment
• Node.js + NPM
• Source files (pages/, components/, store/, assets/, static/)
• nuxt.config.js
b. Build & Runtime Server
• Nuxt Dev Server (npm run dev)
• Nuxt Build & Generate (npm run build → npm run generate)
c. Output Artifacts
• Generated “dist” folder (pre-rendered HTML/CSS/JS)
d. Hosting & CDN
• Firebase Hosting serves static & SSR endpoints
• Optional Cloud Functions if SSR mode is remote (not present here)
e. Client Browser
• Fetches HTML/CSS/JS from Firebase via CDN
• Executes Vue hydration; interacts with Vuex and backend APIs (if any)
• How pages import components and access Vuex store
• Where assets and static files fit (images, fonts, robots.txt)