Breaking down projects into resources, infra, and one-offs

[mattxwang]

I think broadly, we support three types of repos:

1. Resources (our most numerous). These are workshop resources, tutorials, teaching material, etc. This is "open-source" in the content sense (with occasional demos).
2. Infrastructure. These are projects that support ACM / a committee and are actively maintained. These are the projects that are the easiest to showcase as open-source; there is continued activity, and hopefully, a good contribution workflow (design docs, review, CI/CD, etc.). I'm thinking our websites, active LLs, membership portal, cyber platform, etc.
3. One-offs. These are projects that were completed for a certain event or purpose, but are not actively maintained for one reason or another. These are not as easy to contribute to, and occasionally lack the requisite infra to do so. I'm thinking mostly about Teach LA's learning labs that enter hibernation mode, though I'm willing to be corrected on this!

I want to make this demarcation very clear on the website; either by categorizing projects, or creating different filters/pages for this. In particular, while resources dominate most of our GitHub repository count, the infrastructure (and maybe the one-offs) are the more interesting open-source content (IMO).

Open to thoughts :)