Every layout is built to hold together across phone, tablet and desktop — not just scaled down, but reconsidered at each breakpoint so navigation, type and imagery all still make sense on a small screen.
Web Development · Cape Town
Web Development for Interfaces Built to Perform.
Design is only half the job — the code underneath decides whether a site actually feels fast, works on every device, and holds up as content and traffic grow. Poke Digital hand-codes every build from Cape Town, rather than assembling it from a page-builder template.
Semantic markup, clean CSS architecture and JavaScript that's scoped to what a page actually needs — no bloated frameworks loaded for a handful of interactions. The result is a codebase that's easier to read, easier to extend, and lighter for a visitor's browser to run.
Scroll-driven reveals, custom cursors, subtle motion and — where a brief calls for it — WebGL detail work, all built with intent and gated behind prefers-reduced-motion so the experience stays accessible for visitors who need it toned down.
Image compression, lazy loading below the fold, minimal render-blocking resources and disciplined use of third-party scripts — all measured against Core Web Vitals (LCP, INP, CLS) rather than left to chance.
Selected work
View all work →Keyboard-navigable menus, meaningful focus states, proper form labelling and alt text that describes rather than stuffs keywords. Accessible code is also, almost always, better code for search engines to crawl.
Content that exists in the HTML rather than only appearing after JavaScript runs, clean URL structure, canonical tags and structured data — the groundwork covered in full on our SEO-ready websites page.
When a project needs client-editable content — menus, listings, articles, galleries — we build or integrate a CMS around that specific workflow rather than forcing content into a rigid template. More on CMS development.
Code that's readable and sensibly structured is code that can be handed off, extended or maintained by someone else later without a rebuild. We document what a future developer — including a future version of us — would actually need to know.


