Skip to content
IT Services

Jabulani Tech Solutions, Agency Platform

Hand-built agency site with four case studies, a PHP contact pipeline, and local SEO for the Eastern Cape market

Client
Jabulani Group of Companies (South Africa)
Duration
3 weeks
Team
Solo developer
Delivered
June 2026
Jabulani Tech Solutions, Agency Platform, IT Services

The outcome

  • Live and serving the agency enquiries
  • Editable by a non-developer, no compile step
  • Four case studies published

The story

Jabulani Tech Solutions is the IT and web-development arm of the Jabulani Group of Companies in the Eastern Cape, South Africa. The site presents their services, showcases four live systems built for the wider group, and collects qualified enquiries.

The constraint

The host is Hostinger shared hosting, Apache with PHP and no Node runtime. That ruled out any build step, so the whole site is hand-written HTML, CSS and vanilla JavaScript with a single PHP script behind the contact form. Every file can be edited and uploaded directly; nothing is compiled.

Architecture

Five static pages, one per case study plus the home page, sharing two stylesheets and one JavaScript file. Theme state is written to localStorage and read by an inline script in the document head before first paint, so a returning visitor never sees a flash of the wrong theme. The contact form posts to form.php, which sends over authenticated SMTP with credentials kept in a gitignored secrets file and a committed example template alongside it.

Delivery

Apache configuration handles the HTTPS redirect, cache headers and security headers. The site ships robots.txt, a sitemap, Open Graph and Twitter cards, canonical URLs, and geographic meta for Eastern Cape local search. A custom 404 page redirects home rather than dead-ending.

Why it is here

It is the counter-example to the rest of this portfolio. Given a host with no build tooling, the right answer was not a framework, and shipping plain HTML that a non-developer can maintain was the engineering decision.

What made it hard

  1. No build tooling

    Shared hosting with Apache and PHP only, so no bundler, no framework and no npm install in the deployment path

  2. Theme without flicker

    Applying a stored theme before first paint using an inline head script rather than waiting for JavaScript to load

  3. Credential handling

    Keeping SMTP credentials out of version control while leaving the repository reproducible for the next maintainer

Next projectJabulani Point of Sale
Open for new work

Have a system that needs to scale?

Bring your architecture problem, automation bottleneck, or product idea. We will work out the right engineering path before you spend more time or money.

Free, 30 minutes, no pitch. You leave with a next step either way.