How should we manage the Atlassian Product lines?

While it is not exactly a problem, there is a distinction between what is an Atlassian Product and what is a feature that is sometimes overlooked. For example, Jira Service Management is a product and in Jira Service Management we also have Assets, which is a product, but not a standalone product...if that makes sense. So the question is how to handle that in a way that is both trackable and easy to understand?

I think the problem is not so much to set this up as it is to present it. So while I can just create the products as categories and then have the Features as subcategories, it will mean that I separate content from the main product. This is because I can't have a data object connected to more than one category.

So what I can do instead is to work with Prefixes.  This allows us to mark articles and stories that are for example related to Data Center or Cloud, but also if it is related to a Feature like Assets or Plans. While I can't lock down the Prefixes per category, and it will be a little messy if people start to abuse it, I think it will be worth exploring it to see how it will pan out.

I will also ponder a bit on how to make this visible in the product pages as well once I get to those.