Show release version info for modules/properties/etc.

[chasenlehara]

We used to show release info for our modules: see the 2.1 on this page:

We still have that information in some of our repositories but we’re not showing it. It’s a little bit more complicated now that any given thing has two release versions—one in the module, another in the packaged version of CanJS. We will probably want to display both, but I’m not 100% sure.

[jamiemccue]

@chasenlehara

• show module release version number
• show API release version number
• discuss using the term 'introduced': example: can-param 1.0.1 introduced CanJS 3.6
• Bit docs will figure out how it corresponds to the current major CanJS version

Examples in keeping with the brutalist theme. These need refining once we chose a direction.

[jamiemccue]

• remove module 2.0 text - leave introduced...

• make button - link to canjs

• or make label -

• right align 2nd number

• mobile - above and below

[jamiemccue]

Use button style similar to other buttons:

Mobile:

[jamiemccue]

@chasenlehara Do you have any feedback on these recent mockups?

[chasenlehara]

Looks good, thanks @jamiemccue! Moving this to @imaustink’s backlog for implementation.

[tomgreever]

I'd like to recommend simplifying this design by including the name of the collection and the CanJS version next to the title in smaller text.

There are a couple of reasons for this:

1. I'm afraid of overloading the user with too many buttons on the right side
2. Buttons indicate an action, where as text or a link indicate a location. Clicking a button makes sense for editing, Starring, or getting on npm - whereas taking the user to a different page would be more appropriate with just text

I think we can also combine this with the need to include the title of the collection, like Ecosystem.

Here's my recommendation for both. If "3.6+" links to release notes, it would be blue. If not, it would be grey. I think just "3.6+" is enough in this context without saying something like, "Introduced in CanJS..."

[chasenlehara]

I think this is good; for core/infrastructure/ecosystem/legacy, we could link to the collection’s page for people to get more info about what it means.