In Office, in the development mode, all classes are available as they are (subject to permissions). However, it is better to have a specific structure that matches the functionality of the app. It can set the order of classes, grouping, display on demand or filtering objects according to various criteria.

Navigation is a separate metadata module (node_modules/evado-meta-navigation) used to create a convenient user menu.

Navigation data consists of sections and nodes. Section is a set of nodes arranged in a specific order. For example, main section is responsible for creating the Office side menu. Node is a link to a site page. Each node can have child nodes, forming a tree-like menu hierarchy.

Go to Studio and select Navigation sections from side menu. Create a main section. Create a articles node. This will be parent node for lists of articles in various statuses. Go to Children tab and create a publicArticles node. Select article in the Class field and select publicList in the View field.

Node code name must be unique within parent section.

Create another child node allArticles. Choose article class without a view, so that users can access articles in any status.

Export metadata and go to Office. Nodes of the main navigation section will appear in the side menu.