Hunter! A very hearty "welcome"! Your ears must have been burning recently because I've made frequent mention of Clade Finder: https://cladefinder.yseq.net/.
Something you might want to look at is the WikiTree Apps Project: https://www.wikitree.com/wiki/Project:WikiTree_Apps. There is a dedicated field for Y-haplogroup in relevant records in the WikiTree SQL database, but I don't believe much is done with it, programmatically speaking. And because so many more males have taken autosomal tests than for-purpose Y-STR or Y-SNP tests, an interesting thought might be to find a way to build an API with Clade Finder in such a way that a result there could be automatically inserted into an "Other yDNA" test results record on the person's profile at WikiTree. I believe we could increase the number of visible haplogroups by a factor of magnitude, make it extremely easy for members to extract their haplogroups from the atDNA results, make certain that those haplogroups are recorded consistently on WikiTree, and make it an automatic, painless process for the WikiTree member. Might be a way to benefit WikiTree while also gathering data for your L283 project.
Just thinking out loud, here.
Another haplogroup issue that's been a hindrance--in my opinion--to using them effectively on WikiTree is that the integral system of categorization (https://www.wikitree.com/wiki/Category:Categories) is one that is foundationally manual. There's really no good way to adapt it to accommodate Y-haplogroups (mtDNA much less of a problem, of course).
With the FTDNA haplotree having added about 8,000 new branches to the haplotree this year alone, the only way we'll ever be able to manage the data is programmatically. For example, if someone takes a Big Y-700 and learns they are J-FT197991, there is no way currently to understand, visually represent, and categorize them as being in a subclade of L283--or M102 for that matter--so the parent clade associations are essentially lost. We see questions here on G2G somewhat frequently to the effect: "One man is R-M269 but his patrilineal 1st cousin is R-FGC39928. Since they aren't the same haplogroup, does that mean there is an NPE in the line?"
I know the haplotree disconnects between FTDNA and Adamov and company at YFull create an issue. But, really, being able to use either of them as way to help WikiTreers see or understand the hierarchical relationships among haplogroups would be extremely helpful.
In your project name you use the hybrid system of the YCC name for the basal clade first, followed by the short-form SNP subclade. An excellent nomenclature, but one not followed here at WikiTree. One alternative to the haplogroup naming issue may also be to work with Aleš Trtnik so that, in nightly (or weekly) batch processing, we might standardize on that hybrid system by doing a substitution to replace Y-haplogroup fields across the database. For example, J-FT197991 would automatically change to J2b-FT197991, and R-M269 and R-FGC39928 to R1b1-M269 and R1b1-FGC39928. That step alone could go a long way to helping members and visitors immediately see the high-level connection among haplogroups.
And... I truly didn't mean to start building a task list. It's just good to see you here, and ideas for improvements just sorta spontaneously combusted.
