[Feature] Define module manifest fields for documentation contributions #6

Closed
opened 2026-07-07 21:05:28 +02:00 by zemion · 1 comment
Owner

Imported from the repository seed backlog.

  • Source: /mnt/DATA/git/govoplan-docs/docs/DOCS_BACKLOG.md
  • Line: 13
  • Section: P2 Module Integration
  • Milestone: P2 Module Integration

Backlog item:

Define module manifest fields for documentation contributions
<!-- codex-module-seed-fingerprint:fe5b04ae00638366badb4017 --> Imported from the repository seed backlog. - Source: `/mnt/DATA/git/govoplan-docs/docs/DOCS_BACKLOG.md` - Line: `13` - Section: `P2 Module Integration` - Milestone: `P2 Module Integration` Backlog item: ```text Define module manifest fields for documentation contributions ```
zemion added this to the P2 Module Integration milestone 2026-07-07 21:05:28 +02:00
Author
Owner

Completed

The module contract now defines typed documentation, documentation_providers, documentation_configuration_providers, and documentation_sources manifest contributions. The Docs registry consumes these fields with role, module, capability, route, scope, configuration, and source visibility tests. Further source integrations remain separately tracked by Docs #8 and #9.

<!-- codex-routing-2026-07-31:docs-6-complete --> ## Completed The module contract now defines typed `documentation`, `documentation_providers`, `documentation_configuration_providers`, and `documentation_sources` manifest contributions. The Docs registry consumes these fields with role, module, capability, route, scope, configuration, and source visibility tests. Further source integrations remain separately tracked by Docs #8 and #9.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-docs#6