As we start getting more resource submissions, we'll want a clear set of guidelines for tagging resources so they remain useful. Too much or too little looseness can make tags difficult or unhelpful in practice. Curating them well means every resource that should be under a tag is, and the tags are specific, descriptive, and manageable in number. Here on GitHub we have the topics svelte
, sveltejs
, svelte-v3
, svelte3
, and many un-topic'd projects, which is just a leaky unhappy experience.
The search function already does fuzzy matching against the name, description, url, and other fields, leading me to believe we can be tighter with our tag usage.
As a concrete example, here's our first submission that prompted me to post this: sveltejs/community@db01c41
- name: "`Real World Svelte and Google Cloud Masterclass`"
url: "https://www.youtube.com/playlist?list=PLCrwuqjmVebK08Cwz_XB55cNKFfFYOMGo"
description: A video series taking you through the Real World Svelte app tied in with a Google Cloud Functions backend
tags:
- Sapper
- Real World
- Google Cloud
I'm currently thinking I'd tag this resource with sapper
, videos
, and maybe learning
or education
, and I'd remove Real World
and Google Cloud
, which can be searched.
@kevmodrome brought up the idea of having hierarchical categories. The original resources list was organized that way, and it works well but is unable to express cross-cutting information like labeling official
resources unless they can belong to many categories. Does it make sense to have both nestable categories and tags as distinct systems? Or should we try to make it one system? Should we rethink cramming code libraries and arbitrary links into the same resource system?
The initial set of tags for the community resources came by copying over the headings from awesome-svelte-resources, so consider them a first pass.