How sumanthnagireddi/my-portfolio works
Project type and purpose
• This is a single-page web application built with Angular (v18) that serves as a personal portfolio (“MyPortfolio”).
• It is hosted on Firebase Hosting, uses Firestore for dynamic content (blogs, interviews, resources), and includes a minimal Node.js server (server.js) likely for server-side rendering or API fallbacks.
• CI/CD is configured via GitHub Actions workflows (.github/workflows/*.yml) to build and deploy to Firebase on pull requests and merges.
File structure
• Top-level configuration:
• angular.json, tsconfig*.json, tailwind.config.js – Angular build and styling setup
• firebase.json, .firebaserc, firestore.rules, firestore.indexes.json – Firebase Hosting and Firestore security/indexes
• server.js – Node entrypoint for SSR or universal routing
• public/ – static assets served by Firebase
• src/ – Angular source code
• Under src/app:
• app.component, app.routes.ts, app.config.ts – root module, route definitions, environment/config constants
• components/ – reusable UI components (header, hero, blog-card, etc.)
• pages/ – route-backed views (home, about, blog list/detail, interview, resources, work)
• services/portfolio.service.ts – data access service wrapping Firestore calls
• pipes/words-reducer.pipe.ts – text formatting helper
• CI/CD: .github/workflows/firebase-hosting-*.yml triggers ng build and firebase deploy.
README for additional insights
• Confirms Angular CLI usage, dev server (ng serve), build output to dist/, unit tests (Karma), e2e tests, and reliance on standard Angular commands.
Elements
• Labels: “Browser / Angular SPA”, “Firebase Hosting”, “Node.js Server (server.js)”, “Firestore Database”, “GitHub Actions CI/CD”
• Browser → Hosting → Server.js (if routing) → Hosting
• Browser ↔ Firestore (via Firebase SDK)
• GitHub Repo → GitHub Actions → Firebase CLI API → Firebase Hosting & Firestore
• Rectangles for services (Hosting, Firestore, CI/CD)
• Clouds or hexagons for external/managed services (Firebase)