[UX] Console Navigation & Scalability Improvements

[riverma]

Summary

The MAAP Console currently uses a top horizontal navigation bar with four items (Dashboard, Jobs, Batches, Help). As the platform grows to support additional capabilities, this navigation pattern will not scale well and may compromise discoverability and accessibility. We are requesting the UX team to evaluate the current interface and provide mockup proposals for an improved navigation and layout design.

Background

The console today exposes the following top-level sections via a horizontal nav bar:

• Dashboard — Job processing overview with KPI cards, queue distribution, failure tracking, and throughput charts
• Jobs — Individual job browsing, filtering, and detail inspection
• Batches — Grouped processing run timelines with cost estimation, bulk actions, and infrastructure views
• Help — Full user tutorial covering all panels and interactions

As MAAP continues active development, additional features (e.g. data management, algorithm registry, workspace management, notifications, admin tools) will likely be added to the console. The current flat top-bar pattern will quickly become overcrowded and harder to navigate.

Problem Statement

1. Navigation does not scale — A horizontal top bar is limited in how many items it can accommodate before becoming visually cluttered or requiring dropdowns/overflow menus.
2. No hierarchical structure — There is no way to express sub-sections or groupings (e.g. "Processing" containing Jobs and Batches), which will make feature organization harder as the console grows.
3. No global search or quick-access — Users have no way to quickly jump to a specific section, job, or batch without manually navigating through pages.
4. Accessibility compliance — The current interface has not been evaluated against NASA or federal accessibility standards (Section 508 / WCAG 2.1 AA). Navigation patterns, color contrast (noted use of red/green for status), and keyboard navigability should be reviewed.

Request

We are requesting the UX team to provide mockup proposals (wireframes or high-fidelity designs) for a redesigned MAAP Console navigation and layout that addresses the above concerns. Proposals should consider:

• Left-hand sidebar navigation as a primary pattern, consistent with modern console interfaces (e.g. Google Cloud Console, AWS Console, Vercel) — this provides hierarchical grouping, collapsibility, and room for future growth
• Scalable information architecture — a structure that can accommodate future feature additions without requiring a full redesign (e.g. grouped sections, collapsible categories)
• Global search or command palette — a mechanism for users to quickly find sections, jobs, or batches without deep navigation
• NASA / Section 508 accessibility compliance — layouts and color usage should meet federal accessibility standards; in particular, status indicators that currently rely solely on color should include supplementary text or icons

Constraints & Context

• The console serves both NASA and ESA users (joint NASA-ESA collaboration)
• Users are primarily scientists running large-scale geospatial processing jobs; the interface should prioritize efficiency for returning users over onboarding friction
• The platform is in active development; the navigation structure should anticipate growth without locking in a rigid hierarchy too early

Deliverables Requested

• Mockup(s) for a redesigned navigation layout (sidebar-based or alternative proposal with rationale)
• Guidance for developers on how to add new features to the console — where to place links in the navigation, and UX best practices for new feature pages
• Notes on accessibility considerations and recommended remediation for current patterns

References

• Current console screenshots: see attached (dashboard, jobs, batches, help views)

• MAAP Project Documentation

[wildintellect]

@freitagb @brianna-corremonte @abarciauskas-bgse here's the outline of the ask we'd like to get some Designer/Front-end help with. We also have a video available of first impressions with some power users.

[wildintellect]

@riverma can you repost the images, they seem to be linked to a private repo people can't see if they're not part of the Org.

[wildintellect]

@riverma I fixed the images
tagging @fannycc who will likely pick this up or provide more guidance.
cc: @jjfrench

[ifsimicoded]

This is what I see as on @fannycc plate based on PI planning and a quick async talk.

• Reusable components / Reusable plugin geo components (~0.2 FTE)
• Disasters viz (0.25 FTE)
• AQ portal (~0.5 FTE --- it's listed as 1 FTE on slides, but this seemed high also @Fausto has pitched staying on longer on Dashboard to assist Fanny)
• EIE (? it's combined w/ Gjore as 1.5FTE)
• EarthRise (FTE?)

I don't think this is feasible? even if Fanny drops AQ and with the timezone requirement.
Edit: I think it makes sense to follow up with @LanesGood