Should we be logically grouping exercises?

[tleen]

Would it be helpful at the problem-specification level to logically group exercises? I am thinking this may be valuable in auto-configuring some tracks or at least providing some meta-organization.

Some exercises are closely linked thematically. Some are very mathematical in nature, some are "here is a string, find stuff in it", but there is a good amount of thematic overlap in a lot of exercises.

While prepping for the new config file structure for nextercism in the Go track we spent some time trying to formalize these relationships. It was recently brought up that perhaps there is a place for some of this globally.

To me the most obvious are *gram. anagram, isogram, pangram, acronym: the string finders. This seems to be the kind of exercise where one is important in core but others (being so similar) are better off as unlocks off of the primary exercise. Would identifying these as possible thematic suggestions be helpful for tracks still looking to make their nextercism configurations?