\n Denmark has 5 million people.I made that up\n
\n`` Then add a liquid variable where ever you want your compiled footnotes to\nappear. ```liquid {{ footnotes }}\n````\n\nAs liquid templates are evaluated before markdown conversion, and the footnotes are compiled after markdown conversion, `magicbook` will first insert a placeholder string during the liquid processing, and then later in the build process replace this placeholder with the output of a special include named `footnotes.html`. To generate a footnotes, you must have this include in your includes folder. The include will have access to the following array of footnotes:\n\n```js\n[\n {\n id: \"fn1\",\n label: \"Text of footnotes\"\n }\n];\n```\n\nAll projects created with `magicbook new` will have a `footnotes.html` include, and that's a good reference to see what's possible.\n\n## Images\n\nWhen you want to insert an image, simply create a folder called `images` in your book, save your image into this folder, and create an image tag using the name of your image.\n\nFor an image saved to `images/myimage.jpg`, the following would be the appropriate markup.\n\n```md\n\n```\n\nor\n\n```html\n![\"This](\"myimage.jpg\")
\n```\n\nDuring the build process, `magicbook` will transfer all files located in `images` to the `asset` folder of each build and replace the image src attribute appropriately.\n\n### Source files\n\nYou can change where `magicbook` looks for images by supplying an array of globs, just like the general `files` array. The default pattern is `images/**/*.*`.\n\n```json\n{\n \"images\": {\n \"files\": \"custom/images/folder/**/*.jpg\"\n }\n}\n```\n\n### Destination folder\n\nIt is also possible to control where the images are stored in the build. You can specify a custom destination folder by using the `destination` property. It defaults to `assets`.\n\n```json\n{\n \"images\": {\n \"destination\": \"custom/assets/folder\"\n }\n}\n```\n\n### Digest\n\nThe `digest` option will add a md5 checksum of the image content to the filename, to allow you to set long caching headers for a production website.\n\n```json\n{\n \"images\": {\n \"digest\": true\n }\n}\n```\n\n### Colorspace\n\nYou can specify the output images' `colorspace`. All images defined in the source files will be transformed utilizing [sharp](https://sharp.pixelplumbing.com/api-colour#tocolourspace).\n\n```json\n{\n \"images\": {\n \"colorspace\": \"b-w\"\n }\n}\n```\n\n## Stylesheets\n\nYou can style all your builds using CSS or SCSS. The `stylesheets` configuration allows you to specify an array of `.css` or `.scss` files to include in the build. The following example shows a configuration file specifying two stylesheets to include in all builds.\n\n```json\n{\n \"stylesheets\": {\n \"files\": [\"css/first.css\", \"css/second.scss\"]\n }\n}\n```\n\nYou can insert the compiled CSS in the layout using the `{{ stylesheets }}` liquid variable tag. This will insert each file as a separate `` element.\n\n```html\n\n \n {{ stylesheets }}\n \n \n {{ content }}\n \n\n```\n\nBy using different files for each format, you can have a book that looks very different across formats. To share styles between the formats, you can use SCSS `@import`.\n\n### Destination\n\nIt is also possible to control where these stylesheets are stored in the build. You can specify a custom destination folder by using the `destination` property. It defaults to `assets`.\n\n```json\n{\n \"stylesheets\": {\n \"destination\": \"customfolder\"\n }\n}\n```\n\n### Compress\n\nThe `compress` property will remove whitespace from the CSS file, resulting in much smaller file sizes.\n\n```json\n{\n \"stylesheets\": {\n \"compress\": true\n }\n}\n```\n\n### Bundle\n\nThe `bundle` option will combine all the files in the `stylesheets` array into a single CSS file in the output. This, combined with the `compress` option, is recommended to improve the loading speed of a production website. You can set it to `true` or the desired name of the bundle.\n\n```json\n{\n \"stylesheets\": {\n \"bundle\": \"mybundle.css\"\n }\n}\n```\n\n### Digest\n\nThe `digest` option will add the md5 checksum of the file content to the filename, to allow you to set long caching headers for a production website.\n\n```json\n{\n \"stylesheets\": {\n \"digest\": true\n }\n}\n```\n\n## JavaScripts\n\nThe `javascripts` configuration allows you to specify an array of `.js` files to include in the build. The following example shows a configuration file specifying two JavaScript files to include in all builds.\n\n```json\n{\n \"javascripts\": {\n \"files\": [\"css/first.js\", \"css/second.js\"]\n }\n}\n```\n\nYou can insert links to the JavaScript files in the layout using the `{{ javascripts }}` liquid variable tag. This will insert each file as a separate `