47 nodes / one connected world

The connected workshop

Every expression has an identity. Follow the relationships between the ideas, the work, and Hugo Web.

This is the graph beneath the site—not a second collection of copies. Each expression lives in its publishing folder and contributes its node to this index.

Entities

entity nodes

Concepts

concept nodes
design-pattern

Adapter pattern

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

adapter-pattern
process

Build

The phase of turning an approved model into working, inspectable expressions.

build
principle

Builder sovereignty

Practical ownership of knowledge, tools, and decisions, including the ability to inspect and leave a system.

builder-sovereignty
practice

Code Generation Contract

The project-specific guidance for turning approved Hugo Web intent into working, inspectable site code while preserving semantic identity, human authority, simplicity, and publication safety.

code-generation-contract
process

Design

The phase of choosing intent, outcomes, and constraints before committing to implementation.

design
practice

Developer’s Notebook

A place for technical investigation, implementation mechanisms, reproducible questions, and architectural judgment.

developers-notebook
modeling-pattern

Domain-Driven Design

An approach to software design that develops a shared domain language and models within explicit boundaries.

domain-driven-design
practice

Evidence and revision

Use observed results to correct the model while distinguishing measurement, interpretation, and uncertainty.

evidence-and-revision
modeling-pattern

Expression

An outward artifact of structured meaning; on this site every published expression also has its own canonical node.

expression
practice

Frontier models

A time-sensitive category for highly capable AI models, evaluated by task, evidence, operational constraints, and risk rather than a permanent ranking.

frontier-models
design-pattern

Gang of Four design patterns

A catalog of recurring object-oriented design solutions described by Gamma, Helm, Johnson, and Vlissides.

gang-of-four-patterns
principle

Human agency

The builder’s retained ability to set intent, judge evidence, choose actions, and accept responsibility.

human-agency
modeling-pattern

Knowledge graph

A model of identified things connected by explicit relationships under a shared vocabulary.

knowledge-graph
process

Model

The phase of making important distinctions, intrinsic facts, and relationships explicit.

model
modeling-pattern

Ontology

The small controlled vocabulary that governs node types, kinds, relationship predicates, and explicit contracts.

ontology
architecture-style

Ports and adapters

Separate application policy from external mechanisms through explicit interaction boundaries.

ports-and-adapters
practice

Retrieval-augmented generation

Supply retrieved source material as context for generation, then evaluate the result against that evidence.

retrieval-augmented-generation
modeling-pattern

Semantic node

A stable, structured representation of one meaningful thing in the modeled world.

semantic-node
process

Ship

The phase of placing approved expressions into reality and learning from their use.

ship
principle

Simplest-capable architecture

Prefer the least complexity that genuinely satisfies the whole system’s requirements.

simplest-capable-architecture
principle

Single Responsibility Principle

A module should have one coherent reason to change, understood in relation to the actors or policies it serves.

single-responsibility-principle
principle

SOLID

Five object-oriented design principles concerned with responsibility, extensibility, substitutability, interface focus, and dependency direction.

solid
architecture-style

Static-first publishing

Precompute publishable information when freshness and interaction requirements permit, adding runtime work only where it creates value.

static-first
design-pattern

Strategy pattern

Encapsulate interchangeable algorithms behind a shared behavioral contract when variation is a real requirement.

strategy-pattern

Expressions

expression nodes
note

Build an ID index, not a path dependency

A technical explanation of two-pass graph indexing and publication-scoped relationship resolution.

build-an-id-index
reference

Choose a publishing boundary, not a platform identity

An architectural map of optional static publishing services and their responsibilities.

choose-a-publishing-boundary
guide

Close the learning loop

A method for using observed outcomes to revise a model after publication.

close-the-learning-loop
guide

Connect things without over-modeling them

A guide to explicit outbound relationships and compact ontology design.

connect-without-over-modeling
reference

The developer’s field references

A categorized directory of external sources for Hugo, delivery systems, software design, and AI-assisted development.

developer-resource-directory
note

Follow the render path

A technical note on inspecting Hugo page data, template selection, and serialization boundaries.

follow-the-render-path
guide

Give AI a bounded task

A review-first workflow for AI-assisted building with clear authority and limited scope.

give-ai-a-bounded-task
tutorial

Model one meaningful thing

An introduction to creating a minimal semantic node without unnecessary fields.

model-one-meaningful-thing
guide

Old principles. New leverage.

A practical application of established software-design principles to AI-assisted code generation.

old-principles-new-leverage
tutorial

Publish one source two ways

A Hugo pattern for generating HTML and JSON from the same canonical node.

publish-one-source-two-ways
reference

Ship a release you can reverse

A release procedure covering validation, artifact review, deployment checks, and rollback.

release-you-can-reverse
guide

Choose the simplest capable system

An architectural decision method that weighs complexity against concrete requirements.

simplest-capable-system
guide

Start with an outcome, not a stack

A practical method for stating intent before selecting implementation tools.

start-with-an-outcome