I appreciate the feedback but not sure I agree that it should be alphabetical. Currently it is controlled by the sort rank in the feature definition file so developers can influence the position of the feature in the list. My intention was that the most commonly used features such as Html content should be first in the list and infrequently used features should be lower in the list.
If we were to change it I think it would make more sense to sort it by the number of uses of the feature descending and then alphabetically so that the most commonly used features are still at the top.
But I'm not sure that is even needed and it is certainly a lower priority vs other things that need to be worked on.
For the features that ship with mojoPortal I'm open to suggestion about the relative priority of how they should be sorted (ie opinions about which features are most commonly used vs least used) as this could be changed easily form the feature definition files without any development effort.