Keep the center independent

Often called hexagonal architecture, ports and adapters keeps core behavior from being defined by a database, web framework, or provider API. Ports describe useful interactions; adapters connect particular technologies to them.

Use only the boundary you need

For Hugo Web, portable node meaning should survive a change of publishing engine. That does not require six layers of code. A small, documented storage mapping may be enough until the system has multiple implementations.

AI can help identify accidental framework dependencies. It should not generate an elaborate hexagonal scaffold when ordinary files and one adapter suffice.

Original source

Alistair Cockburn: Hexagonal architecture