Currently our tags include architectural styles 'microservice', context of the antipattern e.g. 'system' as well as the type of the json e.g. 'bad_smell'. Maybe we should split these in separate fields. At least into 'tags' and 'category'.
Tags might be split in the presentation layer but the tag field in the JSON files will not be changed. Discussion on how to split the tags field will be continued in #25.
Currently our tags include architectural styles 'microservice', context of the antipattern e.g. 'system' as well as the type of the json e.g. 'bad_smell'. Maybe we should split these in separate fields. At least into 'tags' and 'category'.