json-schema-org / json-schema-org/website

🐛 Bug: Improves the UI/UX of the blog post and its text on the mobile devices.

Open
#1,876 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🐛 Bug Status: Triage
Dominant language
HTML
Stars
169
Forks
484
Avg merge
2d 2h
Merged PRs (30d)
6

Description

Describe the bug

This issue contains the small improvements on the blog pages that breaks the UI or not look responsive on the mobile device either on desktop site or without it.

  1. The title text of blog is currently seems too large and takes too much space on mobile device.
  2. The background image of this blog not fit properly on the mobile device.
  3. The author icon and the read more button overlap each other and not properly define the responsive UI on the mobile device. It can create confusion to the blog reader by seeing the read button behind the icon.
  4. On this blog , there is either a page or a image not found there between the blog contain. Need clarification?
  5. In this page, there is a blog container inside which there is a un-necessary space present between the content that looks not good on the mobile device.
Steps To Reproduce

Go to the blog page and individual blog on the mobile device and see the UI/UX there.

Expected Behavior

The UI/UX of the blog page and it's text should look responsive on the mobile device as well. And also the not found item on the API days Paris 2023 blog should be resolve for better readability and understanding.

Screenshots
Image Image Image Image Image

Image

Device Information [optional]
- OS:Window
- Browser: Chrome,FireFox
- version:
Are you working on this issue?

Yes

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

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The payload names no source files or tests; begin by reproducing the blog index and the named posts on a mobile device in Chrome or Firefox. Check the title, background image, author icon, read-more button, missing content, and spacing, then confirm that each page is responsive and the missing item is resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
design, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.