Overview
The two sites
NTA Therapy (ntatherapy.com)
- Multi-page marketing IA: home, about, services, FAQ, contact, privacy
- Calm visual language matched to the clinical brand
- Booking and contact CTAs wired to the practice’s real workflows (Jane App / email / phone as provided)
- Next.js + MUI so content sections stay structured and easy to extend
Imad Al Rifat (imadalrifat.ae)
- Compact brochure IA: home narrative, why rent, product list, about, contact
- Bilingual-aware branding (English primary; Arabic present in the logo lockup)
- Astro + Tailwind for a fast static export with sitemap support
- Emphasis on clarity and trust over interactive product UX
Tech Stack & Rationale
Engineering Trade-offs
- Stack per client, not one house style. NTA’s longer, section-heavy marketing site fit Next + MUI. Imad’s brochure fit Astro static. Forcing one stack would have optimized for my convenience, not theirs.
- Scope discipline over portfolio flex. These are marketing sites. Overbuilding (CMS, animations for their own sake, custom admin) would raise cost and handoff risk. The win is a live URL that matches the brief.
- Content structure in code. Until a client needs non-dev editors, typed sections and markdown/static pages beat introducing a CMS. Hand-off is git + clear page files, not a training workshop.
- SEO as basics, not a campaign. Titles, descriptions, sensible headings, sitemap where it helps. Enough for a new local/B2B site to be findable; not a growth-marketing engagement.
Outcome
- End-to-end client delivery: brief → IA → UI → launch
- Judgment about when a thin static or marketing site is the right product
- Comfort shipping in more than one frontend stack
- Backend platforms, data pipelines, or AI systems (see other projects for that)