dotCMS / dotCMS/core

[EPIC] Chrome Redesign

Open
#32,010 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

dotCMS: Chrome Redesign Team : Falcon Type : New Functionality
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Big Picture Vision

Redesign the chrome so that it has the appropriate visual hierarchy, it looks and behaves consistently across the pages, it provides a home for certain elements in the UI, and state management works as expected.

User Story

As a user I want my navigation and back stack to work as expected so that I can move among the pages in the application without hitting any unresolved URLs or losing track of where I have been no matter if I press back in the browser or in the application.

As a user I want the chrome of my application to be responsive to my direction and look and feel the same everywhere in the app so that I can transfer my knowledge and expectation of how it works to all the pages in the system.

##PROBLEM
Our chrome is visually dated, doesn’t have a good visual hierarchy, and suffers from inconsistencies in design elements and interaction patterns across different sections, leading to a confusing user experience and hindering usability.
State management is not working as it should, the back stack is not working properly.

Links As Appropriate

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Chrome Redesign epic and review the linked Figma design, kickoff deck, and EPIC folder. The work is done when the chrome has consistent visual hierarchy and behavior across pages, responsive navigation and back-stack state work in both browser and application controls, and unresolved URLs are avoided.

Written by the indexing model from the issue text.

Assessment

Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.