Open is984 opened 2 years ago
Thank you for your suggestion. It is reasonable. I will take your suggestion into consideration to improve the options page.
The groups and the order now is arranged according to the tabs in https://www.hololive.tv/member, but merged into one page. (Oh Hololive China has been removed...) It sorts the members according to the debut time. So do I.
One of the reasons why I did not make subgroups like 0th when I was designing this page is that I think there are few users who will make changes (subscribe to or unsubscribe) to a specific generation.
Also, Mio, Okayu and Korone all belongs to Gamers. Where should Fubuki stay? If a member can belong to multiple groups, should I add groups like the 卍-Gumi, ShiraKen, OKFAMS, etc? Nobody could tell all the unofficial groups. It was hard for me to answer so I did not made groups.
...OK all the 'reasons' above could be just excuses. Perhaps the ultimate reason is that I don't have a design which is good enough to display the subgroups. Making changes to the current page is not difficult but will definitely make it ugly.
For the grouping issue, I think we can take the design from the official page: https://hololive.hololivepro.com/talents. The filter could be the standard to group the members.
Also, Mio, Okayu and Korone all belongs to Gamers. Where should Fubuki stay? If a member can belong to multiple groups, should I add groups like the 卍-Gumi, ShiraKen, OKFAMS, etc? Nobody could tell all the unofficial groups. It was hard for me to answer so I did not made groups.
Is your feature request related to a problem? Please describe. I think the list is getting a little hard to read as there are more and more holo-live members.
Describe the solution you'd like Grouping by generation makes the list more concise and easier to read.
Describe alternatives you've considered Implement the generation as a subgroup.
Example
Additional context I understand that implementing this suggestion would be very difficult as it would require significant changes to the layout. If you find it difficult to implement or not worth the cost, it is perfectly acceptable to reject this proposal. (Actually, I wish I could write the code.