You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be consensus that alphabetical ordering of the sub-lists is the most manageable long-term as this list continues to grow, while still acknowledging that alpha sort does remove some defacto information whether that by maintainer-recommended items appearing first, or just having the sub-lists be chronological.
Add a "contribution date" or "last updated date" to entries (cons: fair amount of overhead on maintaining this)
Using emoji as potential recommendation or highlight indicators
'add a “New for ’21” starburst to anything we add this year. Next year, the first time we do an update, wipe away all the “New for ’21" badges and start adding “new for ’22”.'
Creating this issue to continue that discussion, while not blocking the consensus around #301, which seems to solve some immediate confusion around additions to the list
The text was updated successfully, but these errors were encountered:
I think we should discuss this during the next Fall Working Meeting and have a dedicated Awesome IIIF session where we make decision and prune the repo. I am not against the idea of adding a date, but we are so few curating this list that this (new) work involved will, in my opinion, be counterproductive if we do not succeed in recruiting other people.
Lightest-weight approach probably best, perhaps a combo of bullets 2 and 3 above: Using 🆕 (or something more exciting) and wiping it every year or semi-annually
There seems to be consensus that alphabetical ordering of the sub-lists is the most manageable long-term as this list continues to grow, while still acknowledging that alpha sort does remove some defacto information whether that by maintainer-recommended items appearing first, or just having the sub-lists be chronological.
See also #149 on the topic of order-based recommendations, and also discussion on IIIF Slack #Curators-of-Awesome channel
Possibilities include:
Creating this issue to continue that discussion, while not blocking the consensus around #301, which seems to solve some immediate confusion around additions to the list
The text was updated successfully, but these errors were encountered: