GIVE INFORMATION A PLACE
Clarity, from page to page.
Explore navigation, data states, and disclosures that work through native HTML and Go responses.
A comfortable place to read.
The width follows the font's character metrics and shrinks to fit small screens. It is an upper bound, not an exact number of letters per line.
Build the smallest useful page.
A good application makes room for more than controls. Help articles, project briefs and release notes deserve the same care as the dashboard around them.
Start with clear structure and a useful first sentence. Let headings describe the next section, keep related ideas together, and make each link explain where it goes.
Give content a natural rhythm.
This page uses native HTML. The server supplies its words and structure; the stylesheet handles line length, heading space and the quieter details.
- Choose the heading level that fits the document.
- Group related information into a list when it helps scanning.
- Keep each point specific.
- Use a nested list only for a real relationship.
- Offer a useful next action, such as trying the form lab.
A readable page gives the reader time to understand one idea before introducing the next.
Small details, sensible defaults.
- Measure
- The maximum reading width, expressed in font-relative
chunits. - Rhythm
- The space and line height that separate ideas without fragmenting them.
- Semantics
- The native headings, lists, labels and links that describe the content.
mux.Handle("/gothui/static/", gothui.AssetHandler())
// Your application owns routing and page content.Bring the rest of the interface along.
Embedded controls and feedback can keep their own spacing. Their appearance still follows the same theme.
Try another view
Switch between narrow and wide measures, choose a serif font in Appearance, then compare light and dark themes.
Long content can remain readable inside a larger workspace. Explore layout composition when you are ready to put the pieces together.