# postcss Published articles for postcss. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 🔥 TailwindCSS v4 DevFeed: [🔥 TailwindCSS v4]() Original publisher: [Read original article]() Author: Mads Brodt Published: 2024-03-13T16:01:41Z Content type: article Language: en Sources: [Front-End Focus]() Topics: [Tailwind CSS](), [CSS Framework](), [CSS](), [Front end](), [PostCSS](), [Rust]() Tags: [css](), [postcss](), [rust](), [tailwind](), [tailwindcss]() ### AI overview This article previews TailwindCSS v4 and highlights its proposed CSS-first configuration model, reduced setup requirements, and a new Rust-powered engine advertised as up to 10 times faster. It also mentions container queries, composable variants, and transpilation support for some modern CSS features in older browsers. ### Source excerpt If you've been following the newsletter for awhile, you know that I'm a big fan of TailwindCSS. ## A Vite Buildchain for Craft CMS Plugins & Modules DevFeed: [A Vite Buildchain for Craft CMS Plugins & Modules]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2021-05-17T04:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Vite](), [Content Management System](), [Tailwind CSS](), [JavaScript](), [CSS](), [modules](), [PostCSS]() Tags: [buildchain](), [builds](), [cms](), [composer](), [craft](), [css](), [developer-experience](), [drop-in](), [giving](), [insights](), [javascript](), [module](), [modules](), [optimized](), [plugin](), [plugins](), [postcss](), [production](), [replacement](), [tailwind](), [tailwind-css](), [vite]() ### AI overview This tutorial explains how to add a Vite buildchain to Craft CMS plugins and modules. It covers TypeScript, Hot Module Replacement for CSS, JavaScript, and Twig templates, Vue.js 3, Tailwind CSS with JIT, PostCSS, and optimized production builds with Rollup and content-hash versioning. ### Source excerpt A drop-in buildchain you can use in your Craft CMS plugins and modules, giving you Hot Module Replacement for JavaScript, Tailwind CSS, and optimized production builds. ## Speeding Up Tailwind CSS Builds DevFeed: [Speeding Up Tailwind CSS Builds]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-10-13T12:29:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Tailwind CSS](), [build times](), [PostCSS](), [Development](), [Web Development]() Tags: [build](), [build-times](), [builds](), [css](), [development](), [frontend](), [how-to](), [insights](), [learn](), [live](), [local](), [magnitude](), [make](), [module](), [optimize](), [orders](), [performance](), [postcss](), [reload](), [replacement](), [tailwind](), [times]() ### AI overview A tutorial on optimizing Tailwind CSS builds in local development. It explains how splitting CSS imports can avoid reprocessing the full Tailwind utilities stylesheet during ordinary CSS changes, improving Hot Module Replacement and Live Reload responsiveness. ### Source excerpt Learn how to optimize your Tailwind CSS PostCSS build times to make local development with Hot Module Replacement or Live Reload orders of magnitude faster! ## Using Tailwind CSS with Gatsby, React & Emotion Styled Components DevFeed: [Using Tailwind CSS with Gatsby, React & Emotion Styled Components]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2019-10-20T14:08:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Tailwind CSS](), [gatsby](), [React](), [styled-components](), [CSS](), [PostCSS](), [Babel](), [Web Development]() Tags: [babel](), [components](), [css](), [css-in-js](), [emotion](), [gatsby](), [insights](), [learn](), [postcss](), [project](), [react](), [styled](), [styled-components](), [tailwind](), [tailwind-css](), [utility-first]() ### AI overview A tutorial on combining Tailwind CSS with Gatsby and React through Emotion Styled Components. It explains a hybrid setup using twin.macro for component-level Tailwind styles and PostCSS for Tailwind's base and global styles. ### Source excerpt Learn how to use the utility-first Tailwind CSS with Emotion "CSS-in-JS" Styled Components in a Gatsby JS + React project. ## Marvin v1.0 DevFeed: [Marvin v1.0]() Original publisher: [Read original article]() Author: Stanko Published: 2018-01-05T00:00:00Z Content type: release Language: en Sources: [Stanko Tadić]() Topics: [Boilerplate](), [React](), [Redux](), [PostCSS](), [async](), [data]() Tags: [async](), [boilerplate](), [postcss](), [react](), [redux](), [v1]() ### AI overview Marvin 1.0 is a universal React boilerplate release. The update replaces redux-thunk with redux-saga, adds server-side asynchronous data fetching with results stored in Redux for client reuse, and replaces Sass with PostCSS. The author describes the setup as opinionated and intended as a modifiable starting point. ### Source excerpt Marvin just got better! Few days ago I've released version 1.0 of my universal React boilerplate.Also known as Marvin There are some big changes, and I'm pretty happy with it's current state. At least 20 applications were shipped using Marvin. It has about seven hundred stars on GitHub with quite a few community contributions. Big updates # Switch from redux-thunk to redux-saga. Sagas are bit more complicated but they make managing asynchronous actions easier. They are really powerful and something I usually go for. Thunks are good for smaller apps, but they tend to get messy as application grows. Straight from redux-saga docs: Contrary to redux thunk, you don't end up in callback hell, you can test your asynchronous flows easily and your actions stay pure. Universal async data fetching using sagas. This was one of the most requested features. Marvin now supports getting the async data on the server. Data is then saved to the redux store for client to reuse. Example is included, but I plan to write more detailed documentation on it. Switch from SASS to postcss. It is time to move on. SASS is awesome, but PostCSS caught up, and it is future proof. Plus, if you are using Autoprefixer you are already using it anyway. I could write whole article about it, but people already did it and you can read them here. It is opinionated # These changes and overall setup are very opinionated and crafted by our experience and needs. It is made to be starting point for us, and it might not be the best choice for you. Although, I personally think it is pretty easy to modify it to fit custom needs. If you use Marvin please leave a comment here or on the repo. Thanks!