Thank you for your time. I like the idea of using colors and perhaps an illustrated overview of the available plugins. I want to keep the process as simple as possible for my customers.
The game + DLC example you gave is a great example of how other marketplaces deal with dependencies. Steam for example will show the following message for DLC:
They however do not block the buyer from getting DLC without having the base game. With software this can make sense as you might want to buy a plugin without its core dependencies just to get a part of the source. I do however want a BIG “You require A, B, C” to compile this product and make absolutely sure that no one gets this wrong. To simplify the buying process I’d like to give the option to the buyer to add the dependencies to the cart automatically, excluding products one has already bought. This should be a “3 step” clear process.
Sketch:
Also, will products “contained” by the bundle be marked as “bought” automatically if you buy the combined framework? Of course there might be small integration differences to combine the plugins into 1 framework but the end product is the same. I would like to mark all plugins contained by the framework as “bought” when someone buys the framework. This would include future updates and added content to the framework product.