Files
ss-tools/specs/015-frontend-nav-redesign/spec.md
2026-01-26 20:58:38 +03:00

6.1 KiB

Feature Specification: Frontend Navigation Redesign

Feature Branch: 015-frontend-nav-redesign Created: 2026-01-26 Status: Draft Input: User description: "Я хочу провести редизайн фронта в части навигации. 1. Удалить Dataset Search (из Navbar и дашборда), Deployment Environments 2. Вкладку Tasks оставить для просмотра всех задач - убрать оттуда кнопку Run backup 3. Должен быть полноценный компонент бэкапов, как мы разрабатывали в 009-backup-scheduler. Доступ - из дашборда главного 4. Перенести ссылку на Dataset mapper из Navbar на дашборд 5. Перенести ссылку на Storage manager на дашборд Общая логика - на дашборде должны быть ссылки на полноценные инструменты, навбар - для настроек и общей Tasks"

Clarifications

Session 2026-01-26

  • Q: Do I need to build the Backup Management UI from scratch? → A: Yes, create the UI for backup using data from task 009-backup-scheduler.

User Scenarios & Testing (mandatory)

User Story 1 - Centralized Tool Access via Dashboard (Priority: P1)

As a user, I want to access all main tools (Backups, Mapper, Storage) from the main Dashboard so that I have a central hub for operations.

Why this priority: This is the core of the redesign, shifting the navigation paradigm to a dashboard-centric model for tools.

Independent Test: Can be tested by verifying the Dashboard contains links/cards for Backups, Mapper, and Storage, and that clicking them navigates to the correct full-page tools.

Acceptance Scenarios:

  1. Given I am on the main Dashboard, When I look at the available tools, Then I see options for "Backup Manager", "Dataset Mapper", and "Storage Manager".
  2. Given I am on the Dashboard, When I click "Backup Manager", Then I am taken to the full Backup management interface.
  3. Given I am on the Dashboard, When I click "Dataset Mapper", Then I am taken to the Mapper tool.
  4. Given I am on the Dashboard, When I click "Storage Manager", Then I am taken to the Storage tool.

User Story 2 - Simplified Navigation Bar (Priority: P1)

As a user, I want a clean Navbar containing only global context items (Tasks, Settings) so that the interface is less cluttered and navigation is distinct from tool usage.

Why this priority: Enforces the separation of concerns between "Global Status/Settings" (Navbar) and "Operational Tools" (Dashboard).

Independent Test: Can be tested by inspecting the Navbar across the application to ensure removed items (Search, Mapper, Environments) are gone and only Tasks and Settings remain.

Acceptance Scenarios:

  1. Given I am on any page, When I view the Navbar, Then I do NOT see links for "Dataset Search", "Dataset Mapper", or "Deployment Environments".
  2. Given I am on any page, When I view the Navbar, Then I see links for "Tasks" and "Settings".
  3. Given I am on the Tasks page, When I look for the "Run backup" button, Then it is NOT present (as it belongs in the Backup tool).

User Story 3 - Deprecation of Unused Features (Priority: P2)

As a user, I want removed features (Dataset Search, Deployment Environments) to be inaccessible so that I don't use deprecated workflows.

Why this priority: Cleans up the UI and prevents confusion with features that are being removed or hidden.

Independent Test: Verify that UI elements for Dataset Search and Deployment Environments are removed from both Navbar and Dashboard.

Acceptance Scenarios:

  1. Given I am on the Dashboard, When I look for "Dataset Search", Then it is not visible.
  2. Given I am on the Dashboard or Navbar, When I look for "Deployment Environments", Then it is not visible.

Edge Cases

  • Direct URL Access: If a user attempts to access the URL of a removed page (e.g., /search or /environments) via bookmark or history, they should be redirected to the Dashboard or shown a 404 page (standard app behavior).
  • Mobile View: The simplified Navbar must remain responsive; with fewer items, it should likely avoid collapsing into a hamburger menu unless necessary on very small screens.

Assumptions

  • The backend logic and UI components for the "Backup Scheduler" (Feature 009) are available and ready to be integrated into the main Dashboard view.
  • Existing tools (Dataset Mapper, Storage Manager) function independently of the Navbar context and will work correctly when accessed via the Dashboard.

Requirements (mandatory)

Functional Requirements

  • FR-001: System MUST display "Dataset Mapper" entry point on the main Dashboard.
  • FR-002: System MUST display "Storage Manager" entry point on the main Dashboard.
  • FR-003: System MUST display "Backup Scheduler" (or similar name) entry point on the main Dashboard.
  • FR-004: System MUST provide access to the full Backup Management component (newly created based on feature 009 data) via the Dashboard link.
  • FR-005: Navbar MUST NOT contain links to "Dataset Search", "Dataset Mapper", or "Deployment Environments".
  • FR-006: Dashboard MUST NOT contain "Dataset Search" widget or link.
  • FR-007: Tasks page MUST NOT show the "Run backup" button (backup initiation moves to Backup tool).
  • FR-008: Navbar MUST retain "Tasks" and "Settings" links.

Key Entities

  • Dashboard: The main landing page serving as the registry for tools.
  • Navbar: The persistent top navigation for global application state/config.

Success Criteria (mandatory)

Measurable Outcomes

  • SC-001: Users can navigate to Dataset Mapper, Storage Manager, and Backup Manager within 1 click from the Dashboard.
  • SC-002: Navbar contains strictly 0 links to operational tools (Mapper, Search, Storage), containing only Tasks and Settings.
  • SC-003: "Run backup" action is successfully performed via the new Dashboard -> Backup route.