Responsive Navigation Block vs TailPress – Tailwind for WordPress

This Plugin allows you to display and apply alternative styling to different navigation menus based on the screen size using the WordPress Navigation block. Video Walkthrough Features Two new Navigation Block (variations) for: Mobile Desktop Style your menu differently depending on screen size. Use a different menu for each screen size. Customize the “breakpoint” (where you switch between mobile and desktop). Automatically switch editor to “mobile” preview when editing the mobile navigation. Usage This Plugin creates two block variations from the Navigation block which will be automatically hidden/shown at the configured screensize (breakpoint): Navigation (Mobile) – will be displayed only on smaller screen sizes. Navigation (Desktop) – will be displayed only on larger screen sizes. This affords the ability to independently style mobile vs desktop navigation and even allows for completely different menus to be used. The Plugin should be used as follows: Install and Activate the plugin – two new block variations will be automatically registered for “Mobile” and “Desktop”. Go to the Editor and remove any existing Navigation block. Add the “Desktop Navigation” block – style and configure the menu for “desktop” as required. Add the “Mobile Navigation” block – style and configure the menu for “mobile” as required. View the front of your website and resize your browser to see the navigations swap out at the appropriate breakpoint/screensize. Alternatively you can transform the default Navigation block to either Mobile or Desktop variations via the block’s interface. Support Please see FAQs. If you still have an issue please: check Github for existing Issue reports. (if none) then file a new Issue on Github Privacy Statement Responsive Navigation does not: use cookies. send data to any third party. include any third party resources. Contributing Contributions to this Plugin are welcome. Please fork the Github repository and submit a PR for review. Development Setup This Plugin uses the @wordpress/scripts package. Check out the Github repo into the wp-content/plugins directory of a WordPress installation. cd into the Plugin’s directory install the dependencies with npm i. Running npm start will start the @wordpress/scripts package in watch mode ready to compile the JavaScript on modification. PHP files can be edited in the usual manner. Testing The Plugin has e2e test coverage for the key features courtesey of @wordpress/scripts and Playwright. To run the tests – in your terminal of choice: npm run build. npm run wp-env start. Run the tests: npm run test:e2e Releasing Releasing the Plugin to the WordPress.org Plugin repo is the prerogative of the Plugin owner (@get_dave). The process is as follows: Test the Plugin Commit all changes to trunk branch. Push changes to trunk (only) – git push origin trunk. In Github: Actions Select the Build Release Zip action. Select the Run workflow dropdown and run the workflow to generate a zip file. When action completes download the generated Plugin zip artifact. Manually install and test the .zip. Deploy to WP.org When ready to deploy. Bump Plugin version and tag release – npm run bump-version. Push trunk and tags – git push origin trunk --tags Deployment to WP.org will be handled automatically.

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.