Draft – Tailwind CSS for WordPress.

Description

Install the free plugin and start using Tailwind CSS in WordPress, instantly.

? Start using Tailwind CSS in WordPress in seconds, no setup required.
?? Effortlessly configure Tailwind CSS right from WordPress.
?? Build even faster with 50+ responsive, copy & paste block patterns.

Current Tailwind CSS version: 3.4.5

How It Works:

• Install free Draft plugin
• Configure Tailwind CSS right in the page, post, or site editor or from WP Admin > Settings > Draft settings
• Add Tailwind CSS utility classes to blocks
• Go Pro to improve site performance by purging unused CSS

Free plugin features:

• Configure Tailwind
• Add Custom CSS ( including ability to @apply Tailwind CSS utility classes )
• Add Tailwind CSS utility classes to Gutenberg blocks
• Add Tailwind CSS utility classes inline to text ( such as headings and paragraphs )

Pro plugin features:

• Purge Unused CSS ( make your WordPress site blazing fast )

Block-Editor Add-ons:

• Dark mode toggle block – add dark mode toggle blocks anywhere to toggle using the Tailwind CSS darkMode ‘selector’ strategy
• Group block link – add links to the Group block for creating linkable cards and layouts
• Archive title filter – add text before/after archive titles for better archive labeling
  Go Pro

Free full-site-editing (FSE) block theme:

Learn more

Free ready-to-use copy & paste block patterns:

Explore patterns

Free ready-to-use copy & paste block templates:

Explore templates

Free Video Tutorials

Learn how to speed up your development by adding Tailwind CSS utility classes to Gutenberg blocks:
Tutorials

Copyright

Draft WordPress Plugin, Copyright 2021 leeshadle
Draft WordPress Plugin is distributed under the terms of the GNU GPL

Screenshots

Installation

This section describes how to install the plugin and get it working.

e.g.

1. Upload the draft plugin files to the /wp-content/plugins/ directory, or upload the draft.zip file through the WordPress plugins screen directly by clicking ‘Add New’ and selecting the zip file from your computer.
2. Install and active the Gutenberg WordPress plugin.
3. Activate the Draft plugin through the ‘Plugins’ screen in WordPress.
4. Use the Draft plugin on your pages and posts.

FAQ

Will TailwindCSS utility classes conflict with other plugins?

If they’re using the same utility classes it may override them. You can always configure the Tailwind CSS to use a prefix if you need a different namespace.

What themes is the Draft plugin compatible with?

Any theme built for the Gutenberg editor.

Reviews

i love you who make this

andiganteng August 6, 2024 1 reply

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

This guy developed a price tag on top of free software

sunlifter July 7, 2024 3 replies

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

Impressive work, the future of worpress

hcijr6 July 29, 2023

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!

How it should be done

irishetcher October 22, 2021

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.

Contributors & Developers

Changelog

3.0.9

• Fix bug – nested CSS was not applying properly

3.0.8

• Updating Tailwind CSS to version 3.4.5
• Update PluginSidebar components for WordPress 6.6 compatibility
• Update saving plugin settings to work when custom fields are present in post editor

3.0.7

• Updating blueprint for plugin Playground

3.0.6

• Add blueprint for plugin Playground

3.0.5

• Fix bug by removing welcome guide

3.0.4

• Fix bug preventing settings from saving (update slug – no longer import slug from package.json)
• Update compatibility to WordPress 6.5
• Update default config to include defaults for primary, secondary, text, and accent tokens
• Update default CSS to include ‘text-balance’ utility for headings, slight styling updates (h1 font size, images, dark mode default font color)

3.0.3

• Fix bug toggleFeature bug that crashed editor

3.0.2

• Fix bug that prevents styles from loading in block editor where metaboxes/custom fields are visible

3.0.1

• Fix bug that prevents styles from loading in block editor where metaboxes/custom fields are visible

3.0.0

• Update to latest version of Tailwind CSS (version 3.4.1)
• Add inline Tailwind CSS classes (ie – highlight or underline parts of a heading w/ inline utility classes)

2.0.0

• Complete Plugin rebuild
• Completely customize your Tailwind CSS configuration as you would outside of WordPress
• Add Custom CSS and leverage Tailwind directives such as @apply, @layer, etc.
• Updated Default Tailwind CSS configuration for building block patterns, pages, and websites

1.0.1

• Updating Plugin Settings – Removing core ColorPalette component from TailwindCSS Color configuration settings. New ColorPalette component was breaking the editor. Will work on finding an alternative.

1.0.0

• Release