Blog

Struggling with your WordPress site looking “off” after adding Tailwind CSS? The culprit is often Tailwind Preflight, its powerful reset that clashes with WordPress’s built-in styles. This post cuts through the confusion, explaining why Preflight causes issues and giving you four straightforward solutions—from quick fixes to integrated overrides—so you can get your WordPress site and Tailwind playing nicely together.

This guide walks you through building a VueJS-powered WordPress plugin—from bootstrapping PHP to handling AJAX requests, and tips for using REST API and modern tooling like Webpack or Vite.

Here is a shortened excerpt about the View Transition API, drawing on the sources:
The View Transition API provides a mechanism for easily creating animated transitions between different views on a website. It acts as a native browser mechanism to add captivating animations. This API is beneficial for both multi-page applications (MPA), where it manages transitions between entirely separate pages (known as cross-document transitions), and single-page applications (SPA) or situations where the content changes within a single page (same-document transitions). Using view transitions can significantly reduce users’ cognitive load. They help users stay in context and reduce the perceived loading latency when navigating between states or pages. Historically, creating transitions on the web was difficult. This was especially true for cross-document transitions, which were previously impossible. The View Transition API offers an easy way to handle the necessary view changes and transition animations for both SPA and MPA scenarios. Ultimately, it allows you to add “super cool transitions” to your web applications with greater ease.