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

🐛 Bug: Standardize Blog Image Sizes #1434

Open
idanidan29 opened this issue Feb 26, 2025 · 13 comments · May be fixed by #1477
Open

🐛 Bug: Standardize Blog Image Sizes #1434

idanidan29 opened this issue Feb 26, 2025 · 13 comments · May be fixed by #1477
Assignees
Labels
🐛 Bug Indicates that the issue is a bug or defect. Status: In Progress This issue is being worked on, and has someone assigned.

Comments

@idanidan29
Copy link
Contributor

idanidan29 commented Feb 26, 2025

Describe the bug

The images in blog posts are of varying sizes, causing an inconsistent layout across different pages. Additionally, the blog descriptions are different lengths, which leads to an uneven appearance.

Steps To Reproduce

  1. Go to the blog page.
  2. Observe the images of different sizes.
  3. Scroll down to see inconsistent blog descriptions.

Expected Behavior

All images should be the same size, and the blog descriptions should be shortened to a consistent length for a cleaner, more uniform design across pages.

Screenshots

the current behavior:
Image

my suggested fix:

Image

Device Information [optional]

- OS: Windows 11
- Browser: Chrome
- Version: 133.0.6943.127

Are you working on this issue?

Yes

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

No

If this issue is approved, I would like to be assigned to it

@idanidan29 idanidan29 added Status: Triage This is the initial status for an issue that requires triage. 🐛 Bug Indicates that the issue is a bug or defect. labels Feb 26, 2025
@idanidan29 idanidan29 changed the title 🐛 Bug: 🐛 Bug: Standardize Blog Image Sizes Feb 26, 2025
@r120dhiman
Copy link

I would like to work on this issue.
Please assign it to me

@idanidan29
Copy link
Contributor Author

idanidan29 commented Feb 27, 2025

@r120dhiman

Thank you for your interest in implementing this

Since I posted the issue, I'd like to be assigned to it.

Also, the issue hasn't been approved yet.
I have the solution and waiting for it to get approved.

@jagpreetrahi
Copy link

Hey @idanidan29 , what if , we only put the title , image and author there for clear view and remove the description , because whoever want to read that , go that blog and read about the description there , may be?

@idanidan29
Copy link
Contributor Author

That's a good idea, @jagpreetrahi! It could make it easier for the reader to understand the blog's subject and expose them to more blogs with less confusion.

@Karan-Palan
Copy link
Contributor

Umm, I have a differing opinion of this. Users want the website to be consistent, and almost all blog sites I've used as a user or a customer, they have 1-3 lines of the blog content (medium, dev-to, hashnode etc)
So it'd keep the UX better overall as users are familiar with blogs being shown that way. Let's wait for some of the maintainers to give their word on this

@cbum-dev
Copy link
Contributor

cbum-dev commented Mar 1, 2025

So it'd keep the UX better overall as users are familiar with blogs being shown that way.

Exactly. I'm somewhat familiar with UI/UX, and I believe the blog section should follow the standard design used by most blog sites. Keeping the description is important, as removing it would shorten the blog section and make the overall page look cluttered.

@idanidan29
Copy link
Contributor Author

idanidan29 commented Mar 1, 2025

Thanks for the feedback, @cbum-dev and @Karan-Palan!

Now that you're mentioning it, the description really has an effect on the user, making them want to keep reading and clicking on the blog.

@r120dhiman
Copy link

Hi @idanidan29
What I was thinking is that we can put image, complete title, and first line of description followed by the '....' showing its continuity and after that we can put name of writer. As per mu opinion we should avoid putting date after writers name.

@idanidan29
Copy link
Contributor Author

idanidan29 commented Mar 1, 2025

Thank you for the feedback, @r120dhiman! I think what you described is very similar to the current design, except for removing the date.

I believe the date is quite necessary for the blog card, as it helps users determine if the information is up-to-date and relevant to the topic.

@r120dhiman
Copy link

@idanidan29 then we can also go with entirely new approach for the blog card. Something like when the user hovers on the card the card expands reveling description and writer and other details.

@idanidan29
Copy link
Contributor Author

@r120dhiman, this could be a good idea, but it's a bit off-topic for this issue. If you'd like, I suggest bringing it up in issue #1330, which is focused on the hover effect

@idanidan29
Copy link
Contributor Author

idanidan29 commented Mar 4, 2025

@benjagm @DhairyaMajmudar, can you please assign this issue to me, so I can make a PR?

@benjagm benjagm added Status: Available No one has claimed responsibility for resolving this issue. Status: Accepted It's clear what the subject of the issue is about, and what the resolution should be. and removed Status: Triage This is the initial status for an issue that requires triage. labels Mar 5, 2025
@benjagm
Copy link
Collaborator

benjagm commented Mar 5, 2025

Thanks sounds great. @idanidan29 please go ahead with the change.

@benjagm benjagm added Status: In Progress This issue is being worked on, and has someone assigned. and removed Status: Available No one has claimed responsibility for resolving this issue. Status: Accepted It's clear what the subject of the issue is about, and what the resolution should be. labels Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Indicates that the issue is a bug or defect. Status: In Progress This issue is being worked on, and has someone assigned.
Projects
None yet
6 participants