Remove time from event startDate / endDate fields in the CMS

[CharlyMartin]

📝 Description

This PR updates the event's startDate / endDate fields by removing the time portion. This will improve the CMS UX for the content team, standardize the data and make things clearer for us.

🛠️ Key Changes

• Updates config.yml with new datetime format - 7a61172
• Removes the time portion from all event Markdown entries - 06fd2ec
• Refactors getMetaData to display a single date if the start and end dates are the same.
• Fixes a bug in event sorting where an event can be both upcoming and past, as seen on fil.org today with the Digital Real Estate Summit event - 7920f0c

🧪 How to Test

Run the CMS locally, create an event and make sure the start and end times are only dates, not times.

📸 Screenshots

🔖 Resources

• https://decapcms.org/docs/widgets/datetime/

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
ffdweb-site	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 12, 2025 0:20am
filecoin-foundation-site	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 12, 2025 0:20am

[notion-workspace]

[FF] Improve date/time UX for CMS event entries

[barbaraperic]

Just testing for now! I've added end date, and removed it - which caused a zod error:

Error [ZodError]: [
  {
    "code": "invalid_date",
    "path": [
      "end-date"
    ],
    "message": "Invalid date"
  }
]

Basically the field went from end-date: 2025-02-13 to end-date: ""

[barbaraperic]

Think it's unrelated to this PR, but I was able to create an event without SEO description, and zod started screaming.

 ⨯ Error [ZodError]: [
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "undefined",
    "path": [
      "seo",
      "description"
    ],
    "message": "Required"
  },
  {
    "code": "invalid_date",
    "path": [
      "end-date"
    ],
    "message": "Invalid date"
  }
]
    at async getMarkdownData (src/app/_utils/getMarkdownData.ts:39:23)
    at async getEventsData (src/app/events/utils/getEventData.ts:17:20)
    at async Object.generateStaticParams (webpack-internal:/(rsc)/src/app/events/[slug]/src/app/events/[slug]/page.tsx:137:18)
  37 |     const dataToValidate = content ? { ...data, content } : data
  38 |
> 39 |     const parsedData = await zodSchema.parseAsync(dataToValidate)
     |                       ^

[barbaraperic]

Suuuper random edge case, but we allow start-date to be after end-date. Example: start-date: 2025-02-12
end-date: 2025-02-13.

[barbaraperic]

this reads nicely 😊

[barbaraperic]

Is this the other way around? 🧐

[CharlyMartin]

It should definitely be the other way around 😅 And that's a good catch! Nothing prevents the author from doing this, I'll add a Zod validation to catch these mistakes for us 🙏

[CharlyMartin]

https://fil.org/events/dweb-camp 🙃

[mirhamasala]

Think it's unrelated to this PR, but I was able to create an event without SEO description, and zod started screaming.

@barbaraperic This has been fixed in #1098

[mirhamasala]

Have we tested this using Chrome DevTools → Network tab → More tools → Sensors?

I’m concerned that some systems (browsers) might assume the date is in local time, especially if they automatically attach a time zone.

[CharlyMartin]

That's a valid concern!

When logging the data here I see this, which is what we want!

startDate 2024-11-06T00:00:00.000Z
endDate 2024-11-12T00:00:00.000Z

But I'll play with the Sensors and see if we get different results in the US vs Asia.

[CharlyMartin]

Just testing for now! I've added end date, and removed it - which caused a zod error:

Yes, this is not related to this PR, this is how Decap works. It doesn't delete fields sadly 🥲