An MkDocs site can be treated as a readable interface to a semiotic structure. It is interactive in the sense that it lets a reader traverse, query, and reconfigure their view of content through navigation, search, and metadata.
Site elements as semiotic features
- Pages are things or fragments surfaced as readable nodes.
- Links are interaction terms between pages.
- Navigation is a controlled interaction surface that shapes possible paths.
- Frontmatter and tags act as semantic seeds for the reader and for plugins.
Reading as interaction
Readers do not change the data, but they generate semantic updates by moving through the site. The site is an interface for local interaction with a semiotic universe rather than a static archive.
Implications for design
- Curate navigation to guide meaningful traversals.
- Expose metadata that supports inquiry (tags, dependencies, authors).
- Use plugins to surface footprints, indexes, or vault views when needed.