With the initial implementation of Guise Mummy, the child navigation links appear in arbitrary order. There needs to be a way to indicate their order. Perhaps:
Setting some mummy-order property in the metadata for each resource should provide an explicit indication of order.
By default they could be ordered using an alphabetical collation without regard to case or marks. (Eventually using a collation based upon the site language would be ideal. Perhaps create a context.getProject().getLanguage() or something, and set it by default to en-US.)
It remains to be determined if default-ordered items appear before or after explicit-ordered items; or if negative ordered items appear before default ordered items; or if default-ordered items all get some implicit order number, and ordering occurs first by order (whether explicit or implicit) and then by collation.
There needs to be some way to indicate that "this item goes before the others" and "this item goes after the others".
Following these other specifications, it seems reasonable to have all the navigation items default to an order of 0, and allow explicit negative orders to sort things to the front.
One detail is that recognized prefixes (e.g. og:) in metadata from need to be given actual namespaces. So the mummy: prefix in metadata should be recognized to indicate the https://guise.io/name/mummy/ namespace.