Deployment & quality

Launch deliberately.
Track every decision.

Deploy this documentation as a new project, then use the source-based readiness tracker for actual school-website approvals.

NEW PROJECT / NETLIFY DROP

Four steps to a
separate docs website.

These instructions create a new project rather than changing the existing school site. No repository or build command is required.

01 / DOWNLOAD↓

Extract the ZIP

Use the documentation package. The extracted folder must directly contain index.html and assets/.

02 / CREATE↗

New Netlify project

Sign in to the desired team, open Netlify Drop or choose Add new project → Deploy manually.

03 / VERIFY✓

Publish & inspect

Drop the extracted folder, open the new netlify.app URL, and check the full documentation.

DEPLOY FOLDER / REQUIRED STRUCTUREal-huda-documentation/ ├── index.html ├── workflow/index.html ├── specification/index.html ├── sitemap/index.html ├── launch/index.html ├── resources/index.html ├── assets/ │ ├── css/site.css │ ├── js/site.js │ └── data/al-huda-master-brief.md ├── 404.html └── _headers
After the new URL exists

Replace the provisional relative Open Graph image path with an absolute HTTPS URL and add canonical/og:url values for the chosen docs domain. The package is intentionally marked noindex while it remains a planning reference; opt into indexing only when ready for public discovery.

TRACKER / SOURCE-BASED

What’s reviewed?
What’s still blocked?

Use the controls to track the deployment and school release requirements. Statuses are saved locally in this browser—no data is sent to a server.

0 of 25 verified

Each item starts as Not reviewed. Change a status only when evidence supports it.

0%

New Netlify documentation project

Extract the documentation ZIP

Ensure index.html, folders and assets are at the extracted folder root.

Choose the correct Netlify team

Creating a new docs project must not overwrite the existing Al Huda school website.

Create a new site through Netlify Drop

Use app.netlify.com/drop or Add new project → Deploy manually.

Verify the new netlify.app URL

Open the homepage, workflow, full brief and checklists without sign-in.

Check live navigation and search

Test mobile menu, local links, brief search, progress tracker and downloadable source.

Review document visibility and social preview

Set absolute og:image, og:url, and canonical URLs after the docs domain is known; choose public/private access intentionally.

Source content & school identity

Complete source URL inventory

Document live source URLs, page copy, images, integrations and proposed replacements.

Confirm Secondary grades and admissions years

Resolve conflicting grade availability and different active admissions cycles.

Approve the proposed umbrella name and logos

Maintain separate Elementary and Secondary identity until authorized otherwise.

Approve real school photography

Confirm rights and appropriate student-photo permissions.

Verify operating charity wording

Confirm Guidance College name, registration status and relationship to both schools.

Admissions & charitable giving

Verify both school-specific application journeys

Check available grades, tuition, dates, assessments and backend destinations.

Review secure handling of admissions data

Do not collect student documents with an unapproved or unsecured form.

Reconcile donation recipient and payee

Confirm authorized beneficiary, issuing charity and receipt details.

Validate official payment destinations

Test links and approved sandbox-mode integration; do not send real money to test.

Verify fundraising statements

Avoid unapproved targets, deadlines, fund designations or progress amounts.

Experience, quality & production

Test all routes and primary CTAs

Verify both schools, academic programs, Apply, Donate, Guidance, About and Contact.

Test responsive and orientation layouts

320, 375, 390, 430, 768, 1024, 1440 and 1920px; check overflow and clipping.

Complete automated and manual accessibility review

WCAG 2.2 AA target, keyboard focus, alt text, touch targets and screen-reader checks.

Validate motion controls and fallbacks

Pause Motion, prefers-reduced-motion, no blocked links and no scroll hijacking.

Validate SEO and social sharing

Titles, descriptions, canonical, robots, sitemap, structured data, OG images and WhatsApp crop.

Approve analytics and privacy settings

Avoid sending student identity, medical or payment information to analytics.

Record actual performance testing

Lighthouse and Core Web Vitals, where measurable; do not fabricate scores.

Approve domain migration and redirects

Prepare 301 mapping, but do not activate before domain and school approvals.

Sign off production readiness

Resolve all critical/high issues; label blocked and untested checks accurately.

Local-browser tracker only. Verified means a reviewer marked the item verified; it is not an automated test result. Export and save a copy before changing browsers.

Type a keyword to find the relevant section.