This means that we need to repeat these every time we need a new lhnav, making it likely to introduce bugs somewhere. My preferred approach would be to split the lhNavigation definition into 2 separate objects. The first one would be an actions object that looks something like this:

```
var lhNavigationActions = [
    {
        'icon': 'icon-cloud-upload',
        'title': oae.api.i18n.translate('__MSG__UPLOAD__'),
        'class': 'oae-trigger-upload'
    },
    {
        'icon': 'icon-plus-sign',
        'title': oae.api.i18n.translate('__MSG__CREATE__'),
        'children': [
            {
                'icon': 'icon-group',
                'title': oae.api.i18n.translate('__MSG__GROUP__'),
                 'class': 'oae-trigger-creategroup'
            },
            ...
        ]
    }
]
```

The second one would be the `lhNavPages` as existed. In that case, we can also remove the `default` property, as the first element of the `lhNavPages` would be the default page.