Direction & judgment
Planning, creative feedback, brand assets, issue identification, review and deployment activity.
32% of estimated totalAn accountable breakdown of who did what, how much active time was estimated, and what the Al Huda Schools project produced.
The figures below are approximate active-effort allocations from the documented ChatGPT workflow, not audited timesheets or elapsed wall-clock time.
Planning, creative feedback, brand assets, issue identification, review and deployment activity.
32% of estimated totalResearch support, coding, design, interactive effects, responsive QA, fixes and documentation.
68% of estimated totalEach category is an approximation based on the work described in the conversation—not a precise measurement of active typing or compute runtime.
Defining goals, consolidating two school websites, selecting requirements.
Evaluating visual directions, requesting iterations, reviewing results.
Supplying assets, refining wording, identifying button and layout problems.
Choosing hosting, manual deployment and reviewing the playbook.
Turning the two-site concept into a master brief and researching UX patterns.
Producing and revising page structure, code, layouts and interactions.
Browser checks, bug fixes, animation polish, and social-sharing assets.
Exporting deploy packages, producing the playbook and documenting QA.
A unified school website, six design iterations and a separate public-facing documentation playbook.
These figures come from the recorded AI-assisted development checks. They do not prove cross-browser coverage, live payment functionality, formal accessibility certification or real-user performance. The documentation site is separate from the school website.
Human judgment directed the priorities and verified the outputs. Generative AI accelerated content organization, code production, technical QA and iterative improvement. Manual Netlify deployment connected the finished files to hosting.
Approximate allocation. The 45- and 95-minute totals were estimated in the conversation. They are not stopwatch measurements or Netlify/ChatGPT usage records.
Not calendar duration. Human and AI work may overlap. Adding the figures produces an illustrative 140 minutes of combined active effort, not the exact elapsed project duration.
Not an autonomous deploy claim. Netlify hosted the school site and later this playbook, with manual publication steps. ChatGPT's Netlify connection could manage projects but did not provide a direct file-upload/deploy action.
Scope boundaries. Unrecorded offline work, formal user testing, live integrations and subsequent maintenance are excluded. Verified production operation is distinct from local QA.