Revise Projects Page#656
Conversation
Revises the projects index to group projects in some fashion. I have split out Organization and Affiliate projects to separate sections, then broke the org projects into a few more groups to highlight the most important ones.
| }, | ||
| { | ||
| title: "Cats Collections" | ||
| description: "Niche purely functional collection types" |
There was a problem hiding this comment.
I'm sorry, but I take exception at characterizing cats-collections as "niche". It has a cats.Hash-based hashmap and a cats.Order-based treemap. Those are not niche, but the cats-compatible versions of two of the most fundamental data structures.
I'm sure most people just use the stdlib maps. But I think that's mainly a visibility issue. And putting cats-collections into "miscellaneous", and calling it "niche" exacerbates that visibility issue. In my opinion, of course.
There was a problem hiding this comment.
The documentation for that project is not helping. It doesn’t mention the tree or hashmap, so I don’t know how anyone is supposed to figure out they’re even there without diving into the source code. I didn’t know.
I don’t love the Miscellaneous name, but was getting to a point where grouping things more seemed less useful. Any suggestions for a better category?
There was a problem hiding this comment.
Simply "Other" may come across as more neutral-sounding, maybe?
| platforms: [js, jvm, native] | ||
| }, | ||
| { | ||
| title: "Cats MTL" |
There was a problem hiding this comment.
Nowadays Cats Effect depends on Cats MTL, so in a way it's just as fundamental.
There was a problem hiding this comment.
Sure, but the point of this structure is to point at the things for users to use. Actually making use of MTL in user code is pretty optional.
| }, | ||
| { | ||
| title: "cats-stm" | ||
| description: "A STM implementation for Cats Effect" |
There was a problem hiding this comment.
Might be worth spelling out what STM is. But I defer to @TimWSpence of course.
3 participants
Revises the projects index to group projects in some fashion. I have split out Organization and Affiliate projects to separate sections, then broke the org projects into a few more groups to highlight the most important ones.
The big changes are:
The directory file itself is completely reorganized to sections from alphabetical so that diff is unfortunately large.
Alternatively to the full org/affiliate split, I could add the affiliate tag back and put the affiliates under the same groups as the org ones.
There is still a bit of cleanup I need to do, but this seemed like a good point to solicit some feedback. Still TODO:
Preview