una-ada
commented
1 year ago Current categories are decided on as hierarchical tags. type defines the overall category of a work, soft the software used, lang any programming languages involved, lib any external libraries used (which for things like music production are themselves also categorized as soft), and dist as any channels of distribution used in releasing the work.
This system, as pointed out by the music production issue, is mostly focused on software production and therefore is not generalized enough for a whole system of icons. To remedy this, categories should be more specific.
Software, for instance, can be subdivided into DAWs, IDEs, Game Engines, Image Manipulation, &c.
The current organization system for icons by size then type:
Creates an assumed hierarchy where sizes of icons are their own separate versions of the set as a whole, rather than instances of the same icon. This fails to reflect their primary use case as icons on https://xn--z7x.dev/ where both 12px and 30px icons are used, the former for tags and the latter for project headings. The 16px category, which would be used for something like Visual Studio Code icon themes, could theoretically include all 12px icons with a 2px padding on all sides, which should also be differentiated from 16px as a whole. Furthermore, some icons are not square, such as the fmod and picocad icons, which implies that 12px is merely a height.
Considering all these factors, files should be reorganized to reflect mainly category and use-case, then each icon given its own directory into which alternative versions may be added: