There are two ways to make Fieldnotes yours. Settings in hugo.toml cover the look: a preset and a colour scheme, then fonts and background on top. Hooks are files of your own that the theme picks up, for everything the settings don’t cover. The playground on the home page tries the settings out live.

Settings

# How it's drawn: fieldnotes, minimal, editorial, cinematic,
# brutalist or terminal; its colours, light and dark
# (empty: the preset's own)
[params.style]
  preset = "terminal"
  scheme = "catppuccin"

# light, dark or auto (the visitor's system); without the toggle,
# a light-only or dark-only site
[params.mode]
  default = "auto"
  toggle = true

# Any Google Fonts family, instead of the preset's
[params.fonts]
  body = "Lora"

# grid, dots, none, or an image in assets/, like an SVG tile
[params.background]
  light = "grid"
  dark = "none"

The preset is how the site is drawn: fonts, background, corners, cards and decoration like the fieldnotes preset’s tape. The scheme is its colours, with a light and a dark version, any scheme with any preset. A page can pick its own look with the same names in its front matter (style:), as the pages in Presets do.

Presets and schemes are plugins: a CSS file and a small data file each, which your site can add or replace. The theme generator explains them and downloads a preset as a copy to change.

Hooks

File in your siteWhat it does
assets/css/custom.cssYour CSS, loaded last: its rules win over the theme’s. Every size and colour is a custom property, like --color-accent or --width-content.
layouts/_partials/hooks/head-end.htmlHTML at the end of every page’s <head>: analytics, another font, a script that has to run before the page is drawn.
layouts/_partials/hooks/body-end.htmlHTML at the end of every page’s <body>: a script, a notice.
a partial named by displayCardThe card on the home page, with any HTML you like.

The theme has empty versions of the first three. Hugo takes your site’s file over the theme’s when both exist, so creating the file is all it takes.

This example site uses all four for the playground: the display card holds the form, head-end.html loads every preset and scheme and applies the saved choices before the page is drawn, body-end.html loads the form’s script, and custom.css styles the form.