Skip to content

Jetpack Section: Optimize My Site Menu Items#13969

Merged
ashiagr merged 5 commits intodevelopfrom
issue/13629-optimize-my-site-menu-items
Feb 5, 2021
Merged

Jetpack Section: Optimize My Site Menu Items#13969
ashiagr merged 5 commits intodevelopfrom
issue/13629-optimize-my-site-menu-items

Conversation

@ParaskP7
Copy link
Copy Markdown
Contributor

@ParaskP7 ParaskP7 commented Feb 4, 2021

Parent #13629

This PR updates the following for the My Site screen menu items:

  • The Activity string to Activity log.
  • The Activity icon to ic_gridicons_clipboard_white_24dp.
  • The Backup icon to ic_gridicons_cloud_upload_white_24dp.
  • The Scan icon to ic_baseline_security_white_24dp.
Light Theme Dark Theme
before after

To test:

  • Launch the app and go to My Site tab.
  • Make sure that the above mentioned string and icon changes are as described (for both the Light and Dark theme).
  • Go to My Site -> Toolbar Avatar -> App Settings -> Test feature configuration.
  • Enable MySiteImprovementsFeatureConfig, scroll down and click the RESTART THE APP button.
  • Make sure that the above mentioned string and icon changes are as described (for both the Light and Dark theme).

PR submission checklist:

  • I have considered adding unit tests where possible.
  • I have considered adding accessibility improvements for my changes.
  • I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

@ParaskP7 ParaskP7 added Jetpack [Status] Needs Design Review A designer needs to sign off on the implemented design. /My site Jetpack Mobile labels Feb 4, 2021
@ParaskP7 ParaskP7 added this to the 16.7 milestone Feb 4, 2021
@ParaskP7 ParaskP7 self-assigned this Feb 4, 2021
@peril-wordpress-mobile
Copy link
Copy Markdown

You can trigger optional UI/connected tests for these changes by visiting CircleCI here.

@ParaskP7 ParaskP7 mentioned this pull request Feb 4, 2021
40 tasks
@peril-wordpress-mobile
Copy link
Copy Markdown

You can test the changes on this Pull Request by downloading the APK here.

@ashiagr ashiagr self-assigned this Feb 5, 2021
Copy link
Copy Markdown
Contributor

@ashiagr ashiagr left a comment

Choose a reason for hiding this comment

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

Looks great @ParaskP7!

I just have one comment:

We don’t usually add _gridicons to icon names, it might be nice to remove it from these icons for consistency.

ic_gridicons_clipboard_white_24dp
ic_gridicons_cloud_upload_white_24dp

@ParaskP7
Copy link
Copy Markdown
Contributor Author

ParaskP7 commented Feb 5, 2021

👋 @ashiagr !

We don’t usually add _gridicons to icon names, it might be nice to remove it from these icons for consistency.

Thank you for this comment, I was actually wanted to discuss on that! 🙏

I left the gridicons word on purpose thinking that this is what we want, just to differentiate our gridicons from the rest of them. I got to that conclusion since I saw other icons like that, which was containing the gridicons wording within them. From your comment, it seems that we are not interested in that.

Suggestion (💡): After update the icons in this PR to remove the gridicons word, should I go forward and do the same with all the other icons that contain the gridicons word in them, just to avoid any future suchlike discussion?

Cc: @malinajirka to share his thoughts as well (since he might be more aware of the history).

@ashiagr
Copy link
Copy Markdown
Contributor

ashiagr commented Feb 5, 2021

I left the gridicons word on purpose thinking that this is what we want, just to differentiate our gridicons from the rest of them. I got to that conclusion since I saw other icons like that, which was containing the gridicons wording within them. From your comment, it seems that we are not interested in that.

I see that out of several icons, there's one icon ic_gridicons_checkmark_circle in the main project and 3-4 icons in the separate library modules with _gridicons in the name. I think we're using gridicons for most of our icons and usually do not append _gridicons to the name (e.g. ic_cloud_white_24dp, ic_cog_white_24dp). Either we append _gridicons to all existing such icons or we remove from where they're used, we can go either ways! Or may be not worry about it 😄.

Cc: @malinajirka to share his thoughts as well (since he might be more aware of the history).

Agree, let's wait for inputs from @malinajirka :).

@malinajirka
Copy link
Copy Markdown
Contributor

malinajirka commented Feb 5, 2021

As @ashiagr mentioned, we usually do not include "gridicon" in the name of the icon. I think removing it from all our resources would be good (not necessary). Having said that, watch out that icons in the LoginLib might be used in Woo (I think there is just one).

@ParaskP7
Copy link
Copy Markdown
Contributor Author

ParaskP7 commented Feb 5, 2021

I see that out of several icons, there's one icon ic_gridicons_checkmark_circle in the main project and 3-4 icons in the separate library modules with _gridicons in the name. I think we're using gridicons for most of our icons and usually do not append _gridicons to the name (e.g. ic_cloud_white_24dp, ic_cog_white_24dp). Either we append _gridicons to all existing such icons or we remove from where they're used, we can go either ways!

Yeap, not sure about it either, since I was seeing the gridicons word being used, I initially thought that we want that there in order to easily much the file name with that on the gridicons repo. Thus, I didn't want to delete this information. However, I am really okay with anything we decide, and wanted to raise the question here so I know what to do in the future without further thinking about it.

Or may be not worry about it 😄.

😄 That is true! Either way, it is a small change and we will end up merging to develop today, so I am not stressed about it too much. Also, since we are waiting for @osullivanchris to do the design review on them, we have some additional time to decide on that. 😄

@ashiagr
Copy link
Copy Markdown
Contributor

ashiagr commented Feb 5, 2021

it is a small change and we will end up merging to develop today,

Right, let's merge it 🚀 🚀. We can discuss it later 👍.

@ashiagr ashiagr merged commit c1d92de into develop Feb 5, 2021
@ashiagr ashiagr deleted the issue/13629-optimize-my-site-menu-items branch February 5, 2021 08:10
@ParaskP7
Copy link
Copy Markdown
Contributor Author

ParaskP7 commented Feb 5, 2021

👋 @osullivanchris !

This PR was merged to develop without getting your approval first, this is my fault as I should have added specific merge instructions to not merge it before it gets a design approval.

Would you mind do a design review anyway and let us know if you find anything that need correction and I'll make sure to create another PR with those right away, then link that PR to this one.

Many thanks and apologies for any confusion! 🙏

@osullivanchris
Copy link
Copy Markdown

This PR was merged to develop without getting your approval first, this is my fault as I should have added specific merge instructions to not merge it before it gets a design approval.

😄 no problem. The new icons look good.

One thing that I should have thought of sooner too, I think it should be "Jetpack Settings" and "Activity Log" with title case. As when I look down the rest of the menu that's what we are using (Blog Posts, Site Pages).

@ParaskP7
Copy link
Copy Markdown
Contributor Author

ParaskP7 commented Feb 5, 2021

😄 no problem. The new icons look good.

🙏

One thing that I should have thought of sooner too, I think it should be "Jetpack Settings" and "Activity Log" with title case. As when I look down the rest of the menu that's what we are using (Blog Posts, Site Pages).

Thanks for the review @osullivanchris !

Yes, this makes sense. I'll prepare another PR by the end of the day with that exact change and let you know. 💪

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Jetpack /My site [Status] Needs Design Review A designer needs to sign off on the implemented design.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants