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

🐛 Bug: Event times are shown only in UTC and not in local tim

Open
#2,142 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe the bug

On the JSON Schema website, the upcoming events show time only in UTC.
Users from other countries do not know what time the event is in their own timezone.

This makes it confusing to know when the meeting will actually happen.

Steps To Reproduce
  1. Open https://json-schema.org
  2. Scroll down to “JSON Schema Community Meetings & Events”
  3. Look at the “Upcoming events” list
  4. You will see that event times are shown only in UTC
Expected Behavior

The website should also show the event time in the user’s local timezone
or provide a way to see the local time easily.

Screenshots
Image
Device Information [optional]
- OS:
- Browser:
- version:
Are you working on this issue?

Yes

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

Start at https://json-schema.org and inspect the “JSON Schema Community Meetings & Events” section, especially how the “Upcoming events” list displays times. Confirm the current UTC-only behavior and determine how the website represents event times. Done means upcoming events also expose the viewer’s local time or an equally easy way to see it.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.