# Error when compiling with fonts

**URL:** https://discourse.roots.io/t/error-when-compiling-with-fonts/20947
**Category:** sage
**Tags:** webpack
**Created:** 2021-06-13T20:45:36Z
**Posts:** 20
**Showing post:** 13 of 20

## Post 13 by @strarsis — 2021-06-15T00:47:18Z

So I did a test with Sage 9.x release and Sage 9.x update branch and noticed that albeit there is a `fonts/` folder in `assets/` (using a `.gitkeep` placeholder), there is webpack config in place to copy it over to `dist/...`.  
So this has to be added for Sage 9 themes that need `fonts/` in `dist/...`

See this discussion:

> [@External fonts in folder](https://discourse.roots.io/t/external-fonts-in-folder/9533):
>
> Hi there, (I actually had this issue last year, and never figured it out, so have been copy/pasting from /assets/ to /dist/ since then!). I’m using some [Typography.com](http://Typography.com) fonts, and the way they work (frustratingly) is to provide you with a JS snippet for you site’s head region (pretty standard), but also a folder, named with a random number (in my case 569789), containing production CSS for the fonts, like so: [Typography.com](http://Typography.com) then asks you to let them know the location of this folder o…

One doesn’t have to use the `copy` plugin - depending on the workflow and conversion/style needs, one can also use something like [`postcss-font-magician`](https://github.com/csstools/postcss-font-magician) (this was more important in the past, now all browsers support WOFF/WOFF2).

---

_[View the full topic](https://discourse.roots.io/t/error-when-compiling-with-fonts/20947)._