[EPIC] Edit Content Screen: polish and parity

Abierto
#38,651 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
frontend

Línea de trabajo

Start with the linked child issues grouped by PR, especially the history, validation, image editor, and field parity issues; this epic does not name implementation files or tests. Read the referenced child issues and their linked design or spec first. Done means the scoped work is closed in its grouped PRs and the listed editor behaviors and product decisions meet the desired outcomes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

dotCMS: New Edit Contentlet Epic Team : Scout
Description

Second child EPIC of #38634. It collects the visible improvements and the remaining feature gaps against the legacy editor that do not block adoption: UX feedback batches from the team and Professional Services, the History sidebar redesign and its behaviour bugs, image editor ergonomics, field-level parity (categories sort, page template, tag storage) and the product decisions that were raised in #feat-edit-content but never filed.

Anything that loses edits, blocks a save or makes a customer turn the editor off belongs to the adoption EPIC #38642, not here. Refactors belong to the third EPIC.

Work is grouped by the PR that closes it.

Desired Outcome
  • The screen matches the approved design: header, sidebar sections, state chip, Preview placement, dialogs that close with ESC, no unexpected scrolling.
  • The History tab follows the new design, a historical version is read-only, Preview works, the timeline is ordered with the draft first and compare navigation works.
  • The image editor commits dimensions on blur, links width and height by default, offers SmartCrop and works on small screens.
  • Categories sort, the original template on Page content and Tag Storage behave as in the legacy editor.
  • Validation errors stay where the author is looking and the error banner clears after the next action.
  • The two open product decisions (working vs live on image save, permission behaviour) are recorded and documented.
Target Personas
  • Developer teams
  • Content teams
  • DevOps teams
  • System administrators (dotCMS)
Links
Scope, grouped by the PR that closes it

PR 8 · visual polish, one batch

  • #37958 header divider, date picker width, drag handle, copy button, icons
  • #38036 sidebar titles and sections, comments order, image preview, relationship picker site
  • #38056 state chip next to the title, Preview below the actions, Title / All Fields search
  • #38489 breadcrumb replaced when opening from Content Search
  • #35267 Permissions and Rules dialogs ignore ESC
  • #36454 page auto-scrolls to the JSON field
  • #38665 remove the revert-to-old-editor banner (always redirects to Content Drive)
  • #38666 sidebar dialogs open centred and jump when an action runs
  • #38668 sidebar scroll carries the tabs away

PR 6 · history sidebar

  • #38033 redesign the History tab (Versions and Push Publish)
  • #38652 a historical version is editable instead of read-only
  • #38653 the Preview action on a version does nothing
  • #38654 timeline order and compare navigation

PR 2b · validation UX

  • #38655 validation errors jump between tabs and the error banner never clears
  • #38667 language indicator updates only after save when creating a translation

PR 4b · image editor ergonomics

  • #38019 width and height inputs apply on every keystroke, not linked (spec PR #38030)
  • #36613 action buttons on small screens
  • #36315 SmartCrop control (own PR)
  • #38656 decide working vs live when saving an edited image or file asset

PR 9 · field parity

  • #34468 categories sort
  • #34654 original template on Page content
  • #37789 Tag Storage field shows the wrong value

Side-panel host · Content Drive (feedback from the #38303 QA, out of that PR's scope)

  • #38669 decide whether Content Drive keeps its layout under the panel like the legacy search and the UVE
  • #38670 Content Drive reloads the listing when the panel closes with changes discarded

Docs

  • #38657 document how permissions drive what the editor shows

Linked, not attached

  • #38303 side panel everywhere: Product-owned.
  • #38001, #38002 Edit Source: Content Drive.
Lenguaje dominante
Java
Estrellas
972
Forks
493
Merge medio
2 d 12 h
PR fusionados (30 d)
228

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de dotCMS/core

Todos los issues de dotCMS/core

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.