Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CA Search: Apply updated Design #30427

Closed
Tracked by #30178
hmoreras opened this issue Oct 22, 2024 · 6 comments · Fixed by #30492
Closed
Tracked by #30178

CA Search: Apply updated Design #30427

hmoreras opened this issue Oct 22, 2024 · 6 comments · Fixed by #30492

Comments

@hmoreras
Copy link
Contributor

hmoreras commented Oct 22, 2024

Parent Issue

#30178

User Story

As a developer, I want to implement the UI updates for the Content Analytics portlet, following the design team's specifications in the provided Figma file, so that the UI is consistent with the new design.

Acceptance Criteria

  1. Update the layout and styling of the Content Analytics portlet according to the Figma design.
  2. Ensure that the fonts, colors, and spacing match the Figma file.
  3. Implement any new UI components or interactions specified in the design.

Proposed Objective

UI/UX Improvements

Proposed Priority

Priority 2 - Important

External Links

Assumptions & Initiation Needs

  • The Figma file contains all required design assets and specifications.
  • The development environment is ready for updating the Content Analytics portlet.

Quality Assurance Notes & Workarounds

  • Ensure no performance degradation due to new styles or components.

Sub-Tasks & Estimates

No response

@hmoreras
Copy link
Contributor Author

QA Note:

The design updates include the use of p-splitter and validation of json format before send the request.

image image

Details that we are aware:

  • Help button still pending will be worked in other card.
  • Dropdown to support both queries not needed. for now only the CUBE query will be supported.

Example of Cube Query used:

{ "dimensions": [ "request.whatAmI", "request.url" ], "order": { "request.count": "desc" }, "measures": [ "request.count" ], "timeDimensions": [ { "dimension": "request.createdAt" } ], "filters": [ { "member": "request.url", "operator": "equals", "values": [ "/" ] }, { "member": "request.whatAmI", "operator": "equals", "values": [ "PAGE" ] } ] }

Copy link

github-merge-queue bot pushed a commit that referenced this issue Oct 29, 2024
#30492)

### Proposed Changes
* Apply new design updates, using the `p-splitter`
* Json format validation before be able to make the request




### Additional Info
** any additional useful context or info **

### Screenshots

<img width="1323" alt="image"
src="https://github.com/user-attachments/assets/daaed8ce-7285-4aa5-88ad-894a2a520df3">

<img width="1301" alt="image"
src="https://github.com/user-attachments/assets/c62ce545-4ddb-417e-9643-e4e1434db905">

<img width="1359" alt="image"
src="https://github.com/user-attachments/assets/edb41833-aebf-471f-aba9-cea22c9c7d0e">
@github-project-automation github-project-automation bot moved this from In Review to Internal QA in dotCMS - Product Planning Oct 29, 2024
@dsilvam dsilvam assigned dsilvam and unassigned hmoreras Oct 31, 2024
@dsilvam
Copy link
Contributor

dsilvam commented Oct 31, 2024

Passed IQA:

  • Validating JSON and preventing to execute the query when the JSON is invalid
  • Fetching results properly
  • Same as designed
Screenshot 2024-10-31 at 2 53 19 PM Screenshot 2024-10-31 at 3 09 12 PM

Had requested changes in the Dialog when the Analytics app is not configured but we'll have a wall instead, so this Dialog will go away:

Screenshot 2024-10-31 at 2 53 56 PM

@john-thomas-dotcms
Copy link
Contributor

Suggested title: Analytics is Not Configured

@dsilvam dsilvam moved this from In Progress to QA - Backlog in dotCMS - Product Planning Oct 31, 2024
@hmoreras
Copy link
Contributor Author

hmoreras commented Nov 1, 2024

configration errores are being worked in other card, we wil use a "wall" #30233

@josemejias11
Copy link
Contributor

Approved: Tested on trunk_7408571, Docker, macOS 14.5, FF v126.0.1

@josemejias11 josemejias11 moved this from QA - In Progress to Done in dotCMS - Product Planning Nov 1, 2024
dsolistorres pushed a commit that referenced this issue Nov 5, 2024
#30492)

### Proposed Changes
* Apply new design updates, using the `p-splitter`
* Json format validation before be able to make the request




### Additional Info
** any additional useful context or info **

### Screenshots

<img width="1323" alt="image"
src="https://github.com/user-attachments/assets/daaed8ce-7285-4aa5-88ad-894a2a520df3">

<img width="1301" alt="image"
src="https://github.com/user-attachments/assets/c62ce545-4ddb-417e-9643-e4e1434db905">

<img width="1359" alt="image"
src="https://github.com/user-attachments/assets/edb41833-aebf-471f-aba9-cea22c9c7d0e">
spbolton pushed a commit that referenced this issue Nov 11, 2024
#30492)

### Proposed Changes
* Apply new design updates, using the `p-splitter`
* Json format validation before be able to make the request




### Additional Info
** any additional useful context or info **

### Screenshots

<img width="1323" alt="image"
src="https://github.com/user-attachments/assets/daaed8ce-7285-4aa5-88ad-894a2a520df3">

<img width="1301" alt="image"
src="https://github.com/user-attachments/assets/c62ce545-4ddb-417e-9643-e4e1434db905">

<img width="1359" alt="image"
src="https://github.com/user-attachments/assets/edb41833-aebf-471f-aba9-cea22c9c7d0e">
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment