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: Feedback Landing page #104

Open
wants to merge 6 commits into
base: testnet
Choose a base branch
from

Conversation

Benjtalkshow
Copy link

Closes #101
For the task 1 "Changing the size of the header banner", i used 700 x 700 because i noticed that 500x500 was still small.

Copy link

vercel bot commented Jan 29, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
starknet-id ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 30, 2025 3:46pm

Copy link

vercel bot commented Jan 29, 2025

@Benjtalkshow is attempting to deploy a commit to the LFG Labs Team on Vercel.

A member of the Team first needs to authorize it.

@@ -5,8 +5,10 @@ const HeaderBanner: FunctionComponent = () => {
return (
<img
alt="Header banner"
src="/visuals/home/headerBanner.webp"
src="/visuals/home/headerImage.png"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please use png format, not webp.
In addition, the image doesn't load, please test your code
image

Copy link
Author

Choose a reason for hiding this comment

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

@Marchand-Nicolas
Do you mean i should use webp format instead of png? Because what i used is png format.
Additionally, i am wondering why the image is not loading from your end because it loads properly from my localhost and i tested it properly before pushing.

Copy link
Collaborator

Choose a reason for hiding this comment

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

@Benjtalkshow
Yes, you should use webp, not png, sorry, just saw I inverted in my comment!
For the image that doesn't load in production but loads in local, there can be two options:

  • Either one letter should/shouldn't be uppercase in the image path. From my experience, the links are only case sensitive in production.
  • Or, you use the CDNImg component. If so, you can replace it by the Image component from next/image

Copy link
Author

Choose a reason for hiding this comment

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

@Marchand-Nicolas ,
I have fixed the headerBanner. But i noticed argent wallet, starkscan and braavos icons arent displaying too.

Copy link
Collaborator

Choose a reason for hiding this comment

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

@Marchand-Nicolas , I have fixed the headerBanner. But i noticed argent wallet, starkscan and braavos icons arent displaying too.

Ah, where do you see t-it ? Can you send me a screenshot please @Benjtalkshow

Copy link
Author

Choose a reason for hiding this comment

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

@Marchand-Nicolas Marchand-Nicolas added the ❌ Change request Change requested from reviewer label Jan 29, 2025
Copy link
Collaborator

@Marchand-Nicolas Marchand-Nicolas left a comment

Choose a reason for hiding this comment

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

Too much space around the header image on mobile. Please use the same margins as on figma
Screenshot 2025-01-30 at 8 43 16 AM

Same here, there is too much space on mobile
Screenshot 2025-01-30 at 8 46 22 AM

@@ -5,8 +5,10 @@ const HeaderBanner: FunctionComponent = () => {
return (
<img
alt="Header banner"
src="/visuals/home/headerBanner.webp"
Copy link
Collaborator

Choose a reason for hiding this comment

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

If you add a new headerImage.webp file, then delete the headerBanner.webp file as it's not used anymore

@Benjtalkshow
Copy link
Author

@Marchand-Nicolas
Did the logo images load from your end?

@Marchand-Nicolas
Copy link
Collaborator

@Marchand-Nicolas Did the logo images load from your end?

#104 (comment)

@Marchand-Nicolas
Copy link
Collaborator

Hello @Benjtalkshow I think it loads in production and not locally because the files doesn't exist (with that exact names), but the contributor used the CDNImg component, which makes it working in prod (because it uses the cached assets).
Can you replace it with the Image component (from next/image) please ? I guess you'll have to fix some links too, but at least by using this component I will have the same rendering as you

@Benjtalkshow
Copy link
Author

Hello @Benjtalkshow I think it loads in production and not locally because the files doesn't exist (with that exact names), but the contributor used the CDNImg component, which makes it working in prod (because it uses the cached assets). Can you replace it with the Image component (from next/image) please ? I guess you'll have to fix some links too, but at least by using this component I will have the same rendering as you

Alright sir.

@Benjtalkshow
Copy link
Author

@Marchand-Nicolas
I have fixed the large spaces on mobile.
Additionally, i use the next/Image as requested for the partners logos

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
❌ Change request Change requested from reviewer
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feedback Landing
2 participants