The build workflow

From the first URL
to the final deploy.

A repeatable, honest record of the ChatGPT-to-Netlify process, including its iterations, mistakes, testing and human review.

END-TO-END / NINE STAGES

A process you can repeat.

Each stage builds on the one before it. No stage is complete merely because AI produced an attractive screenshot.

01DISCOVER

Audit two existing websites

Review Al Huda Elementary and Al Huda Secondary, then inventory pages, programs, original images, admission links, and donation paths. Keep conflicting claims as questions, not facts.

  • Capture original URLs and school divisions.
  • Record uncertain grade levels, admission years and donor recipients.
  • Identify authentic logos and permitted photography.
02SPECIFY

Write the master prompt

Translate the audit into a 21-chapter development brief spanning branding, architecture, programs, accessibility, admissions, fundraising, source verification, and QA.

  • State what must be preserved.
  • Define responsive sizes and major user journeys.
  • Specify acceptance criteria and verification constraints.
03GENERATE

Create a working website

Use ChatGPT to generate actual multi-page static files, not just screenshots. The prior Al Huda project grew into a 26-route site with shared navigation and school-specific content.

  • Produce a root index.html and route folders.
  • Keep functional HTML/CSS/JavaScript separate.
  • Preserve official external application and donation destinations.
04ITERATE

Improve design through V1–V6

Give direct feedback about what is not working. The revisions addressed difficult typography, generic visual treatment, oversized layouts, animation, image composition, and brand fidelity.

  • Compare mobile and desktop screenshots.
  • Use supplied identity assets rather than invented logos.
  • Review real interactions, not only static aesthetics.
05VALIDATE

Test and fix issues

Run browser checks at multiple widths. Earlier local QA reports recorded 208 viewport cases for V6, but those checks do not replace real-device and hosted-browser signoff.

  • Audit overflow, duplicate arrows, accessible tabs and menu behaviour.
  • Test reduced motion and keyboard operation.
  • Report blocked checks honestly.
06SHARE

Prepare rich social previews

Generate Open Graph metadata and centrally composed share cards so important words remain visible when WhatsApp creates smaller or square thumbnails.

  • Use the supplied school crest and colours.
  • Check square and 4:5 crops.
  • Test real WhatsApp previews after deployment.
07PACKAGE

Export the deployable site

Create a static folder with root index.html, assets and Netlify configuration. Package the folder as a ZIP, then extract it on the local machine before deployment.

  • No Git dependency or custom build command.
  • Check all local paths and required routes.
  • Keep version numbers and QA artifacts organized.
08DEPLOY

Create or update a Netlify project

For a new documentation site, log in and use Netlify Drop or Add new project → Deploy manually. Updating an existing project instead requires that project’s Deploys area.

  • Choose the intended Netlify team.
  • Deploy the extracted folder, not the wrong parent directory.
  • Verify the new netlify.app URL and key links.
09VERIFY

Run the post-deploy checklist

Confirm the live website, inspect console warnings, test major journeys and metadata, and document anything not yet approved. Version and share the final deliverable.

  • Check primary pages and mobile navigation.
  • Update canonical and OG URLs once the final domain is assigned.
  • Keep the docs site separate from the live school project.
REUSABLE PROMPTING

Ask for outcomes.
Then ask for evidence.

FIRST PROMPT / START WITH THE BRIEFCombine the two existing school websites into one coherent, deployable, responsive website. Preserve the distinct Elementary and Secondary identities and current official destinations. Audit source content, create every required page, and provide source files plus QA evidence.
FOLLOW-UP PROMPT / TARGETED REVISIONReview the current build at 320, 390, 768, 1024 and 1440px. Find and correct clipped text, unclickable elements, duplicate arrows, focus issues and animation conflicts. Retest and package the corrected website as a new version.
Evidence standard

A browser screenshot, a successful deployment, and a functional admissions backend are three different claims. Document each independently and never mark an untested item as passed.

Type a keyword to find the relevant section.