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] Mobile responsiveness for blog pages #60

Open
1 task done
Netacci opened this issue Oct 2, 2024 · 4 comments
Open
1 task done

[Bug] Mobile responsiveness for blog pages #60

Netacci opened this issue Oct 2, 2024 · 4 comments
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on

Comments

@Netacci
Copy link

Netacci commented Oct 2, 2024

Description

When viewing blog post pages on smaller screens (mobile devices), the content appears to shrink, making it difficult to read and interact with. This issue affects the overall mobile user experience, as the page layout is not adapting responsively to the screen size

Reproduction

  1. Go to `blog-post.html` or `blog-index.html` on a mobile device or simulate a smaller screen size using browser developer tools.
  2. Scroll through the content and observe how the text and images scale.
  3. Notice that some content doesn't take up the full width, leaving many whitespaces.
  4. See error: content is not mobile-friendly, and elements are improperly scaled.

Expectation

The blog post pages should be fully responsive across all screen sizes:

  • Content should resize and reflow appropriately for mobile devices.
  • Text should remain legible, and images should scale while maintaining their aspect ratio.
  • The layout should adapt to smaller screens without shrinking or distorting content.

Screenshots

Blog post page /specimen/contexts/blog-post.html

Blog Index page /specimen/contexts/blog-index.html
This issue only occurs on the first item on the featured posts list. The text doesn't fill up the container space causing a lot of whitespace.

Environment

  • Device: Laptop
  • OS: Windows 11
  • Browser: Chrome
  • Version: (eg. 13; 73)
  • Other info: Display resolution – max width 680px (issue specifically observed at this breakpoint or lower)

Additional context

We can reduce the padding for article on the blog index page. Currently, it is 4em for all screen sizes. Also, we can reduce fontsizes where necessary so that it's more suitable for mobile.

Implementation

  • I would be interested in implementing this feature.
@Netacci Netacci added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Oct 2, 2024
@possumbilities possumbilities added 🧹 status: ticket work required Needs more details before it can be worked on and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Oct 2, 2024
@possumbilities
Copy link
Contributor

@Netacci Thanks for this contribution! Which context are you viewing this in? What specific px cut-off is this occurring at? Can you please fill out and provide the device/browser/os details that were in the Issue template originally?

@Netacci
Copy link
Author

Netacci commented Oct 2, 2024

Hi @possumbilities I have updated the issue with additional information, screenshots, and screen recordings. This issue spans across some other pages but I picked the blog post pages as a starting point.

@Netacci Netacci changed the title [Feature] Mobile responsiveness [Bug] Mobile responsiveness for blog pages Oct 7, 2024
@Netacci
Copy link
Author

Netacci commented Oct 10, 2024

hi @possumbilities, I updated this issue last week, but it hasn't been looked at yet. Just a soft reminder

@OmarAmeen01
Copy link
Contributor

Linking this issue to the this issue #276 for a application of general fix to this problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on
Projects
Status: Backlog
Development

No branches or pull requests

3 participants