Production portfolio for a data analyst and automation developer building dashboards, analytical systems, and workflow automation.
Live Portfolio | Blog | Architecture | GitHub Sync | Deployment | Roadmap
This repository powers the public portfolio of Md. Masum Billah, a Data Analyst, Automation Developer, and Business Intelligence Specialist. The site presents verified projects, skills, experience, certificates, case studies, technical writing, and contact paths in one recruiter-facing experience.
Personal and career content is managed through Google Sheets. Public repository facts are synchronized from GitHub, combined with manual portfolio curation, and served through strict Google Apps Script DTOs. Blog articles are generated as static HTML, validated, committed by GitHub Actions, and published through GitHub Pages. The portfolio assistant routes questions through Apps Script to Groq without exposing the AI credential to the browser.
- Responsive portfolio with profile, skills, projects, certificates, experience, and contact sections
- Data and automation project case studies with direct repository and demo links
- Static technical blog with category filtering, search indexing, RSS, and sitemap generation
- Google Sheets-backed content management through Google Apps Script
- Scheduled GitHub repository snapshots with unpublished-by-default portfolio curation
- Explicit public DTO allowlists with last-known-good backend and browser caching
- Automated blog publishing through
repository_dispatchand GitHub Actions - Portfolio assistant grounded in structured portfolio context
- Search, SEO metadata, structured data, robots rules, and a custom 404 page
- Modular HTML components and browser JavaScript modules without a frontend build dependency
The screenshot contains portfolio content from the connected CMS at the time it was captured. The live site remains the canonical source for current experience, skills, and project details.
flowchart LR
Sheets[Google Sheets CMS] --> AppsScript[Google Apps Script API]
AppsScript --> Site[Static portfolio]
Site --> Pages[GitHub Pages]
Sheets --> Trigger[Publishing trigger]
Trigger --> Dispatch[GitHub repository dispatch]
Dispatch --> Action[GitHub Actions]
Action --> Generator[Node.js blog generator]
Generator --> Artifacts[HTML, sitemap, RSS, search index]
Artifacts --> Pages
Site --> AppsScript
AppsScript --> Groq[Groq API]
Read docs/PROJECT_OVERVIEW.md, docs/ARCHITECTURE.md, and docs/DECISIONS.md for system boundaries and rationale.
| Layer | Technology |
|---|---|
| Frontend | HTML, CSS, vanilla JavaScript |
| UI | Tailwind CDN, AOS, particles.js, Google Fonts |
| Content management | Google Sheets, Google Docs, Google Apps Script |
| AI assistant | Groq Chat Completions through Apps Script |
| Static generation | Node.js built-in modules and native fetch |
| Automation | GitHub Actions, Apps Script triggers |
| Hosting | GitHub Pages |
components/ HTML sections loaded by the homepage shell
assets/css/ Global, component, and animation styles
assets/js/ Startup, API, SEO, search, and shared utilities
assets/modules/ Section-specific renderers and interactions
assets/screenshots/ Curated portfolio captures
assets/social-preview/Repository and Open Graph preview artwork
apps-script/ CMS API, contact/chat handlers, and publishing triggers
blog/generator/ Static blog, sitemap, RSS, and search-index generators
blog/templates/ Canonical article and index templates
docs/ Architecture, security, deployment, roadmap, and decisions
The site must be served over HTTP because browser components are loaded with fetch.
git clone https://github.com/itsmebillah/itsmebillah.github.io.git
Set-Location itsmebillah.github.io
npx serve .Open the local URL printed by the server. Runtime portfolio content still depends on the configured public Apps Script endpoint in assets/js/config.js.
node blog/generator/blog-page-generator.jsReview generated changes in the blog manifest/pages, sitemap.xml, rss.xml, and search-index.json. Do not hand-edit generated article files when the source belongs in the CMS or template.
Frontend commits to main are published through the repository's GitHub Pages setting. Apps Script changes require clasp push and an update to the existing versioned web-app deployment. Blog publishing can run manually through Actions or through the configured publish-blogs repository dispatch.
Follow docs/DEPLOYMENT.md for the complete checklist and rollback process.
- Homepage content depends on the availability and response shape of the external Apps Script CMS.
- An automated browser capture on 2026-07-29 observed the loader failing to resolve consistently; production API availability should be monitored.
- Repository evidence cannot confirm the active GitHub Pages source, Apps Script version, installed triggers, or Script Properties.
- The frontend has no automated browser regression suite.
- Generated blog artifacts must remain synchronized with their manifest, sitemap, RSS feed, and search index.
Read docs/CONTRIBUTING.md, docs/SECURITY.md, and docs/PROJECT_RULES.md before changing source or generated artifacts. Never commit Apps Script tokens, Groq keys, GitHub tokens, contact submissions, or private spreadsheet exports.
No open-source license is currently declared. The source is publicly visible, but reuse rights are not granted until a license is added by the repository owner.
Md. Masum Billah | Data Analyst, Automation Developer, and Business Intelligence Specialist
Portfolio | GitHub | Email | LinkedIn | Documentation | Related: Sales Intelligence Platform