5+ years building pixel perfect, production ready WordPress experiences, with 40+ template packs personally developed for an ecosystem of 700K+ users.
Stack
Focus
Over five years of production WordPress, built around Elementor and Gutenberg, and around getting an implementation to match its design exactly.
Production template packs and client editable sites built in Elementor: custom layouts, responsive breakpoints, and structure that survives real content.
Native block editor builds: block patterns, reusable layouts, and clean semantic structure that stays fast without a page builder runtime.
I translate design specifications into production ready builds, working directly with designers and QA until the implementation matches the reference at every breakpoint.
Expert level experience implementing and maintaining Templately’s Global Style and Typography systems across template packs. I am the internal reference for it on my team.
Store and site work on live installs: WooCommerce layouts, theme customisation, plus the update and maintenance workflows that keep a site ecosystem healthy.
Handwritten HTML, CSS, JavaScript and React where a builder is the wrong tool, plus WordPress migrations, WordPress to Astro work, and automating repetitive maintenance.
Production template packs I personally built for the Templately library: Elementor and Gutenberg, live and in use by hundreds of thousands of WordPress makers.
A conversion focused SaaS marketing pack with pricing, feature, and onboarding sections. I built every page in Elementor from the design reference, pixel perfect and fully responsive across breakpoints.
A consultancy pack I built natively in the block editor: clean block structure, accessible markup, and layouts that stay easy to edit after handover.
A travel booking pack with search focused layouts and trust building sections, built and shipped by me in Elementor. One of the 40+ packs I have developed for Templately.
A WordPress automation tool I built to streamline repetitive maintenance across Templately’s multisite template pack environments. It started with plugin installs and updates and has since grown past that.
Contributing to production WordPress to Astro migrations on the team, including the ongoing migration of easy.jobs, rebuilding WordPress front ends as static Astro sites.
Over five years of production WordPress, a pixel perfect habit, and the scale of a 700K+ user template library behind it. Currently looking for a remote WordPress / Web Developer role.
Get in touchDeveloper tools I'm building and sharing publicly, with more on the way.
Point it at a URL and get a DESIGN.md: automatic design token extraction (colors, type, spacing, radius) from any live site, ready for your coding agent.
An end to end data pipeline: it crawls news sources, uses AI to classify and geotag each incident, stores it in Postgres, and renders everything on a live, filterable map with charts, from scraper to dashboard.
More tools are in the works. I'm building open source projects regularly now. Follow along.
Follow on GitHub ↗Over five years of frontend work, more than three of them building production WordPress at the scale of a template marketplace serving 700K+ users.
Building production WordPress template packs for Templately, split roughly 50/50 between Elementor and Gutenberg, in a workflow where pixel perfect implementation is the baseline requirement.
Built functional websites for marketing focused client projects, learning to structure sites with SEO in mind: content hierarchy, usability, and search engine friendly markup.
Developed websites and web applications, working inside existing PHP codebases and turning designs into pixel perfect frontends.
Design → development → responsive implementation → QA → refinement. The last stage is the one that decides whether a build matches its design.
I start from the design reference (Figma files or a spec from the design team) and read it closely enough to catch what is ambiguous before building anything.
The build itself, in Elementor or Gutenberg: real structure, reusable patterns, and content that stays editable by whoever inherits it.
Every breakpoint handled deliberately rather than left to the builder’s defaults, so the layout holds from wide desktop down to small phones.
QA reviews the build, I work with them and the designer through the findings, and refine until the implementation matches the design.
The things a hiring team usually wants to know first.
A remote WordPress / Web Developer role, full time. My day to day is production WordPress (Elementor and Gutenberg), and that is the work I want to keep doing on a product or agency team.
Both, at roughly a 50/50 split across the 40+ template packs I have developed. I am equally comfortable being handed either, and comfortable saying which one fits a given build better.
I implement from the design reference rather than designing it myself, then work directly with the designer and QA through review rounds until the build matches at every breakpoint. Design → development → responsive implementation → QA → refinement.
Expert level, and it is the area I am the internal reference for on my team: implementing and maintaining Global Style and Typography systems consistently across template packs.
I am based in Dhaka (GMT+6) and I overlap comfortably with EU mornings and early US hours. My current work is already collaborative across designers, QA, and a 4-member development team I coordinate.
HTML, CSS, JavaScript and React on the frontend; PHP and MySQL on the back; Git and GitHub day to day. I also build internal automation, and I am contributing to production WordPress to Astro migrations.
Currently looking for a remote WordPress / Web Developer position. Send over the details and I'll reply quickly.