When DocC builds documentation for one platform it gets the information from each symbol’s @available
attribute to know what platforms and versions each symbol is available for. If a symbol has no explicit availability attribute, DocC assumes that the symbols is available on all platforms.
In the rendered documentation, each symbol displays this availability information to the side in wide viewports, or above the declaration in narrow viewports.
There’s a known issue that symbols that are marked unconditionally unavailable from the platform being built (for example @available(macOS, unavailable)
) are excluded from the built documentation.
If you have other use-cases that would benefit from a different structure to the rendered documentation, we’d love to hear about that in a Feedback.