Find more useful features for project listing page

[agjohnson]

What to do with the project listing page? It's rather empty and could be more useful.

• List more metadata for each project?
  • Last successful build of each version? Each popular version?
  • Metadata like build count? Number of versions active/inactive/etc -- or build passing/build failed/inactive?

Merged from another issue:

Replace project list build list with something more intelligent. Right now, it is only selecting the stable build and the latest build. This doesn't work for a number of cases, like projects not using latest, and could be something more helpful, like most popular versions, most recently built versions, or most frequently build versions.

• What versions do we list?
• How many versions do we list?

[agjohnson]

I am trying a slight redesign and came up with something I quite like, unfortunately for #128, response time is even slower

This uses a number of fields that won't be cached and I can't come up with an alternative sub heading that is ~5 words and would be cached. We might want to consider making a model property field that is cached, similar to some of the other property fields.

The only thing so far is I also can't come up with a good default description for a project, when there are no special configurations. It definitely looks better with two lines, one heading and one sub heading.

[agjohnson]

I've updated this with b801bd5

I'm not in love with this, and again, don't think latest build is super useful, but we'll need some backend changes to make metadata here useful and performant. The addition of the right cards column helps the usability of this page, as we don't need to rely on the listing view for features on the page.

I think this satisfies my wants for now, but I would like to return to this later with some metadata that is more helpful to the user.