Unhardcode

README.md

@@ -259,13 +259,23 @@ topdata:
         granted_on_level: -1
         on_menu: 0
   wiki:
+    source: topdata/wiki
     output_root: wiki
     pages_dir: pages
     state_file: state.json
+    page_index_file: page-index.json
     managed_namespaces: [classes, feat, itemtypes, races, skills, spells, meta]
     deploy_manifest: .wiki_deploy_manifest.json
     deploy_edit_summary: Auto-generated from native builder
+    namespaces_file: namespaces.yaml
+    data_file: data.yaml
+    page_paths_file: wiki.yaml
+    tables_file: tables.yaml
     visibility_file: visibility.yaml
+    templates_dir: templates
+    page_templates_dir: templates/pages
+    manual_sections_dir: manual-sections
+    manual_sections_file: manual-sections/default.yaml
     title_prefix_min_length: 3
     status_listing_scope: all
 
@@ -325,6 +335,15 @@ topdata:
       target_pattern: Guides/Alignment/{alignment}
 ```
 
+Generated wiki input and output paths are YAML-configurable. `source` points to
+the wiki authoring root, `data_file`, `page_paths_file`, `tables_file`,
+`visibility_file`, `page_templates_dir`, and `manual_sections_file` are resolved
+under that source root, and `page_index_file`, `pages_dir`, and `state_file` are
+resolved under the configured wiki output root. `templates_dir` and
+`manual_sections_dir` remain as compatibility defaults for deriving
+`page_templates_dir` and `manual_sections_file` when the newer explicit paths
+are omitted.
+
 `paths.source` and `paths.assets` must name real repository subtrees when they
 are configured. They may be omitted for repositories that do not own that class
 of source, but they must not resolve to the repository root (`.`). Output and