Skip to content

fix(library): show full unambiguous dates on featured and related cards#5783

Merged
waleedlatif1 merged 2 commits into
stagingfrom
worktree-fix-library-dates
Jul 20, 2026
Merged

fix(library): show full unambiguous dates on featured and related cards#5783
waleedlatif1 merged 2 commits into
stagingfrom
worktree-fix-library-dates

Conversation

@waleedlatif1

Copy link
Copy Markdown
Collaborator

Summary

  • Featured cards on the Library/Blog index and the "more posts" cards on a post page rendered dates as month + 2-digit year — e.g. July 2026 showed as "JUL 26", which reads like a day (July 26th) rather than a year.
  • Switched both to the same month / day / year format used by the list rows, post header, and author page (e.g. "Jul 13, 2026"), so dates are consistent and unambiguous everywhere.

Type of Change

  • Bug fix

Testing

Tested manually

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

@vercel

vercel Bot commented Jul 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
docs Skipped Skipped Jul 20, 2026 11:32pm

Request Review

@cursor

cursor Bot commented Jul 20, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
Display-only date formatting on marketing pages with no auth, data, or API impact.

Overview
Fixes ambiguous dates on featured (library/blog index) and related post cards that used short month + two-digit year (e.g. "JUL 26"), which could be read as a day instead of 2026. Those cards now use the same month / day / full year pattern as list rows and post headers (e.g. "Jul 13, 2026").

All landing content date displays in content-author-page, content-index-page, and content-post-page also pass timeZone: 'UTC' to toLocaleDateString, so published dates stay stable across server and client locales.

Reviewed by Cursor Bugbot for commit 84c41a0. Configure here.

@greptile-apps

greptile-apps Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR makes publication dates consistent and unambiguous across the Library and Blog pages. The main changes are:

  • Shows featured and related-card dates as Mon D, YYYY.
  • Formats card, list, author, and post-header dates in UTC.
  • Prevents server timezones from shifting UTC publication dates.

Confidence Score: 5/5

This looks safe to merge.

  • The updated formatters use UTC with UTC-normalized publication dates.
  • The previously reported calendar-day shifts are no longer reachable.
  • No blocking issues were found in the changed code.

Important Files Changed

Filename Overview
apps/sim/app/(landing)/components/content-author-page/content-author-page.tsx Formats both author-page date variants in UTC.
apps/sim/app/(landing)/components/content-index-page/content-index-page.tsx Uses full dates on featured cards and UTC across index-page date variants.
apps/sim/app/(landing)/components/content-post-page/content-post-page.tsx Uses UTC for the post header and full UTC dates on related cards.

Reviews (2): Last reviewed commit: "fix(library): format content dates in UT..." | Re-trigger Greptile

@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@greptile

@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@cursor review

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

Reviewed by Cursor Bugbot for commit 84c41a0. Configure here.

@waleedlatif1
waleedlatif1 merged commit a1ea3bd into staging Jul 20, 2026
20 checks passed
@waleedlatif1
waleedlatif1 deleted the worktree-fix-library-dates branch July 20, 2026 23:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant