How renzel/portfolio_new works
Main Components
• Developer Machine / Code Repository
• Source files (src/, public/, portfolio.js, SCSS, assets)
• Configuration (.env, Dockerfile, CI workflows in .github/workflows)
• Build & CI/CD Pipeline
• npm scripts + Webpack (via create‑react‑app)
• Pre‑commit hooks (prettier, linting)
• GitHub Actions workflows (deploy.yml)
• Docker image build (optional)
• Hosting / CDN Layer
• GitHub Pages or Netlify (netlify.toml) serving static files (HTML, JS, CSS, assets)
• Browser / Client
• React SPA (App.js → containers/components)
• Service Worker (serviceWorker.js) for caching
• Context API (StyleContext) & custom hooks (useLocalStorage)
• External API Services
• GitHub GraphQL API (apollo‑boost) to fetch profile, repos, pinned projects
• Medium (RSS or API) for blog posts
• Twitter Embed (react‑twitter‑embed) for timeline
• Lottie (lottie‑react) for animations
Relationships & Data Flows
• Developer pushes code → CI triggers build & tests → artifacts deployed to CDN
• On page load: Browser GETs index.html & bundles → React mounts App
• React components use Apollo Client to query GitHub GraphQL (with REACT_APP_GITHUB_TOKEN)
• Conditional fetch: Medium blogs if MEDIUM_USERNAME set
• TwitterTimeline component fetches embed scripts
• Service Worker intercepts requests for offline caching
Architectural Patterns
• SPA (Single Page Application) with client‑side routing (if any)
• Component‑Based Architecture (src/components vs src/containers)
• Context + Hooks for global state (theme, localStorage)
• External Data Layer via Apollo Client (GraphQL) & REST/embeds
• Static Hosting + CI/CD for zero‑backend deployment