# Setting up Critical CSS in Sage 10: Best Practices and Recommendations? **URL:** https://discourse.roots.io/t/setting-up-critical-css-in-sage-10-best-practices-and-recommendations/26039 **Category:** sage **Tags:** bud, critical-css, sage10 **Created:** 2023-09-28T21:25:53Z **Posts:** 2 **Showing post:** 2 of 2 ## Post 2 by @talss89 — 2023-09-29T10:18:23Z Hi @Dogit, 1. **How do I best integrate a tool/package like `@roots/bud-criticalcss` into the Sage 10 build process?** `bud-criticalcss` has worked fine for me, despite being experimental. Conditionally enabling it based on `isProduction` as per the [example](https://bud.js.org/extensions/bud-criticalcss#example) is the way to go. You’ll find emitted styles in `./public/css/critical/..css`. To make it more portable, I’ve set the `src` to `process.env.WP_HOME`, but that may not be appropriate for you. `bud-criticalcss` doesn’t appear to support multiple sources and multiple critical css outputs, so if you need multiple entries, may may need to come up with another approach. 2. **Once the critical CSS is generated, how do I inline it effectively in my Blade templates?** AFAIK, this is a developer decision. I would use [`$asset->contents()`](https://roots.io/sage/docs/compiling-assets/) to leverage Acorn to deal with your asset manifest and grab the contents. Then hook into `` and output the `