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

fix: updated donation progress with heading #54377

Merged
merged 9 commits into from May 3, 2024

Conversation

JeevaRamanathan
Copy link
Contributor

Checklist:

Closes #54156

Updated Block Progress Bar with heading
image

@JeevaRamanathan JeevaRamanathan requested a review from a team as a code owner April 12, 2024 14:57
@github-actions github-actions bot added platform: learn UI side of the client application that needs familiarity with React, Gatsby etc. scope: i18n language translation/internationalization. Often combined with language type label labels Apr 12, 2024
@lasjorg
Copy link
Contributor

lasjorg commented Apr 15, 2024

I haven't checked, but are we sure .progress-bar-percent isn't used elsewhere?

I'm not saying the linear-gradient with the animation is working well if it is used elsewhere, but changing it for all instances might not be the correct thing to do here.

Maybe we should make a new class or a modifier class (so it can exist with and without the gradient).

@JeevaRamanathan
Copy link
Contributor Author

Hi @lasjorg,
The .progress-bar-percent is descendant of an element with the class annual-donation-alert in this file which had the background-image for the animation

.annual-donation-alert .progress-bar-percent {

Additionally, in the other occurrence in a different file, the background-image property is also not present in this section

.progress-bar-percent {
height: 10px;
overflow: hidden;
position: relative;
background-color: var(--primary-color);
transition: width 0ms linear;
}

Therefore, I believe it would not have an impact. But I would appreciate your input on this.

@lasjorg
Copy link
Contributor

lasjorg commented Apr 16, 2024

If we remove the gradient, I don't think we need the animation as well.


We didn't get any feedback yet in the issue from one of the maintainers, and I realize this is opinionated and gets into the weeds.

Personally, I'm not crazy about the component having different styles depending on its placement. It feels like a side effect, and it's not very transparent to the user of the component. I would want to know the component styles by looking at the component or any variations of the component to be explicit, and not just based on its placement in the DOM.

@JeevaRamanathan
Copy link
Contributor Author

Oops! Somehow I have missed that, animation has been removed now.


Ok, let's see if we hear any feedback from maintainers

@lasjorg
Copy link
Contributor

lasjorg commented Apr 17, 2024

BTW, how does it look with the paragraph element?

I didn't check, but I would assume the element needs some styles to be larger and have more weight?

Copy link
Member

@naomi-lgbt naomi-lgbt left a comment

Choose a reason for hiding this comment

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

image

The new text will need a specific colour set so it does not become illegible in night mode.

@naomi-lgbt naomi-lgbt added the status: waiting update To be applied to PR if a maintainer/reviewer has left a feedback and follow up is needed from OP label Apr 25, 2024
@JeevaRamanathan
Copy link
Contributor Author

@naomi-lgbt, it has been updated with a specific color, and I hope the translation text, which is showing as "learn.donation-heading," will map with its corresponding value once it's live.

@naomi-lgbt
Copy link
Member

which is showing as "learn.donation-heading," will map with its corresponding value once it's live.

Yeah, that only shows because I was too lazy to clean the local files when I was switching branches.

@naomi-lgbt naomi-lgbt added status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. and removed status: waiting update To be applied to PR if a maintainer/reviewer has left a feedback and follow up is needed from OP labels Apr 25, 2024
Copy link
Member

@moT01 moT01 left a comment

Choose a reason for hiding this comment

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

LGTM 🎉

Hey @ahmaxed, do you mind taking a look at this redesign before we merge?

@ahmaxed ahmaxed self-assigned this Apr 26, 2024
@ahmaxed
Copy link
Member

ahmaxed commented Apr 27, 2024

This is the final state. Removed the hr as requested. Adding an animation would be nice.

Screenshot 2024-04-27 at 9 03 44 PM

@ahmaxed ahmaxed enabled auto-merge (squash) April 27, 2024 18:07
@JeevaRamanathan
Copy link
Contributor Author

Hi @ahmaxed, I see auto-merge is enabled but could you kindly clarify the conversation that needs resolution and is currently blocking the merge?

@ahmaxed ahmaxed merged commit c548323 into freeCodeCamp:main May 3, 2024
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform: learn UI side of the client application that needs familiarity with React, Gatsby etc. scope: i18n language translation/internationalization. Often combined with language type label status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Donation progress bar UI/UX
6 participants