Classic Editor vs TailPress – Tailwind for WordPress

Classic Editor is an official plugin maintained by the WordPress team that restores the previous (“classic”) WordPress editor and the “Edit Post” screen. It makes it possible to use plugins that extend that screen, add old-style meta boxes, or otherwise depend on the previous editor. Classic Editor is an official WordPress plugin, and will be fully supported and maintained until 2024, or as long as is necessary. At a glance, this plugin adds the following: Administrators can select the default editor for all users. Administrators can allow users to change their default editor. When allowed, the users can choose which editor to use for each post. Each post opens in the last editor used regardless of who edited it last. This is important for maintaining a consistent experience when editing content. In addition, the Classic Editor plugin includes several filters that let other plugins control the settings, and the editor choice per post and per post type. By default, this plugin hides all functionality available in the new block editor (“Gutenberg”).

Tailwind CSS is a great companion to building block based sites in WordPress. Unfortunately, it’s been pretty complicated to add Tailwind CSS to WordPress since it needs to be compiled with Node.js in order to be production ready. This plugin takes care of that by adding Tailwind CSS to WordPress in one easy step (activate the plugin) and at the same time takes care of performance and caching so your site remains fast and production ready! Who It’s For This is primarily for developers and users that are familiar with Tailwind CSS and comfortable styling their site using their utility class framework. It’s also for those who have struggled to add Tailwind to their workflow without having to constantly compile their CSS every time the classes in their page content changes. How it Works Extracts classes from pages and compiles them server-side into Tailwind CSS Caches the dynamically generated CSS to avoid performance issues on the frontend of your production site. Are you affiliated with tailpress.io the theme? No, we are not! Unfortunately the same name was used for both out of coincidence, but we are not affiliated and are two different solutions. Tailpress.io is a great starting point for developing custom themes with deep integration of Tailwind. I would recommend it for any developer that wants to build a custom theme that depends heavily on Tailwind. Tailpress, this plugin, adds Tailwind support to any project as an add-on. It can be used as much or as little as you need, added to custom themes or pre-existing ones. Can this be used in production? Yes! Although the styles in the backend get generated on the fly, the CSS on the frontend gets cached for every page. Changing any classes on the page will bust the cache automatically so it’ll still stay up to date with any changes. Can this be used outside the block editor? Yes! This will work anywhere on the backend or front end of your site that uses classes to style things. Known Issues Device Preview Mode in Block Editor The non-desktop preview modes in the block editor utilize an iframe and don’t load assets properly. Therefore your Tailwind styles won’t be visible here. Page Caching If you have any page caching on your site, you’ll have to clear your cache for the best experience.