Secure by default

The default configuration of the theme gets an A+ score on Mozilla Observatory.¹

This is accomplished by programatically configuring Content Security Policy (CSP) headers based on a user-defined list of allowed domains in the config.toml file. Here’s the default and recommended setup (you could remove the last directive if you don’t want to embed YouTube videos):

[extra]
allowed_domains = [
    { directive = "font-src", domains = ["'self'", "data:"] },
    { directive = "img-src", domains = ["'self'", "https://*", "data:"] },
    { directive = "script-src", domains = ["'self'"] },
    { directive = "style-src", domains = ["'self'"] },
    { directive = "frame-src", domains = ["https://www.youtube-nocookie.com"] },
]

The allowed_domains list specifies the URLs that the website should be able to connect to, and each domain in the list is associated with a CSP directive such as frame-src, connect-src, or script-src. The templates/partials/header.html file dynamically generates the CSP header based on this list.

This feature allows you to easily customize the website’s security headers to allow for specific use cases, such as embedding YouTube videos, loading scripts or remote fonts (not recommended).

You can disable the CSP (allowing all connections) on a page, section, or globally by setting enable_csp = false in the front matter or config.toml file.

Note: enabling comments or analytics automatically allows scripts/frames/styles/connections as needed from the respective services.