Skip to main content
ambooka
Back to case studies
Case studyCompleted

Hebatullah CMS Website Rebuild

Reworked hebatullah.com from static HTML into a CMS-backed site for non-developer content management.

CMSWeb DevelopmentContent ManagementHosting

Project summary

Company website rebuild from static HTML into a CMS-backed system for non-developer content updates.

Live project

Site

hebatullah.com

Problem

  • The company website was static, making every marketing update dependent on developer involvement.

Architecture

  • Problem-first presentation: the case study opens with the operational or engineering pain point, not a UI effect.
  • Implementation details are summarized through stack, workflow, integrations, data handling and deployment context.
  • Sensitive client/company details are sanitized while preserving real business value and technical credibility.
  • Every project record links stack, proof, engineering evidence and measurable impact where available.

Key Decisions

  • Use real resume evidence only: client work, company work, academic research and completed portfolio platform work.
  • Keep private learning plans out of the public portfolio.
  • Avoid overclaiming: status, proof and metrics must reflect actual evidence.
  • Prioritize readable business value and implementation decisions over decorative presentation.

Implementation

  • Rebuilt the website around a CMS workflow so the marketing team could manage content independently.
  • Stack used: CMS, Web Development, Content Management, Hosting.
  • Documented the project with a recruiter summary, business value and engineering evidence.
  • Prepared the project for public case-study presentation with safe disclosure boundaries.

Quality Gates

  • Testing evidence is limited or not public for this project.
  • CI/CD is not public or not applicable for this project.
  • Deployment or real operational use is part of the proof.
  • Public wording avoids private planning language and keeps the portfolio professional.

Results

  • Reduced update friction and improved ownership for business content.
  • Strengthens the portfolio through real-world experience instead of tutorial-style claims.
  • Supports positioning across software engineering, IT systems, business automation and applied AI/ML engineering.

Future Improvements

  • Add screenshots or diagrams where safe to publish.
  • Add demo videos for public-facing work.
  • Attach more measurable performance, reliability or business impact metrics when available.
  • Keep client/company-sensitive details sanitized.

Public Evidence

  • Docs
  • Deployed