CodeForPhilly / CodeForPhilly/codeforphilly-ng
RelativeTime component for the 13 <time dateTime title> sites
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 9
Description
## Context
PR #157 converted every relative or `title`-only date in `apps/web` to `` — 13 sites after the sweep, across `ActivityCard`, `HelpWantedCard`, `BlogIndex`, `BlogDetail`, `Account`, `AccountClaim`, `StaffAccountClaimQueue`, `PersonDetail`, `ProjectDetail`.
## Problem
Three attributes and two formatter calls per site, all identical. The next date rendered in the app will likely drop one of them (that is exactly how three sites were missed on the first pass of #157).
## Proposal
A `RelativeTime` component (`apps/web/src/components/RelativeTime.tsx`) taking `iso` and an optional `className`, rendering the `
Deferred from `plans/a11y-mechanical.md` (PR #157).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with apps/web/src/components/RelativeTime.tsx and review PR #157 plus plans/a11y-mechanical.md for the existing date patterns. Check the 13 named sites across ActivityCard, HelpWantedCard, BlogIndex, BlogDetail, Account, AccountClaim, StaffAccountClaimQueue, PersonDetail, and ProjectDetail. Done means those sites use the shared component with their needed props and retain the dateTime, absolute title, relative text, and any prefixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100