About Monowar Hossain
My name is Monowar Hossain. I am a WordPress plugin developer from Dhaka, Bangladesh, known online as devmonowar — I maintain six free plugins on WordPress.org, published since 2021, with the source on GitHub.
Who I am
I build things for WordPress, and almost all of it is free and open source — anyone can download it, read the code, and change it. Twelve public repositories carry the work, and every plugin goes through the WordPress.org review before release.
Right now I maintain a set of plugins published on WordPress.org, and I run a shared demo library that shows what every ready-made demo looks like before anyone imports it.
How I started
I finished a Diploma in Engineering at Magura Polytechnic Institute in 2016. I did not begin with WordPress. I started with plain HTML and CSS, then moved to PHP because I wanted to understand what was actually happening behind the pages I was putting together.
WordPress kept me for one simple reason: when something did not work the way I wanted, I could open the code and fix it. That is exactly how my first plugin began. I needed a slider that did not slow a site down, I could not find one I was happy with, so I wrote my own. Later I cleaned it up and published it on WordPress.org so other people could use it too.
How I work
Every plugin I have released follows the same three rules, and they came from problems I hit myself.
- Load only what the page needs. A plugin should not add CSS and JavaScript to pages that do not use its feature. This is the single most common reason a WordPress site gets slow, and it is avoidable.
- Do one job properly. I would rather ship a plugin that does testimonials well than an addon pack with dozens of widgets where you use three and pay for the weight of the rest.
- Be honest about limits. If a plugin cannot be certain about something, it should say so instead of guessing. That idea shaped Janitorix Media Audit completely — it refuses to recommend deleting an image unless it can show the evidence behind that verdict.
What I build and why
None of these started as a product idea. Each one started as something that annoyed me on a real site.
- General Slider — I needed a slider that loads fast and still works for someone using a keyboard or a screen reader. Most sliders are heavy and skip the accessibility part entirely.
- Advanced Testimonial — a client wanted the same customer reviews in several places on their site, each in a different layout. Copying the text meant several places to update every time a review changed.
- Free Widgets For Elementor — Elementor's free version is missing a few widgets nearly every site needs. The usual fix is a giant addon pack. I built a focused alternative instead.
- Janitorix Media Audit — media libraries fill up with images no page uses any more, and the existing cleanup tools mostly guess. Leaving an unused image costs a few kilobytes; deleting one that is still referenced breaks the site. Those two mistakes are not equal, so the plugin does not treat them as equal. The method it uses is written out in full: how to find unused images in WordPress.
- CrawlWatch – AI Bot Insights — AI assistants had been reading my site for months and I had no way of knowing it. Analytics does not count a crawler, and the server log is not something most site owners will ever open. So the plugin logs those visits, shows which pages were taken, and lets you allow or block each bot without writing a line of
robots.txtby hand. - ScheduleLens – Cron Viewer & Manager — WordPress runs its scheduled jobs invisibly, so a missed schedule always looks like some other bug. I wanted one screen that lists every job in plain words and lets me run or pause it there — and a health check that admits when the quiet site itself is the problem.
- Alo Blog — after six plugins, the theme questions in every support thread pushed me to build one: a quiet, fast writing theme with no builder, no slider, and no upsells. The story is in the launch post.
Open source
I keep my work free because that is how I learned. When I was starting out I read other people's plugin code to figure out how WordPress really worked. That code was free for me, so mine is free too.
Free does not mean unfinished. Every plugin goes through the WordPress.org review before release, ships with documentation and a changelog, and I answer the support topics on the forum myself. If something is broken, I would much rather hear about it and fix it.
What I am learning now
Two things have most of my attention. The first is performance — how to keep a plugin small enough that adding it to a site is not a trade-off. I wrote up what actually makes a WordPress slider slow and how to measure it yourself. The second is accessibility, which I did not take seriously enough early on: making sure what I build works with a keyboard and a screen reader, not only with a mouse.
Writing the guides on this site is part of how I work on both. Explaining something to another developer is the fastest way to find out whether I actually understand it — and it is usually while writing the steps down that I notice the one I had been getting away with.
Quick facts
- Name Monowar Hossain
- Known online as devmonowar
- Title WordPress Developer · Plugin Developer · Open Source Contributor
- Location Dhaka, Bangladesh
- Works with WordPress, PHP, JavaScript, Elementor, ACF, HTML, CSS, Git
- Education Diploma in Engineering, Magura Polytechnic Institute (2016)
- Email devmonowar@gmail.com
Find me online
- GitHub github.com/devmonowar
- WordPress.org profiles.wordpress.org/kstmonowar
- LinkedIn linkedin.com/in/devmonowar
- Facebook facebook.com/devmonowarwp
- Threads threads.com/@devmonowar
- Stack Overflow Monowar Hossain
- Medium medium.com/@devmonowar
- Mastodon mastodon.social/@devmonowar
- Dev.to dev.to/devmonowar
- Instagram instagram.com/devmonowar
- Pinterest pinterest.com/devmonowar
- Packagist packagist.org/packages/devmonowar
- Demo library WordPress Plugin Demo Library