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

791: Campaign details page #87744

Merged
merged 43 commits into from
Feb 28, 2024
Merged

791: Campaign details page #87744

merged 43 commits into from
Feb 28, 2024

Conversation

ernestoSk13
Copy link
Contributor

Related to #

Proposed Changes

  • In this PR I'm working with the new campaign details UI. The UI should comply to the one shown in Figma.
    Screenshot 2024-02-21 at 6 54 07 p m

Testing Instructions

  • Login to any blog that has campaigns on calypso and go to one of them
  • Verify the different UI elements and compare it to Figma
  • Try the same but with a Woo product (flag: is_running_in_woo_site).

NOTE: Some elements like the CTA Button or the Weekly total row, are not included in this PR. Also the Preview button is still unclear where should we place it

#64626

Screenshots

WPCom blog
Screenshot 2024-02-21 at 6 57 00 p m
Screenshot 2024-02-21 at 6 57 07 p m

Woo
Screenshot 2024-02-21 at 6 58 03 p m
Screenshot 2024-02-21 at 6 57 57 p m
Screenshot 2024-02-21 at 6 57 51 p m
Screenshot 2024-02-21 at 6 57 43 p m

Pre-merge Checklist

  • Has the general commit checklist been followed? (PCYsg-hS-p2)
  • Have you written new tests for your changes?
  • Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
  • Have you checked for TypeScript, React or other console errors?
  • Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
  • Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

@matticbot matticbot added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels Feb 22, 2024
@sbarbosa sbarbosa marked this pull request as ready for review February 23, 2024 13:21
Copy link
Contributor

@sbarbosa sbarbosa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @ernestoSk13, I did another review/test and found some other details in the page (I added some comments for those).

In some medium screens, the header shows both of the buttons, but they are not aligned to the right, and have no gap between them
Screenshot 2024-02-23 at 11 09 56

client/components/breadcrumb/index.tsx Outdated Show resolved Hide resolved
const overallSpendingFormatted = `$${ formatCents( total_budget_used || 0 ) }`;
const deliveryEstimateFormatted = getCampaignEstimatedImpressions( display_delivery_estimate );
const campaignTitleFormatted = title || __( 'Untitled' );
const campaignCreatedFormatted = moment.utc( created_at ).format( 'MMMM DD, YYYY' );
const devicesListFormatted = devicesList ? `${ devicesList }` : __( 'All' );
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is currently a valid target option, we shouldn't remove it from the page. I think it's OK to put in above or under Languages.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @ernestoSk13, with the last update we lose this targeting option. It is still a valid option, I think we need to include it in the final details.

client/my-sites/promote-post-i2/utils/index.ts Outdated Show resolved Hide resolved
@therocket-gr
Copy link
Contributor

some comments from me as well

not sure if this is ok and whether we should just have a breakpoint so that the labels should display in mobile one on top of the other (rather than just allowing the text to flow to different lines)

Screenshot 2024-02-26 at 15 57 36

same as below.. not sure if this is ok .. looks like the text on the left in relation to the button is not aligned or something is off

Screenshot 2024-02-26 at 15 59 07

@ernestoSk13
Copy link
Contributor Author

hi @sbarbosa @therocket-gr I've fixed this behavior and another minor UI issues :) thanks for your review

@ernestoSk13
Copy link
Contributor Author

hi @sbarbosa I've cleaned the scss and the index file. The mobile views should be working now too :)

Copy link
Contributor

@sbarbosa sbarbosa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work @ernestoSk13, the page adapts very well to the different screens now.
Great job!

I only find a comment related to the device target list. With the last changes, we lose that data, and still remains a valid targeting option in the Create campaign widget.

const overallSpendingFormatted = `$${ formatCents( total_budget_used || 0 ) }`;
const deliveryEstimateFormatted = getCampaignEstimatedImpressions( display_delivery_estimate );
const campaignTitleFormatted = title || __( 'Untitled' );
const campaignCreatedFormatted = moment.utc( created_at ).format( 'MMMM DD, YYYY' );
const devicesListFormatted = devicesList ? `${ devicesList }` : __( 'All' );
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @ernestoSk13, with the last update we lose this targeting option. It is still a valid option, I think we need to include it in the final details.

Copy link
Contributor

@therocket-gr therocket-gr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

everything seems ok to me now (i will approve even though i see a comment by @sbarbosa.. )
nice work

Copy link
Contributor

@sbarbosa sbarbosa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the changes! The PR looks good 👍

@ernestoSk13 ernestoSk13 merged commit 437fd01 into trunk Feb 28, 2024
11 checks passed
@ernestoSk13 ernestoSk13 deleted the add/blaze-woo-express-791 branch February 28, 2024 16:18
@github-actions github-actions bot removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Feb 28, 2024
@a8ci18n
Copy link

a8ci18n commented Feb 28, 2024

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/11500566

Some locales (Hebrew, Japanese) have been temporarily machine-translated due to translator availability. All other translations are usually ready within a few days. Untranslated and machine-translated strings will be sent for translation next Monday and are expected to be completed by the following Friday.

Thank you @ernestoSk13 for including a screenshot in the description! This is really helpful for our translators.

@a8ci18n
Copy link

a8ci18n commented Mar 4, 2024

Translation for this Pull Request has now been finished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants