fontsFolder

Author: oscarotero

posts/lume-3.md

@@ -278,26 +278,31 @@ Or with a custom title
 <!-- <h1>New title</h1>  -->
 ```
 
-## Global cssFile and jsFile
+## Global cssFile, jsFile and fontsFolder
 
 As mentioned, Lume components can output CSS and JS code. However, some plugins
 output code too. For example, `google_fonts` generates the CSS code needed to
 load the fonts, `prism` and `code_highlight` export the CSS code with the
-themes, etc.
+themes, and `katex` (that didn't generate CSS code in Lume 2) now generates the
+CSS code automatically so you don't need to copy manually the CSS code.
+
+Additionally, some plugins download also font files (specifically,
+`google_fonts` and `katex`).
 
 In Lume 2, you have to configure how to export the generated code for every
-plugin individually. In Lume 3 there are two global options that will be used by
-default by all plugins and components:
+plugin individually. In Lume 3 there are three global options that will be used
+by default by all plugins and components:
 
 ```js
 const site = lume({
   cssFile: "/style.css", // default value
   jsFile: "/script.js", // default value
+  fontsFolder: "/fonts", // default value
 });
 ```
 
 All extra code generated by components and the plugins `code_highlight`,
-`google_fonts`, `prism`, and `unocss` will store the code in these files.
+`google_fonts`, `prism`, `katex` and `unocss` will be stored there.
 
 Of course, you can still change the code destination for a specific plugin: