Currently, More Sites tab classifies the sites by their site type and course term if there is one, but this has several issues.
-New site types can't be classified apart without hardcoding them.
-New course-like site types or project-like site types can't be isolated from courses/projects.
Our proposal is two optional properties in sakai.properties. One (moresites.externalConfig.siteTypes) with the list of site types and other (moresites.externalConfig.prefix) with the prefix to use in the properties files, so every site type in the list can be classified in More Sites tab by its internationalized property key.
For example, for setting two new site types (courseAsig is a new course type and course 2 is a new site type), sakai.properties would have this:
And the properties "moresites_course_asig" and "moresites_course_2" would be used for the i18n texts in sitenav.properties.
If moresites.externalConfig.siteTypes is not set or is empty, the usual logic is applied.