instructions, docs, tools: Export - setup-instance und How-to nennen auch die ganze KB, page_export-Docstring nennt die Index-Dateien (#217 close); 10.1.0-beta.22
CI / verify (push) Successful in 8m6s
CI / pwsh (push) Successful in 2m45s
Release / converters (push) Successful in 26s
Release / release (push) Successful in 35s
Release / wiki-mirror (push) Skipped

Files changed:
- CHANGES.md
- VERSION
- docs/how-to/export-to-a-synced-folder.md
- instructions/setup-instance.md
- tools/chemenu/page_export.py

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
This commit is contained in:
torbenandClaude Opus 5.5 committed 2026-10-16 16:01:10 +02:00
1 parent db09e89223
commit 39514be176
5 files changed
+9 -7

No files matched your search

+3 -3
View File
@@ -1,8 +1,8 @@
# Export to a synced folder
Give a reader outside the repository a read-only version of part of `kb/`: the selected pages,
written as files into a folder - typically one a sync client such as OneDrive uploads, so that a
Microsoft 365 tenant can index them. The export is derived. It is regenerated from the committed
Give a reader outside the repository a read-only version of part or all of `kb/`: the selected
pages, written as files into a folder - typically one a sync client such as OneDrive uploads, so
that a Microsoft 365 tenant can index them. The export is derived. It is regenerated from the committed
pages on every run, nobody edits it, and nothing in it flows back into the wiki. What the settings
look like: [configuration reference](../reference/configuration.md#export-to-a-folder).