-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Text alignment and layout issue on blog page #5652
Comments
can you assign it to me |
I would like to work on it @Ashparshp |
I would like to work on it @Ashparshp |
@ayush-343 Thanks for your interest! This issue is meant for first-timers to get started, and it has already been assigned. We proceed in chronological order, so keep an eye out for more issues soon. 😊 In the meantime, you can check out this issue: #5651 |
@ShyanRoyChoudhury Any luck? |
Working on it. My apologies for the delay. Got caught up with some other work. Will create PR soon. @Ashparshp |
@ShyanRoyChoudhury No worries, thanks for the update. Looking forward to the PR! |
@ShyanRoyChoudhury Are you still working on it, or should we give someone else a chance to fix this one? |
@Ashparshp My apologies for the extreme delay. Submitted the pull request. |
duplicate of #5693 |
Already solved |
Already solved, closing this now. |
Description
The text alignment and layout on the blog page do not look good in the mobile view, particularly in the "Tags" section and the blog content cards. This misalignment affects readability and the overall user experience.
URL
The issue can be observed on the Layer5 Blog page.
Steps to Reproduce
Expected Behavior
The text and layout should be properly aligned and formatted for a consistent and visually appealing presentation on mobile devices.
Screenshots
Environment:
Contributor Resources and Handbook
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the
master
branch.Join the Layer5 Community by submitting your community member form.
The text was updated successfully, but these errors were encountered: