"Todos" is not like the other pages in the left nav. It pertains to the current chat session, it is not a global page; however the left navigation is for pages that are global, so it's confusing when going there that it does not match that expectation. Todos is more like a sidebar for a currently active chat session; but I kinda get it, there's no mechanism for activating such a sidebar (yet).
Recommend a more structured dual-purpose navigation approach for consistent and predictable information architecture:
- Left-hand navigation: top-level pages and features, such as Chats, Tasks, Kanban, Settings, etc. (basically everything except Todos)
- Top header that better follows the page hierarchy: Hermes logo and customizable agent name top-left that takes you Home when clicked (to Chats); Right side of top header has sub-controls for the current page, one of which can be ToDos for the current Chat session when in a chat session. The center can remain the page/feature title as it is today.
This would create a 2-level hierarchy enabling a place for sub-features within a page, which is logical for the Todos feature.
Items clicked in this contextual area would open as right-hand drawers or sidebars, to go alongside the current view. They should not overlay the content but be more like a split-screen, so they can stay open.
One could imagine other contextual features within each of the main top-level functions, for example viewing a Kanban item quickly without leaving your list. Lots of potential uses in a standard and predictable way.
"Todos" is not like the other pages in the left nav. It pertains to the current chat session, it is not a global page; however the left navigation is for pages that are global, so it's confusing when going there that it does not match that expectation. Todos is more like a sidebar for a currently active chat session; but I kinda get it, there's no mechanism for activating such a sidebar (yet).
Recommend a more structured dual-purpose navigation approach for consistent and predictable information architecture:
This would create a 2-level hierarchy enabling a place for sub-features within a page, which is logical for the Todos feature.
Items clicked in this contextual area would open as right-hand drawers or sidebars, to go alongside the current view. They should not overlay the content but be more like a split-screen, so they can stay open.
One could imagine other contextual features within each of the main top-level functions, for example viewing a Kanban item quickly without leaving your list. Lots of potential uses in a standard and predictable way.