We're starting to have more contributions for custom themes and extensions. I think it's about time we start to catalog these nicely.
One of the unfortunate realities of open source efforts is that these efforts are often fragmented and scattered all over the place, making things difficult to find. With that in mind, I've started a new GitLab project here consisting of a simple README file that we can use to start tracking the client-side themes and extensions that the community here has been hard at work developing.
The list, at the time of posting this, is empty. The README is sparse and the entire thing is subject to change by the community itself. I will only be reviewing changes to ensure that changes are acceptable before a merge is allowed through (we don't want e.g. malicious links thrown in or perfectly good projects removed by someone acting in bad faith). You can change contribution notes/guidelines, existing language, layout, categories, and whatever else you can think of. If there's something else that you think the repository could use aside from the README, then you're free to issue a merge request to have it reviewed as well.
I'm hoping that this will help us keep track of everything and aid future users in discovering the various tools and themes provided by the community.
Please feel free to discuss guidelines here. Is there anything that shouldn't be allowed on the list? Is there anything that should be taken care of immediately? Are there any immediate concerns? Is there anything else on your mind?
Is it not possible to contribute to docs.tildes.net? I think that'd be a much better place than a random Gitlab project. I'm not sure how @Deimos would feel about this, though, so his input would be appreciated here.
Yeah, I'm not entirely sure if it's something that should go in the Docs section. If he's for it, then sure, I'll just discard the repo and open up a section there.
That's what I was feeling as well. A sticky or a link somewhere on the site itself, but it doesn't feel like a Docs thing. Either way, it's really a decision for @Deimos to make in the end. I'm just taking the safest route that feels the most sensible for the time being :)
A quick shout-out to @Bauke for the initial contributions and follow-up feedback! We've been having a good, constructive back-and-forth about some changes that are really fleshing it out.
Of note is that updating the listing should be easier for those who aren't as familiar with the git workflow. Specifically, as long as you submit an issue using one of the preset templates provided, I--or any contributors or future members added to the repo who choose to take up the task--can handle the update for you :)