Being able to use content variants for content that is semantically different

[kchonka-kognitos]

What's your feature/idea?
Being able to use content variants for content that is semantically different. It would be useful to have one singular space to document two different versions of the same feature (where one version has components that the other one doesn't).

This doesn't work well right now, as there are errors that get thrown when a page exists in one variant but not another. Right now, the guidance in GitBook's documentation is to "to use variants as variations of the same content."

What's your desired outcome?

Better handling of content variants that are semantically different. Errors aren't being thrown when a user tries to use the variant selector to navigate between v1 and v2.

What's the impact of this for you?

• Critical
• High
• Medium
• Low