Wiki Maintenance

Wiki maintenance

The wiki is a separate Git repository. Its builder reads existing documentation from rebuild/main and gh-pages and writes only this wiki checkout. It does not push, edit the source checkouts, run docs-sync.yml, change translations, or deploy the website.

Where to make a correction

• Task guides: edit the corresponding gh-pages HTML page through the project's normal review process.
• Detailed references: edit the corresponding Markdown document on rebuild/main.
• Generated external-tools sections: edit the templates in .github/workflows/docs-sync.yml; direct edits to their generated source output will be overwritten by the existing workflow.
• Wiki homepage, navigation, source mappings and conversion: edit _tools/build.py in this wiki repository.

Every imported page has an exact source-commit link at the bottom. Correct its source, then regenerate the wiki. Direct edits to imported wiki pages are overwritten on the next rebuild. Integration plans and the internal documentation gap checklist are not published as user guides; links to those files remain links to the source repository.

Rebuild

Use Python 3.10 or newer, Git, and three separate sibling directories. The source and site checkouts must be clean. Existing working copies are also accepted by the builder.

git clone --depth 1 --single-branch --branch rebuild/main https://github.com/NathanNeurotic/Open-PS2-Loader.git source
git clone --depth 1 --single-branch --branch gh-pages https://github.com/NathanNeurotic/Open-PS2-Loader.git site
git clone https://github.com/NathanNeurotic/Open-PS2-Loader.wiki.git wiki
cd wiki
python -m venv .venv

Activate the environment with .venv\Scripts\activate on Windows or source .venv/bin/activate on Linux/macOS, then run:

python -m pip install -r _tools/requirements.txt
python _tools/build.py --source ../source --site ../site
git diff --check
git diff --stat
git diff

The builder fails on missing source pages, dirty source checkouts, duplicate page names, unresolved wiki links or section anchors, and unexpected output files. It checks that conversion preserves text, tables and code examples. Run it again with the same inputs: generated file hashes must be identical. Source checkouts are checked again at the end to ensure their tracked and untracked state did not change.

Review the content before committing and pushing the wiki repository. Use a normal push that preserves history; concurrent edits must be reconciled. There is no automatic publication job or additional credential configured by this setup.

Coverage and source revisions

• Source: 3ce281b0793c
• Website: fc2e13154e51
• All website HTML pages are included, with explicit source-to-wiki mappings.
• The complete README, release reference and selected user/developer Markdown guides are included.
• _tools/manifest.json records source revisions, per-page origins, output hashes and validation counts.

Website search, styling and JavaScript controls belong to the website. In the wiki, tables are static and expandable explanations are shown in full. Content, code examples, and section destinations are preserved. Site and source guides may overlap; paired pages link to one another and retain their source provenance rather than silently combining potentially different instructions.