Concepts & principles / design-pattern

Adapter pattern

Translate one interface into another interface a client expects without changing the underlying meaning.

Canonical graph nodeadapter-pattern

At the Hugo boundary

The portable semantic node and Hugo page parameters are different interfaces. The storage adapter maps root node: into .Params.node for templates. That mapping should not redefine the identity of the modeled thing.

AI-assisted application

Keep provider-specific response shapes behind a small adapter when the domain actually needs a stable interface. Ask AI to generate contract tests, including failure cases. Do not conceal meaningful provider differences behind an overly broad promise of interchangeability.

A conceptual resemblance to the pattern does not mean this template system is an implementation of the original object-oriented class structure.

Part of a connected world

Follow the meaning.

View the graph →

Outgoing connections

extendsGang of Four design patterns
applies-toHugo

Connected from

Node data identity, meaning & relationships

The complete semantic record, rendered from root node: front matter.

semantic_node:
  description: Translate one interface into another interface a client expects without changing the underlying meaning.
  id: adapter-pattern
  kind: design-pattern
  name: Adapter pattern
  relationships:
  - predicate: extends
    target: gang-of-four-patterns
  - predicate: applies-to
    target: hugo
  type: concept

Publishing metadata

description: Translate one interface into another interface a client expects without changing the underlying meaning.
draft: false
title: Adapter pattern
url: /graph/concepts/adapter-pattern/