Skip to content

Wiki Conventions / ウィキの規約

How the Sagishima wiki is organized and how to add to it. This folder (SagiWiki/) is a knowledge base about the island, structured so it can later become a wiki-like website. Each page is one topic.

The category map

Folder Holds 日本語
00_Overview.md Island at a glance; the front page 概観
Place/ The physical island: geography, hydrology, districts, ports, maps 場所
History/ The island in human time, from premodern to the present 歴史
People/ Demographics, named residents, families 人
Built_Environment/ Kakumeisha, the houses, the gymnasium, the akiya 建物
Culture_and_Ritual/ Festival year, Ke/Hare, Radio Taiso, the 88+α, ceremonies 文化と儀礼
Land_and_Food/ Island agriculture: heritage and current crops, the asparagus revitalization (RDS's artichoke project + the studio kitchen moved to the Foundation wiki) 食べもの
(moved) RDS's Sagishima Data Project is research by the School, so it now lives on the Foundation wiki: /foundation/Research/ 調査
Relationships/ The island's regional neighbors (Onomichi, nearby islands); RDS's institutional partnerships (Mihara City, Hiroshima University, sponsors) moved to the Foundation wiki 近隣
References_and_Media/ Outside views: the Naked Island, cartographers, the view from elsewhere (alumni voices moved to the Foundation wiki) 外からの視線
_meta/ This file, the open-questions tracker メタ
_sources/ The primary-source library and bibliography 出典

Folders prefixed with _ are infrastructure, not articles. They sort to the top.

The full long-form narrative lives in Sagishima_Compendium.md (+ .docx). The wiki pages are the granular, living layer; the Compendium is the curated long read. Note: the Compendium is a Claude-generated secondary synthesis. Use it for orientation and link to it as "related," but never cite it as a source (see Citations below).

How to add a page

  1. Pick the right category folder. If a topic spans two (the 88+α spans Culture and Research), give it one canonical home and link to it from the other; do not duplicate the content.
  2. Copy the stub template below into a new Title_With_Underscores.md.
  3. Fill Overview and What we know. Cite as you go (see Citations).
  4. Move anything you could not answer into _meta/open-questions.md.
  5. When a stub becomes real content, change status: stub to status: draft or status: stable.

Stub template

---
title: "English Title"
title_ja: "日本語タイトル"
category: "Category"
status: stub        # stub | draft | stable
updated: YYYY-MM-DD
sources: []         # bibliography keys this page draws on
---

# English Title / 日本語タイトル

## Overview / 概要
## What we know / わかっていること
## Open questions / 未解決の問い
## Sources / 出典

Naming and slugs

  • Filenames use English words separated by underscores (Sunoue_Gymnasium.md). English slugs keep URLs portable when this becomes a site.
  • The Japanese title lives inside the page, never in the filename.

Images / 画像

  • Sagishima imagery lives canonically in _assets/, organized by the same subfolder taxonomy as the old image library (buildings/ landscape/ townships/ plates/ portraits/ partnerships/ studio_documentary/ community/ data_charts/ marks/). This folder is the single source of truth for the wiki's images.
  • Reference images by relative path to _assets/ (for example, a page in Built_Environment/Houses/ embeds ../../_assets/buildings/sumifuku_dormitory.jpg). Do not point back into the top-level RDS_Image_Library/; that pool holds only non-Sagishima (RDS, Found Object, brand) imagery now.
  • When you add a new Sagishima image, drop it in the matching _assets/ subfolder. Keep alt text bilingual (English / 日本語).

Building the site / サイトのビルド

The wiki renders with MkDocs + Material. Config is ../mkdocs.yml at the repo root (docs_dir: SagiWiki). Run mkdocs serve from the repo root for a live preview, or mkdocs build --strict to produce site/ and catch broken links. Navigation is generated automatically from the folder tree (the mkdocs-awesome-pages-plugin); a folder's order and bilingual title are set in its .pages file, so new pages appear without editing yaml.

Bilingual rule (non-negotiable)

English and Japanese are fully coequal. Every page heading carries both at equal weight (English / 日本語), same prominence, neither presented as a subtitle or translation of the other. When this graduates to a website, the intended end state is parallel /en and /ja trees; until then, coequal-in-page is the standing form.

This applies to body content, not just headings. As of 2026-06-02 every article body is bilingual. Follow this form when adding or editing pages:

  • Prose paragraph: the English paragraph, one blank line, then the Japanese paragraph as its own block.
  • List item: the English item, then the Japanese on the next line indented two spaces so it stays part of the same item.
  • Table cell: make each translatable cell coequal: English / 日本語 for short labels, or English then a <br> then Japanese for sentence-length cells. Never translate years, figures, source codes, or URLs.
  • Blockquote: English quoted line(s), a blank > line, then the Japanese as quoted lines.
  • Leave verbatim: frontmatter, link targets/URLs, filenames, code spans, inline source codes (n241cbe045f22), bibliography keys, and figures. Headings and image alt-text are already bilingual.

The Japanese in the article bodies was Claude-generated and has not had a native review. Treat it as draft until a native reader confirms it; flag uncertain proper-noun readings in _meta/open-questions.md.

Citations

Per standing project order, cite sources for substantive claims: - Cite PRIMARY sources only. A primary source is the original record (a note.com post, a thered.school page, a primary RDS document, the film, the journal article). Never cite a Claude-generated synthesis as a source: not the Sagishima Compendium, not audit-folder READMEs, not the audit .md mirrors of website content. Trace each fact back to where it actually came from and cite that. If you cannot find the primary, write "not yet traced to a primary; flagged for verification" rather than citing a synthesis or inventing one. - Inline, at the point of the claim (for example: per the Old Home page or per note.com n241cbe045f22). - End of page, under ## Sources, resolving to a key in _sources/bibliography.md.

When two sources disagree (the island area, the population figure), quote both and flag the discrepancy rather than silently picking one. See the open questions for the live discrepancies.

A few content rules carried from the project

  • Artichokes are an active RDS introduction project, not island heritage. The artichoke project is RDS's work, so it lives on the Foundation wiki (/foundation/Practice/Artichoke_Project/); keep it clearly separate from island Agriculture Today, and never present artichokes as Sagishima tradition.
  • No em-dashes in outward-facing prose. This is internal/AI-facing for now, but do not introduce them in new writing.
  • .docx is the human source of truth; .md mirrors it. For any paired file, back-port .docx edits into the .md rather than overwriting the author's .docx.