Category: Configuration

OINK’s documentation and blog layouts can show links to the current page’s source repository. They live in the page actions menu at the end of the breadcrumb row: View markdown opens the generated Markdown alternate when that output is enabled. View …

When a product has several supported releases, the documentation usually follows. OINK provides two things: a version switcher and an archived version banner. How each version is deployed is up to you — commonly one subdomain or subpath per version, …

OINK uses Hugo’s multilingual page model directly and introduces no site-specific domain convention or template assumption. This site treats English as the primary language and Simplified Chinese (zh) as the second. Configure languages hugo.yaml YAML …

Once the site runs, this chapter covers site-level structural configuration: how readers navigate, how many languages the content has, how many versions the documentation carries, and which repository the page actions point at. How to write …

OINK combines Hugo’s content tree and menu model with a documentation workspace: a site navbar on every layout, a collapsible and resizable section sidebar, a collapsible page outline in the right rail, and a site footer. The same structure works for …

OINK follows a “native first” configuration model. Site identity, languages, menus, outputs, taxonomies, markup, and modules stay in their Hugo-defined locations. Existing Docsy parameters remain where their semantics are useful. OINK adds only …