[SR-15434] [Swift-DocC] Support custom documentation module kinds

[ethan-kusters]

Previous ID	SR-15434
Radar	rdar://83448323
Original Reporter	@ethan-kusters
Type	Improvement
Status	Resolved
Resolution	Done

Additional Detail from JIRA

Votes	2
Component/s	Swift-DocC
Labels	Improvement
Assignee	@ethan-kusters
Priority	Medium

md5: 6206e14f17a5fa158306a795d8f034f6

Issue Description:

Swift-DocC currently describes every documentation catalog it produces as a “Framework”.

For example, DocC’s own user-facing documentation at https://swift.org/documentation/docc/ is currently incorrectly described as a “Framework”.

While SwiftDocC is a framework, the documentation hosted at https://swift.org/documentation/docc/ is documentation explaining how to use DocC as a tool; it is not documentation of the SwiftDocC framework.

Swift-DocC should be enhanced to allow documentation authors to provide custom text to describe the thing they are documenting. This should allow the DocC user-facing documentation to describe itself as a “Documentation Tool” instead of as a “Framework”. This should also allow for build systems that integrate with DocC to accurately produce documentation for other product types, like executables.

[ethan-kusters]

[[SR-15434] Add support for custom (non-framework) module kinds|#33]

[ethan-kusters]

0752acf