Prepare the product

Create src/docs/en/_index.md and/or src/docs/de/_index.md in the product repository. Add Markdown pages and page-bundle assets below those roots. Do not commit a Hugo website or a copy of the theme there.

Register the source

Add one tab-separated row to products.tsv:

  onlinemeetinglink	KYANIS-GmbH/kyanis-onlinemeeting	src/docs

The fields are a stable public URL slug, GitHub owner/repository, and source root relative to the product repository. The default branch is discovered remotely; no main assumption is made by the importer.

The example maps to /en/onlinemeetinglink/ and /de/onlinemeetinglink/ when those language sources exist. Slugs must be lowercase words separated by hyphens. Do not reuse guide, en, de, another product slug, or an existing central content section. Source roots use simple path components without ...

Grant read access

Install the documentation read GitHub App on the product repository. The initial CI setup supports source repositories under the same GitHub owner as the central repository. Cross-owner sources require separate installation tokens and are outside the initial workflow.

Connect automatic updates

Copy .github/product-workflows/notify-docs.yml from the central repository to .github/workflows/notify-docs.yml in the product repository. Configure its notification App credentials as described in Publishing.

The workflow detects documentation changes on the repository’s default branch and notifies the central site. If you change the source root, update its path filter too. The event is only a notification: central CI reads its own registry and the actual default branch, not arbitrary refs from the event payload.

Verify

Run the importer and Hugo locally, then verify the pages and images in each available language. After merging the product workflow, change a documentation page on its default branch and confirm the central deployment runs. Registration alone is not proof that the notification workflow has been installed.