Denote source availability for recommended tools

[pedroluccasc]

@overdrawn98901

I don’t think we should bias heavily towards FOSS and entirely exclude Proprietary, but rather lay out the facts as-is for the user and what they can expect.

This is exactly what I was thinking when I first wrote it.

@overdrawn98901

Further, having a dedicated FOSS vs Proprietary page should help readers understand how to make decisions with this information. I don’t think we should bias heavily towards FOSS and entirely exclude Proprietary, but rather lay out the facts as-is for the user and what they can expect.

@overdrawn98901

A simplified icon could standardize this, and enforce a consistent reader experience across all recommendations. However, we may also consider to leave in the text, or ensure that the icon is properly labelled with accessibility attributes.

In my opinion, these are the best ways to move forward. However, we should prioritize readability to ensure that both novices and experts can easily understand the differences between FOOS and Proprietary, as well as the distinctions between the project lists.