diff --git a/content/en/docs/latest/advanced-settings/server-headers.md b/content/en/docs/latest/advanced-settings/server-headers.md index a1a8b56f..b77437da 100644 --- a/content/en/docs/latest/advanced-settings/server-headers.md +++ b/content/en/docs/latest/advanced-settings/server-headers.md @@ -1,7 +1,7 @@ --- title: Server headers description: Configure the server headers to refine the content security policy. -date: 2024-10-09 +date: 2024-10-10 layout: docs aliases: - "/docs/server/" @@ -101,7 +101,7 @@ First, we will define a new hugo build command `build:headers` as npm script. It {{< docs name="segments" file="config/_default/hugo.toml" >}} -As we cannot mount files into the `config` folder or base foloder, we need to copy the generated files ourselves. The following script uses the package `cpy-cli` to copy the generated files cross platform. +As we cannot mount files into the `config` folder or base folder, we need to copy the generated files ourselves. The following script uses the package `cpy-cli` to copy the generated files cross platform. ```json "scripts": { @@ -134,3 +134,5 @@ npm run build:headers (out) (out)Total in 281 ms {{< /command >}} + +Add the `/prebuild` folder to your `.gitignore` file to prevent polluting your source code repository. diff --git a/content/en/docs/latest/configuration/digital-asset-managers.md b/content/en/docs/latest/configuration/digital-asset-managers.md index 75bb0aa6..9f40cfe2 100644 --- a/content/en/docs/latest/configuration/digital-asset-managers.md +++ b/content/en/docs/latest/configuration/digital-asset-managers.md @@ -1,7 +1,7 @@ --- title: Digital Asset Managers description: Configure Digital Asset Managers to delegate the transformation of images -date: 2024-08-14 +date: 2024-10-10 layout: docs --- @@ -17,10 +17,18 @@ Hinode supports {{< link cloudinary>}}Cloudinary{{< /link >}}, {{< link imagekit ## Content Security Policy -Hinode has enabled access for Cloudinary, ImageKit.io, and Imgix by default. The following settings are set in `config/_default/server.toml`. Similar settings are defined in the `netlify.toml` file provided in the repository’s root when deploying to {{< link netlify >}}Netlify{{< /link >}}. Revise the Content Security Policy as needed. +Hinode has enabled access for Cloudinary, ImageKit.io, and Imgix by default. The following settings are set in the site's parameters (usually `hugo.toml`). See the {{< link "/docs/advanced-settings/server-headers" >}}Content Security Policy{{< /link >}} for more information. -```yaml -img-src: https://*.imgix.net https://*.imagekit.io https://*.cloudinary.com +```toml +[params.modules.hinode.csp] + frame-src = [ + "player.cloudinary.com", + ] + img-src = [ + "*.imgix.net", + "*.imagekit.io", + "*.cloudinary.com" + ] ``` ## Supported providers diff --git a/hugo_stats.json b/hugo_stats.json index 9fa798a9..a942c32a 100644 --- a/hugo_stats.json +++ b/hugo_stats.json @@ -1118,7 +1118,6 @@ "deploying-the-current-branch", "deploying-the-generated-server-headers", "deprecated-feature", - "disclaimer", "discover-how-hinode-can-help-you", "dismissible-alert", "display-headings",