The generated site (note: Site) carries the organisation's identity (3 passages, no note) and nothing of the tool's. The name, logo, favicon, font families (3 passages, no note), corner radius, light and dark (3 passages, no note) palettes (24 passages, no note), footer (19 passages, no note) and additional stylesheet (26 passages, no note) all come from theme.yaml, validated by the theme (note: Theme) schema (31 passages, no note); a faulty key (3 passages, no note) is reported by its path like a configuration (note: Configuration) error (29 passages, no note). The footer credits (4 passages, no note) the tool only when the project (note: Project) asks for it (footer.credit: true, a plain link (note: Link) to the repository (note: Knowledge repository)); by default nothing a reader (note: Reader) sees names it. Font (17 passages, no note) files are shipped by the project itself and bound (4 passages, no note) with @font-face rules (note: Rule): the site emits no request (31 passages, no note) to any other host (8 passages, no note). Light (18 passages, no note) and dark modes (note: Colour scheme) follow the system preference (8 passages, no note), the reader can force one with the mode switch and the choice is remembered (8 passages, no note); without JavaScript the theme's default applies. The accent colour (3 passages, no note) never carries information (10 passages, no note) on its own: wherever the default theme uses it, an underline (4 passages, no note), an outline (17 passages, no note), a weight or a text carries the same meaning.
The project's own wiki asks for the credit, because it is the tool documenting itself.