AI Summary
Purpose:
- Maintain the private wiki's Korean navigation and reading interface without changing the source knowledge.
Key points:
scripts/build-wiki.mjsbuildshuman/index.html,human/wiki/, the existing report-hub alias and redirects.- The September 11 redesign uses the portfolio's white/navy/cobalt palette with a persistent library sidebar, search-first home, document rows, category/tag directories and a document table of contents.
- UI sources are
scripts/wiki/templates.mjs,wiki.css,wiki.js, andgraph.js. Generated HTML and CSS must not be the only place an interface edit is made. - CSS, scripts and catalog URLs carry a content-derived revision so a rebuild does not reuse stale UI assets.
- Existing document URLs remain unchanged. English source documents retain their original language; the navigation and controls are Korean.
- This host cannot read some existing Google Drive HTML placeholders.
--reuse-html-indexexplicitly retains the current HTML catalog while rebuilding Markdown pages and the interface. It does not refresh HTML metadata. - Browser verification uses the existing toolchain under
scripts/portfolio/node_modules/, without adding runtime dependencies.
Relevant when:
- Redesigning the wiki, editing its navigation, rebuilding pages, or diagnosing local previews.
Do not read full document unless:
- Running the build, changing a component, or investigating route/interaction behavior.
Linked documents:
../workspace/wiki-redesign-2026-09-11/index.mdllm-wiki-portfolio.md../worklog/2026/2026-W37.md
Open Questions
- Existing generated study HTML must be hydrated before a full content reindex can succeed on this Drive mount. The design task does not repair or regenerate the study site.
- Publication was not requested for this redesign. The changes are local.
Details
Build and preview
Run from the repository root:
node scripts/build-wiki.mjs
python3 -m http.server 8766 --bind 127.0.0.1 --directory humanWhen published HTML cannot be read but the existing human/wiki/assets/wiki-data.js is readable:
node scripts/build-wiki.mjs --reuse-html-indexThat explicit mode retains every existing HTML document record, including its URL and prior excerpt. Markdown is rebuilt from current sources. It must not be described as a fresh HTML content audit. The build retains unrelated existing output files instead of recursively deleting the wiki directory.
Open http://127.0.0.1:8766/. The static files also support direct file:// browsing and relative path prefixes. Assets include a copied local Pretendard font and its license from the portfolio; platform Korean fonts cover characters outside the existing subset.
Interface contracts
- The home search submits to
wiki/index.html?q=.... - Library state uses
q,category,tag, andsort=recentquery parameters. Search matches all whitespace-separated terms against title, path and tags. - Enhanced browsing displays 40 documents at a time, a live result count, explicit empty state and reset controls. All documents remain in static HTML for browsing without JavaScript.
- Existing
categories.html#category-*andtags.html#tag-*destinations remain available. Each directory section previews documents and links to the full filtered result set. - The document shell has correct relative navigation at its nested depth and an anchor-based table of contents. Source-body Markdown links are rewritten when their target is in the catalog.
- The graph is a bounded, deterministic neighborhood view. At most 14 nodes are plotted; the adjacent list exposes all matches and all connected documents. Category, tag and document-link modes use the existing graph data. It no longer runs an unbounded all-pairs simulation every frame.
- Desktop has a fixed sidebar; mobile has an inline collapsible menu.
/focuses search and Escape closes the mobile menu. Native links remain usable without JavaScript.
Validation
node scripts/wiki/qa.mjsWIKI_URL overrides the preview base, WIKI_QA_OUT the evidence directory, and WIKI_CHROMIUM an already installed Chromium executable when it differs from the toolchain's expected version. The QA covers six page types at 375/768/1440 pixels plus search, categories, tags, sorting, pagination, graph interaction, document navigation and no-JavaScript browsing.
The palette and source-copy boundaries are shared with the portfolio, but the wiki UI has its own components. Do not rebuild or restyle the portfolio as a side effect of a wiki change.