This plugin hasnt been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
Learn how to speed up your development by adding Tailwind CSS utility classes to Gutenberg blocks: Tutorials
Draft Pro WordPress Plugin, Copyright 2021 leeshadle
Draft Pro WordPress Plugin is distributed under the terms of the GNU GPL
This section describes how to install the plugin and get it working.
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.
Install and active the Gutenberg WordPress plugin.
Activate the Draft plugin through the ‘Plugins’ screen in WordPress.
Use the Draft plugin on your pages and posts.
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.
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!
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.