Skip to content

Redesign the 'View/Edit Knowledge Card' page

Edouard Legoupil requested to merge feature/redesign-knowledge-card-page into main_dev

Created by: Edouard-Legoupil

This commit redesigns the 'View/Edit Knowledge Card' page to be more compact and aligned with the rest of the app.

The changes include:

  • A new card-based design for the references section, with add, edit, and delete functionality.

  • The generated content section is now responsive.

  • The 'Regenerate' button has been removed from each section.

  • The edit box for a section is now full-width when editing.

  • A history snapshot is now recorded whenever the knowledge card content is regenerated or a section is edited.

  • Does my code meet the quality standards for releasing packages?

  • Does the reviewer have all the information to validate the features/issues without too much research?

  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports