open to work · remote worldwide

I build websites that just work.

I'm Ibraheem, a freelance web developer. I build sites on WordPress and Webflow, or hand-code them with Hugo and Jekyll when speed matters more than a dashboard — then stay on to keep them running. Remote, worldwide.

  • scope agreed up front
  • tested on real devices
  • handover included
ibraheem.js
const ibraheem = {
  role:   "web developer",
  stack:  ["wordpress", "webflow", "hugo"],
  works:  "remote, worldwide",
  status: "available"
};

ship(ibraheem); // ✓ handover included

what i do

Skills & Tools

six things I do · one person, start to finish

  • CMS builds

    WordPress, Webflow, Wix and Drupal. Custom themes, the plugins you actually need, and an admin your team can post to without calling me.

  • Static sites

    Hugo and Jekyll when a site should be quick and low-maintenance. Hand-written HTML and Tailwind CSS, nothing to patch every month.

  • Responsive layouts

    Built mobile-first, then checked on real phones and tablets rather than a resized browser window. Includes the awkward in-between widths.

  • Performance & SEO

    Compressed images, lean CSS, sensible heading structure, meta tags and a sitemap that's actually correct. Faster pages are cheaper to run and easier to find.

  • Launch & upkeep

    Hosting, DNS, SSL, redirects and migrations. Then I stay available for the small fixes and content changes most projects forget to budget for.

  • Working together

    You send what you have, I ask questions until the scope is clear, then you get a staging link to react to instead of a reveal at the end.

recent work

Shipped & Live

live sites · most recent first

how i work

My Process

4 steps · how a project actually runs

  1. understand

    Who the site is for, what it has to do, and what counts as finished. We agree that in writing first — it's the cheapest way to avoid a rebuild later.

  2. build

    CMS if you'll be updating it weekly, static if you won't. You get a staging link early and watch it come together, rather than seeing it once at the end.

  3. test

    Chrome, Safari and Firefox, on real phones as well as desktop. Forms get submitted, links get clicked, page weight gets checked before anything goes live.

  4. deliver

    DNS, SSL, redirects and analytics, plus notes on how to run the thing. You own the accounts and the code — I'm around afterwards, not required.

process.sh — bash

$ ./process.sh --client "your-project"

understand  scope agreed in writing

build  staging link from week one

test  real devices, real browsers

deliver  dns, ssl, handover notes

done — 4/4 steps passed · ready to ship

$

let's talk

Tell me what you're building.

New builds, rebuilds, and the unglamorous fixes on sites that already exist — all remote. Send me what you have and I'll tell you straight whether I'm the right person for it.