Skip to content

project_mtp_nav_depth.md

Latest commit

 

History

History
31 lines (23 loc) · 2.35 KB

project_mtp_nav_depth.md

File metadata and controls

31 lines (23 loc) · 2.35 KB
Raw
name project-mtp-nav-depth
description Navigation depth model for mtp-web shell — 4 levels (module → group → page → in-page tab), collapsible submenu groups, Ctrl-K palette, never 5-deep.
metadata
type
project

Navigation depth — mtp-web shell

ERP breadth needs 4 navigation levels, not the 2 the current mockups appear to show. The depth already exists in the mockups, just hidden well.

Level Name Where rendered Mockup proof
1 Module Icon rail (60px, dark, Zoho-style) --rail-w:60px in zoho.html / accounting.html
2 Group Submenu section header sub-section-label ("Workflow", "Books", "Pinned")
3 Page Submenu item submenu body links
4 View / Tab In-page tabs Approvals Inbox/Outbox/Team; bank-recon Books/Stmt

So chrome = rail → submenu groups → submenu items → in-page tabs.

Why: Real ERP surface (Accounting Reports = P&L/BS/TB/CashFlow; GST = GSTR-1/3B/Reco/E-invoice; TDS = Entries/26Q/24Q/Form16A; Exam = Setup/Conduct/Results; Fees = Heads/Slabs/Concessions; Students = Master/Lifecycle) does not fit in a flat 2-level menu without either a giant flat list or burying pages.

How to apply (rules):

  • Submenu stays flat with collapsible group headers — sub-section-label becomes click-to-expand/collapse, not just a visual divider.
  • In-page tabs for tight variants of the same screen (Inbox/Outbox, Books/Statement). Not for distinct pages.
  • Never go 5-deep. A felt 5th level = signal a screen must split into two pages.
  • Ctrl-K command palette for power users — bypasses depth entirely (search "GSTR-1" → land on screen). Top-search bar already wired. Transfers Tally F-key muscle memory to fuzzy search.

Note on entity-360 hubs (staff-360, future student-360): these add a vertical tab rail (--vtab-w:240px) inside the page that switches record sections (11 panels in staff-360). That vertical tab rail IS level-4 (in-page tab) for those record-detail screens — not a 5th level. The rail/submenu (levels 1-2) still wrap it.

Drives: mtp-web AppShell layout, [[project-mtp-repo-topology]] feature-folder routing, ADR-0008 folder structure. Each feature manifest declares its Group (level 2) so the submenu auto-builds. Pages doc (pages.html) must tag each screen with its 4-level coordinate (module/group/page/tab).