Fix wiki deploy
This commit is contained in:
@@ -244,6 +244,7 @@ topdata:
|
||||
deploy_manifest: .wiki_deploy_manifest.json
|
||||
deploy_edit_summary: Auto-generated from native builder
|
||||
title_prefix_min_length: 3
|
||||
status_listing_scope: all
|
||||
|
||||
autogen:
|
||||
cache:
|
||||
@@ -304,6 +305,11 @@ setting remains as a module-only compatibility alias when `consume_archives` is
|
||||
not set. Stale cleanup is scoped to roots actually touched by extracted
|
||||
resources, so the default module-only extraction does not prune assets.
|
||||
|
||||
`topdata.wiki.status_listing_scope` controls the generated wiki-status detail
|
||||
pages. The default `all` writes both per-namespace listings and aggregate
|
||||
`meta:wikistatus:<status>` listings. Use `namespace` when aggregate status
|
||||
lists would be too large for the target NodeBB post limit.
|
||||
|
||||
GFF JSON extraction can merge selected fields and lists from the existing source
|
||||
file instead of replacing the whole extracted document. Rules are matched by
|
||||
`target` relative to `paths.source`; files without a matching rule keep the
|
||||
|
||||
Reference in New Issue
Block a user