Draft – Tailwind CSS for WordPress.

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

Directory searches this plugin turns up in, and which way each one is moving. WordPress.org publishes no history of search positions, so this starts the day we first tracked a keyword and never backfills.

wp.org is where the directory puts the plugin for that search. On merit is where it would sit if results were ranked on rating, support and updates, without the install boost. The last column is how far the wp.org position moved, from our first reading in the last 90 days to the latest.

6 searches this plugin appeared in over the last 90 days, 3 listed. 3 left out as unrelated or noise (years, numbers, stray words). 2 of its tags aren't in the top 24 for their own search.

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

Share of active installs on each version of this plugin · 100% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

Crossed into this band 5 months ago; a band this size takes about a year or more to cross, which places it about 56% of the way through.

1. ★★★★★ andiganteng

   2.2y ago

   its the best plugin ever i install, so usefull for people stuck in FSE wordpress, with this can full control of Front EndSuper Thanks, God Bless You

   Read on wp.org ↗
2. ★★★★★ sunlifter

   2.3y ago

   — Since WordPress doesn’t allow reviews removal, I’ll leave this here —

   Read on wp.org ↗
3. ★★★★★ hcijr6

   3.3y ago

   I think Gutenberg is flawed in design by not properly defining structural elements such as sections, rows and columns, and by allowing third parties to reinvent the wheel with their own block implementations. It would have been better to have a basic set of blocks in the core, with the ability for third parties to extend and enhance the experience through an API. This would have provided greater security and consistency for page builders. Also, I’d like to acknowledge the hard work you’ve put into your system and how you’ve managed to implement it in an elegant and minimalistic way. It is evident that you have put a lot of effort and dedication into this project. I strongly encourage you to continue developing improvements and expanding your approach to make the block editor even more secure and versatile. Your vision of having a robust set of blocks in core, along with the ability for third parties to contribute their own ideas and improvements via an API, could lead to a more cohesive and enriching experience for all users and page builders. Keep up your innovative approach, as it will undoubtedly continue to have a positive impact on the community and the future of WordPress page development – thank you for your valuable contribution!

   Read on wp.org ↗
4. ★★★★★ irishetcher

   5.0y ago

   Hi Lee, Really enjoyed your demo on the Page Builder Summit yesterday. While I am not a Tailwind CSS user, more a Divi user, I totally agree with the way you have implemented your system from a minimalist point of view, where only the existing blocks in core are extended or, as you have done, reduced to be manipulated with the Tailwind CSS only. So far I have some niggles with the Gutenberg project which I see as fundamental design flaws in the long run; the fact that they didn’t nail the main layout and structural elements (Sections/containers, rows and columns + better responsiveness on device breakpoints ) and make these, along with all the other blocks, a restricted set which third parties could extend, via an API, with their own UI, bells and whistles. So far I see many vendors out there making their own implementations of block sets where they are reinventing the wheel. Seems to me that they are perpetuating the age old problem where, if you disable any one of these solutions you potentially lose content, layout or both, whereas, if WordPress had a core foundation of set blocks, turning off or switching to another solution would retain content and maintain layout to some degree. Having this systematic approach would have had more buy-in from page builder vendors and subsequently a better overall direction in the development of the Gutenberg project. It would have also driven better consistency and interoperability between builders. What you have done makes the whole enterprise of using the block editor “Safer” and in this context third party vendors should only be allowed to override existing blocks in core by plugging in their own UI and features. This topic was modified 4 years, 9 months ago by irishetcher.

   Read on wp.org ↗

1 open vulnerability affects the current version (3.0.9). 0 of 1 disclosed are patched.

1. Open Medium · 4.4 Draft <= 3.0.9 - Authenticated (Editor+) Stored Cross-Site Scripting ↗
   2025-09-22 CVE-2025-58033 Improper Neutralization of Input During Web Page Generation Affects <= 3.0.9 No patch available

Automated install-time checks, tested on PHP 8.1.12 · WP 6.6.2

Whether ChatGPT and Claude name this plugin when asked the category question, and whether the readme gives them something to quote.

Not measured yet for this plugin’s topics. Its tracked searches are not among the measured topics. See the topics measured so far.

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

1. 2026-05-23 700+ → 600+ down after 95 days in tier
2. 2026-02-17 800+ → 700+ down after 20 days in tier
3. 2026-01-28 900+ → 800+ down after 1 days in tier
4. 2026-01-27 1K+ → 900+ down after 411 days in tier
5. 2024-12-12 900+ → 1K+ up after 27 days in tier
6. 2024-11-15 800+ → 900+ up after 21 days in tier
7. 2024-10-25 700+ → 800+ up after 20 days in tier
8. 2024-10-05 800+ → 700+ down after 1 days in tier

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

Embed this report card

Drop a live Pulse card for Draft – Tailwind CSS for WordPress. into a readme, a review or a deck. It updates itself.

Draft – Tailwind CSS for WordPress.: 600+ active installs, 5.0★ (4 reviews). Plugin Pulse (WP Mayor), as of 2026-10-31. https://plugins.wpmayor.com/plugin/website-builder