How kotaoue/gamemo works
Project type & purpose (from file tree + top README)
This repo is primarily a personal knowledge base + analysis notebook (“gamemo”) organized by game/topic (Splatoon, Pokémon, etc.) using Markdown files as the main artifact.
In addition, it contains a couple of small Go-based tooling subprojects that automate collecting/transformation of data into Markdown:
• splatoon3/ikamemo/ — a Go tool (with Makefile) that likely generates memo/summary Markdown from Splatoon-related data (notably the splatoon3/sheets/*.json files and splatoon3/results/template.md).
• hypnosismic/hypwiki/ — a Go tool with files like scraper.go, writer.go that strongly implies scraping + writing wiki-style content.
There is also automation via GitHub Actions:
• .github/workflows/fetch-splatoon3-sheets.yml — a workflow that likely fetches or updates Splatoon 3 “sheets” data into splatoon3/sheets/.
Repository as the canonical store
• Markdown notes (manual + generated)
• JSON datasets (“sheets”)
• Generated outputs (splatoon3/results/, possibly more)
Automation paths that update the repo
• GitHub Actions (scheduled or manual)
• Local developer runs (Makefile / go run)
External sources
• Whatever the workflow fetches (likely Google Sheets or some hosted JSON)
• Whatever hypwiki scrapes (a website/wiki)
“Content” (human-facing artifacts)
From the tree, these are the primary deliverables:
• Top-level Markdown collections:
splatoon3/*.md, splatoon2/gear.md, pokemon/*.md, ocg/*.md, mhr/mhr.md, ssb/spirits.md, tsumtsum/tsumtsum.md, etc.
• Splatoon 3 outputs:
splatoon3/results/template.md (template), splatoon3/results/ (likely generated result docs)
• Images:
splatoon3/images/
Data inputs / datasets
• splatoon3/sheets/*.json (multiple datasets, plus download_sheets.sh)
• Anything fetched by .github/workflows/fetch-splatoon3-sheets.yml
Tooling subprojects (Go)
• splatoon3/ikamemo/
• main.go (entrypoint/CLI)
• generator.go (core transformation logic)
• writer.go (output formatting/writing)
• go.mod, go.sum (dependencies)
• Makefile (local execution)
• hypnosismic/hypwiki/
• main.go (entrypoint/CLI)
• scraper.go (external fetch/parse)
• writer.go (writes markdown/pages)
• go.mod, go.sum
Automation / orchestration
• GitHub Actions workflow: .github/workflows/fetch-splatoon3-sheets.yml
• Shell helper: splatoon3/sheets/download_sheets.sh
• (Optional) Dev environment docs: environment/desktop.md
External Sheets Source
↓ (HTTP fetch/export)
GitHub Actions: fetch-splatoon3-sheets.yml and/or local script download_sheets.sh
↓ (writes/updates)
Repo folder: splatoon3/sheets/*.json
↓ (read)
Go CLI: splatoon3/ikamemo/main.go
• generator.go transforms JSON → internal model → sections/metrics
• writer.go renders Markdown
↓ (write)
Repo outputs: splatoon3/results/ and/or splatoon3/*.md
• Local dev run (Makefile)
External Hypnosismic site/wiki
↓ (HTTP scrape)
Go CLI: hypnosismic/hypwiki/main.go
• scraper.go fetch/parse
• writer.go outputs Markdown
↓ (write)
Manual content authoring
• “Human editor” → modifies Markdown notes directly across topic folders
• Human also runs tools locally
Architectural patterns / design principles to highlight (from structure)
Even without reading code, the file naming implies clear separations:
• CLI entrypoint (main.go) vs domain logic (generator.go / scraper.go) vs IO/output (writer.go)
• Data-driven generation: JSON datasets are treated as inputs; Markdown is output.
• Repo as single source of truth: both raw inputs (JSON) and final artifacts (Markdown) live together.
• Automation-as-code: GitHub Actions codifies ingestion steps.
• In .github/workflows/fetch-splatoon3-sheets.yml:
• schedule vs manual trigger
• exact source endpoint(s)
• whether it commits back to repo
• In splatoon3/ikamemo/README.md and main.go:
• exact inputs (which JSON files)
• exact outputs (which .md files/paths)
• whether it uses splatoon3/results/template.md
• In hypnosismic/hypwiki/README.md and scraper.go:
• scraped site(s) and output directory structure
• External: “Sheets Source” → (GitHub Actions / download_sheets.sh) → splatoon3/sheets/*.json
• splatoon3/sheets/*.json → splatoon3/ikamemo (Go CLI) → splatoon3/results/* + splatoon3/*.md
• External: “Hypnosismic Wiki Site” → hypnosismic/hypwiki (Go CLI scraper) → hypnosismic/*.md
• Actor: “Author” ↔ Repo (manual edits + runs tools locally)
This captures the essential architecture: ingest → transform → publish, with the repo as the hub.