Shingo Content Sections

Shingo divides its published material into three clearly named directories, and the directory name becomes the first segment of the corresponding URL. No internal synchronisation paths or database identifiers leak into the routing layer; the structure is a direct reflection of how the filesystem is laid out.

The record directory serves long-form writing such as notes and articles. Everything under it appears at /record/, and this area is meant for sustained, essay-like pieces rather than quick experiments or constantly updating references.

The toy directory groups together small projects and playful experiments. It maps to /toy/ and contains self-contained works where the focus is on trying out ideas rather than polished documentation.

The wiki directory holds a curated knowledge base. It is rendered at /wiki/, but its content is not authored inside Shingo. Instead, the entire wiki section is maintained and synchronised by an external process known as nemo-knows, keeping cross-document linking and content preparation separate from the static site generator.

This three-part organisation reflects the site’s deliberately thin scope. Shingo concerns itself only with structure, navigation, styling, and static rendering. Preparation of Markdown text, linking logic, and ongoing maintenance of the knowledge graph all happen upstream, before the content ever reaches the presentation layer.