Skip to content

Category: Design

  • Design proposals and PRDs

    In Proposals

    Design

    Non-normative material A proposal describes behaviour that may not exist. Current behaviour is defined by the contracts, accepted decisions, implementation, and owning checkers. Never use a proposal as a configuration reference. This section is the …

    Non-normative material A proposal describes behaviour that may not exist. Current behaviour is defined by the contracts, accepted decisions, implementation, and owning checkers. Never use a proposal as a configuration reference. This section is the …

  • Design research

    In Research

    Design

    Evidence, not a contract Research records what was measured, with which inputs and tool versions. Results may explain a decision, but they do not override the current contracts or implementation. Research belongs in the public Design tree when …

    Evidence, not a contract Research records what was measured, with which inputs and tool versions. Results may explain a decision, but they do not override the current contracts or implementation. Research belongs in the public Design tree when …

  • Design and development

    In Design

    Design

    OINK 0.6.0 contract This section publishes the maintainer contracts released with OINK 0.6.0, with Hugo Extended 0.160.1 as the compatibility floor. The canonical bilingual sources live in this repository under content/docs/design/. This section is …

    OINK 0.6.0 contract This section publishes the maintainer contracts released with OINK 0.6.0, with Hugo Extended 0.160.1 as the compatibility floor. The canonical bilingual sources live in this repository under content/docs/design/. This section is …

  • Design decisions

    In Decisions

    Design

    Accepted rationale A decision explains why OINK chose one compatible design over another. The five contracts above it remain the normative description of current behaviour; implementation and owning checkers remain the executable facts. OINK used to …

    Accepted rationale A decision explains why OINK chose one compatible design over another. The five contracts above it remain the normative description of current behaviour; implementation and owning checkers remain the executable facts. OINK used to …

  • OINK migration boundary

    In Design

    Design

    OINK 0.6.0 contract This is the migration contract released with OINK 0.6.0. This page is the canonical English source; its Chinese peer is maintained beside it in content/docs/design/. This is source and configuration guidance, not a release …

    OINK 0.6.0 contract This is the migration contract released with OINK 0.6.0. This page is the canonical English source; its Chinese peer is maintained beside it in content/docs/design/. This is source and configuration guidance, not a release …

  • Landing contract

    In Design

    Design

    OINK 0.6.0 contract This is the landing-page contract released with OINK 0.6.0. This page is the canonical English source; its Chinese peer is maintained beside it in content/docs/design/. Shared rules live in the architecture and component …

    OINK 0.6.0 contract This is the landing-page contract released with OINK 0.6.0. This page is the canonical English source; its Chinese peer is maintained beside it in content/docs/design/. Shared rules live in the architecture and component …

  • Shell and navigation contract

    In Design

    Design

    OINK 0.6.0 contract This is the shell and navigation contract released with OINK 0.6.0. This page is the canonical English source; its Chinese peer is maintained beside it in content/docs/design/. Authorities and navigation Concern Authority Global …

    OINK 0.6.0 contract This is the shell and navigation contract released with OINK 0.6.0. This page is the canonical English source; its Chinese peer is maintained beside it in content/docs/design/. Authorities and navigation Concern Authority Global …

  • Markdown-first authoring

    In Decisions

    Design

    Decision Prefer a native Markdown form when Goldmark can preserve the intended semantics. Keep a shortcode only when it provides a capability the native form cannot express. Add a content scenario by extending an existing shell and data model, not …

    Decision Prefer a native Markdown form when Goldmark can preserve the intended semantics. Keep a shortcode only when it provides a capability the native form cannot express. Add a content scenario by extending an existing shell and data model, not …

  • Bulk agent indexes

    In Proposals

    Design

    Draft PRD — partial premise already exists OINK already supports per-page Markdown, language-local llms.txt, HTML discovery links, and Copy Markdown. It does not currently publish llms-full.txt or a navigation JSON. Only those remaining outputs are …

    Draft PRD — partial premise already exists OINK already supports per-page Markdown, language-local llms.txt, HTML discovery links, and Copy Markdown. It does not currently publish llms-full.txt or a navigation JSON. Only those remaining outputs are …

  • Media convergence

    In Proposals

    Design

    Draft PRD — remaining work only OINK already has a shared content-image resolver, one Zoom marker, processed Markdown images, numbered figures, and safe Landing URL handling. This page proposes only the unresolved convergence; it must not be read as …

    Draft PRD — remaining work only OINK already has a shared content-image resolver, one Zoom marker, processed Markdown images, numbered figures, and safe Landing URL handling. This page proposes only the unresolved convergence; it must not be read as …

  • Consumer and migration evidence

    In Research

    Design

    Dated corpus snapshot These counts describe the repositories inspected in August 2026. They are evidence for design choices, not live product metrics or compatibility promises. Corpus The authoring survey scanned the content/ trees of eleven OINK …

    Dated corpus snapshot These counts describe the repositories inspected in August 2026. They are evidence for design choices, not live product metrics or compatibility promises. Corpus The authoring survey scanned the content/ trees of eleven OINK …

  • Configuration model

    In Decisions

    Design

    Decision OINK keeps Hugo’s native keys and useful Docsy-compatible keys in place, places theme presentation and behaviour under params.ui.*, and exposes a matching top-level front-matter key for a page override. It does not add a params.oink.* tree …

    Decision OINK keeps Hugo’s native keys and useful Docsy-compatible keys in place, places theme presentation and behaviour under params.ui.*, and exposes a matching top-level front-matter key for a page override. It does not add a params.oink.* tree …

  • Component contract

    In Design

    Design

    OINK 0.6.0 contract This is the component contract released with OINK 0.6.0. This page is the canonical English source; its Chinese peer is maintained beside it in content/docs/design/. Tutorials and exhaustive examples belong in the reader-facing …

    OINK 0.6.0 contract This is the component contract released with OINK 0.6.0. This page is the canonical English source; its Chinese peer is maintained beside it in content/docs/design/. Tutorials and exhaustive examples belong in the reader-facing …

  • Backlinks and knowledge graph

    In Proposals

    Design

    Draft PRD — not implemented OINK currently has no backlink block, local graph, global graph page, or graph output format. Names and configuration in this proposal are not public API until the proposal is accepted and the contracts change. Premise …

    Draft PRD — not implemented OINK currently has no backlink block, local graph, global graph page, or graph output format. Names and configuration in this proposal are not public API until the proposal is accepted and the contracts change. Premise …

  • Goldmark block-attribute evidence

    In Research

    Design

    Verified snapshot These probes produced byte-identical relevant output on Hugo Extended 0.160.1 and 0.164.0. They explain OINK’s native component forms; the current component contract remains authoritative. Method The probe used a minimal Hugo site …

    Verified snapshot These probes produced byte-identical relevant output on Hugo Extended 0.160.1 and 0.164.0. They explain OINK’s native component forms; the current component contract remains authoritative. Method The probe used a minimal Hugo site …

  • Warnings and safe fallbacks

    In Decisions

    Design

    Decision OINK does not call Hugo’s errorf. Invalid author or site input emits a warning and either uses a documented safe fallback or omits the invalid fragment. Release and deployment builds use --panicOnWarning, so the same warning remains a hard …

    Decision OINK does not call Hugo’s errorf. Invalid author or site input emits a warning and either uses a documented safe fallback or omits the invalid fragment. Release and deployment builds use --panicOnWarning, so the same warning remains a hard …

  • Architecture contract

    In Design

    Design

    OINK 0.6.0 contract This is the architecture contract released with OINK 0.6.0. This page is the canonical English source; its Chinese peer is maintained beside it in content/docs/design/. Repository and assembly The repository root is a Hugo Module …

    OINK 0.6.0 contract This is the architecture contract released with OINK 0.6.0. This page is the canonical English source; its Chinese peer is maintained beside it in content/docs/design/. Repository and assembly The repository root is a Hugo Module …