← Back to Blog

Designing and Deploying Client Websites

Published: October 2026 | Category: Web Design & Deployment

Alongside the AI systems, I design and ship websites for small businesses and NGOs — layout, visual system, motion, front-end build, hosting, DNS and TLS. Two recent builds show the range: a fashion house with an admin console, and a therapy NGO that has to work on a cheap phone as well as a laptop.

Both are preview builds, so there is no public domain to click through yet. The walkthroughs are the demo.

BEM Africa: a scroll-driven fashion house site

The brief was a site that behaves like a lookbook rather than a catalogue. The homepage is built around a scrolling editorial sequence — full-bleed imagery, staged reveals and motion transitions between looks — with the collection, story and contact routes hanging off it.

Behind the site sits an admin console for products and content, so the client is not emailing a developer to change a hero image.

BEM Africa — public site and admin console walkthrough.

Mind Renewal Care: a therapy NGO site

This one is the opposite discipline. The audience arrives anxious and often on a phone, so the site leads with clarity: what the service is, who delivers it, what a session involves, and a single obvious action — schedule a session.

Service cards cover psychiatric care, counselling and community programmes; the team, approach and impact sections carry the credibility; and the whole layout collapses cleanly to mobile instead of being an afterthought.

Mind Renewal Care — desktop and mobile walkthroughs.

How I ship a site

LayerWhat I actually do
DesignType scale, colour, spacing and a page system that survives real content, not lorem ipsum.
BuildSemantic HTML/CSS, responsive layout, motion that respects reduced-motion, images sized for the connection.
HostingCloudflare Pages or Workers for static and edge, Netlify where forms and previews fit better, Hugging Face for anything ML-backed, or a hardened VPS with Nginx when the site needs a server.
DomainDNS, TLS and WAF at Cloudflare; self-hosted mail on the same domain when the client wants their own inboxes.
After launchMonitoring, uptime checks and a deployment path that does not require me to be awake.

What the two builds have in common

  1. The site is a product, not a poster. If the client cannot update it, it is not finished — hence the admin console on BEM Africa.
  2. Mobile is the default. The therapy site was designed at phone width first and expanded up.
  3. Motion is a tool, not decoration. Scroll animation earns its place only when it carries the reader forward.
  4. Deployment is part of the work. A design that is not live, fast and reachable is a mock-up.

Related

Author: Agu Chiedozie | Cloud & AI Systems Engineer