Publish curated itworx-knowledge-hub source from 883ef812ee04516208b84972195b5e2a46207e44

README.md

@@ -48,6 +48,12 @@ secrets, persist every documented data volume and test restore before relying on
 backup. Start from the reviewed [Docker Compose configuration](docker-compose.yml) and
 the [backup/restore guide](docs/guides/back-ups-herstel-en-unraid-beheer.md).
 
+## Organize your first knowledge space
+
+After first-run owner setup, create a small page, edit its Markdown and inspect the saved revision. Add a project dossier when you need structured decisions and runbooks, then test search with words from your own content. Keep drafts distinct from published reference material.
+
+For LeafWiki migration, review the import preflight and conflicts before execution; retain the import identifier for validation and rollback. The source snapshot stays read-only. External applications should use a separately scoped service account rather than the owner's browser credentials.
+
 ## Architecture
 
 ```text
@@ -69,6 +75,8 @@ truth, and attachments are stored by SHA-256 outside the database.
 
 ## Development and verification
 
+Backend development uses the .NET SDK pinned in `global.json` (10.0.302, with `latestFeature` roll-forward). The container build supplies its own SDK; host SDK tooling is for development.
+
 ```bash
 corepack pnpm install --frozen-lockfile
 node scripts/verify.mjs --fast