Dashboards hierarchy

We are going to understand Dashboards hierarchy as the content organization of an entire business. The general content that groups reports into dashboards. We currently have different options to be able to organize the content, not only in paths and subpaths. 
​
These organization capabilities are currently offered:
Path
Subpath
​
​
​
​
Characteristics:
Main element of organization 
It is located on the side of the page 
It can contain reports or serve only as a bundler and not contain reports
Characteristics:
Child element of path 
It is located on the side of the page 
Must contain reports
​
Main use:
Main navigation element.
It should normally show overviews or data summary of the whole group.
Organize groups of dashboards if content is not required.
Main use:
Secondary organization element.
It is advisable not to abuse subphats, from 8 Subpaths it is advisable to look for another form of organization. (See "Tabs" or "Hidden paths")

 Recommendations 

Use capital letter only in the first letter of the word
Use descriptive names that help to understand the objective of the path. Example: "Sales" (Data about sales in your business)

 Recommendations 

Use capital letter only in the first letter of the word
Use descriptive names that help to understand the objective of the path. Example: "Detailed" (Detailed data of your sales in your business)

 Warnings 
It is recommended not to use capital letters for the entire word or words. Unless it is required from the client.
Texts with words of more than 40/50 characters will have a truncated ellipsis after this amount.
 Warnings 
It is recommended not to use capital letters for the entire word or words. Unless it is required from the client.
Texts with words of more than 25/35 characters will have an ellipsis truncated from this amount.
​
Hidden path&Subpath
Tabs
​
​
​
​
Characteristics:
These elements share the same characteristics as Path&Subpath 
They are not visible in the drawer. This allows an organization of elements of greater quantity 
It is necessary to have an access point to these Hidden. For this reason, the use of indicators or tables with urls for these spaces is recommended.
Characteristics:
Grouping elements and easily accessible reports. 
They are located inside a dashboard. 
It is a navigation alternative to subpaths. 
It can be placed in different positions within a dashboard. But it is advisable to always place it in the second position, after a title.
​
Main use:
In case of having too many records, so as not to collapse the drawer. More than 10 subpaths are considered too many elements.
Obtain a second level of detail within the same space. Example: Within "Sales" we can have an indicator that does not link to hidden paths or subpaths with information on a specific sales process or product.


Main use:
Classify data reports with a similar level of association. Example for "Team": "All team members", "Department 1", "Department 2", "Department 3", "Department 4" 
Separation of complementary content. Example: "Questions" / "Answers" 
Vertical space saving. If we believe that the amount of data that we are showing on the same screen is excessive (5/6 scrolls*) we should see how to separate this into 2 tabs.
 Recommendations 
​
Always activate breadcrumb to improve navigation 
It is recommended to activate the history navigation
 Recommendations 
​
Use descriptive names that help to understand the purpose of the Tab. Example: "Questions" / "Answers"

 Warnings 
​
Do not include more than two levels of hidden path subpath within a space
 Warnings 
​
Do not abuse more than 8/9 tabs
It is not recommended to place the tabs in intermediate positions of a dashboard.
​
​Breadcrumb​
This functionality is used to provide context in dashboards. 
Simply place the source and the current page being viewed in a text at the top left of the dashboard

​History navigation​
This functionality introduces two buttons for quick navigation similar to that of the browser but you are inside Shimoku. 
Its use is recommended for apps that have hidden paths and sub paths

​
​

Path	Subpath

Characteristics: Main element of organization It is located on the side of the page It can contain reports or serve only as a bundler and not contain reports	Characteristics: Child element of path It is located on the side of the page Must contain reports
Main use: Main navigation element. It should normally show overviews or data summary of the whole group. Organize groups of dashboards if content is not required.	Main use: Secondary organization element. It is advisable not to abuse subphats, from 8 Subpaths it is advisable to look for another form of organization. (See "Tabs" or "Hidden paths")
Recommendations Use capital letter only in the first letter of the word Use descriptive names that help to understand the objective of the path. Example: "Sales" (Data about sales in your business)	Recommendations Use capital letter only in the first letter of the word Use descriptive names that help to understand the objective of the path. Example: "Detailed" (Detailed data of your sales in your business)
Warnings It is recommended not to use capital letters for the entire word or words. Unless it is required from the client. Texts with words of more than 40/50 characters will have a truncated ellipsis after this amount.	Warnings It is recommended not to use capital letters for the entire word or words. Unless it is required from the client. Texts with words of more than 25/35 characters will have an ellipsis truncated from this amount.

Hidden path&Subpath	Tabs

Characteristics: These elements share the same characteristics as Path&Subpath They are not visible in the drawer. This allows an organization of elements of greater quantity It is necessary to have an access point to these Hidden. For this reason, the use of indicators or tables with urls for these spaces is recommended.	Characteristics: Grouping elements and easily accessible reports. They are located inside a dashboard. It is a navigation alternative to subpaths. It can be placed in different positions within a dashboard. But it is advisable to always place it in the second position, after a title.
Main use: In case of having too many records, so as not to collapse the drawer. More than 10 subpaths are considered too many elements. Obtain a second level of detail within the same space. Example: Within "Sales" we can have an indicator that does not link to hidden paths or subpaths with information on a specific sales process or product.	Main use: Classify data reports with a similar level of association. Example for "Team": "All team members", "Department 1", "Department 2", "Department 3", "Department 4" Separation of complementary content. Example: "Questions" / "Answers" Vertical space saving. If we believe that the amount of data that we are showing on the same screen is excessive (5/6 scrolls*) we should see how to separate this into 2 tabs.
Recommendations Always activate breadcrumb to improve navigation It is recommended to activate the history navigation	Recommendations Use descriptive names that help to understand the purpose of the Tab. Example: "Questions" / "Answers"
Warnings Do not include more than two levels of hidden path subpath within a space	Warnings Do not abuse more than 8/9 tabs It is not recommended to place the tabs in intermediate positions of a dashboard.

Visual hierarchy

Information and context

Last modified 1mo ago

Dashboards hierarchy

​Breadcrumb​

​History navigation​

Breadcrumb

History navigation