Documentation on Example Agency

Getting started

Mon, 01 Jan 0001 00:00:00 +0000

Section heading (h2)

These headings introduce sections and subsections within your body copy. Be succinct, descriptive, and precise.

Body copy carries the usual inline marks: bold for emphasis you would say out loud, italic for terms being introduced, inline code for anything a reader will type, ~~strikethrough~~ for superseded guidance, and links to the source. Keep links descriptive — “read the USWDS documentation” tells a screen reader user where they are going; “click here” does not.

Theming

Mon, 01 Jan 0001 00:00:00 +0000

Colors and type

Set values under [params.uswds.theme]. They are passed into Sass through the hugo:vars module, so no .scss file needs to change.

Going further

If you need a setting that is not exposed, create assets/uswds/_settings.scss in your own project. Hugo’s union filesystem gives your file precedence over the theme’s, so the theme itself stays untouched and upgrades cleanly.

Blog and news

Mon, 01 Jan 0001 00:00:00 +0000

Any section of dated pages behaves as a news section — there is no separate layout to opt into. The /news/ section on this site is an ordinary content directory; everything below comes from front matter and config.

Article front matter

---
title: "Section 508 audit results published"
date: 2026-06-30
author: "Digital Services"
tags: ["Accessibility", "Performance"]
description: "Findings from the annual audit, with remediation dates."
image: "img/og-news.png"
imageAlt: "Example Agency news"
---

date, author and tags render as a byline under the title. Each is optional and the byline disappears entirely when all three are absent, which is why documentation pages — like this one — do not show one.