Category: Advanced

This chapter covers optional capabilities. Each one is enabled explicitly — the theme supplies the implementation but does not set site policy on your behalf. In this chapter Keyboard navigation: the complete single-key map, focus rules, and per-page …

OINK does not contact analytics, form, comment, or advertising services by default. These integrations are site decisions: enable them explicitly, document the data boundary, and provide any consent or policy required by the site’s users and …

OINK supports giscus through a Hextra-compatible comments configuration under params.comments. giscus gives each content page a comment thread backed by GitHub Discussions and lets readers comment through GitHub OAuth. How giscus works When a page …

Early evaluation Features described in this page are experimental, and are useful for early adoption and evaluation. Output details and validation coverage may change in future releases. To track the phased evolution of the agent-support feature, see …

Individual documentation pages print well from most browsers as the layouts have been styled to omit navigational chrome from the printed output. Printing one page is therefore the browser’s own Cmd/Ctrl+P; OINK offers no page-level print action of …

OINK defaults to and recommends local search: Hugo generates a separate index per language, and Lunr plus the CJK fallback are served from same-origin assets. A site builds and searches without a public crawler, an external account, a CDN, or a …

OINK ships single-key keyboard navigation on docs, blog, and Swagger pages. It is on by default, every binding yields to anything you are typing into, and a site or a single page can switch it off. The design treats the current page as the implicit …