Update event content type based on content strategy

Hi,
I have created an MR for updating the content type.
@deepali sardana, I was already working on the issue and hence have created an MR. If you wish, you can review the MR provided.

Moving to Needs Review.
Please review.
Thanks.

This is a good start, but it's incomplete. Changes are needed in `recipe.yml` too (and possibly other files). Additionally, there are elements of the content model itself which make little sense:

• Why is the Tags field for events marked as having a cardinality of 1? (For that matter, why are there separate "Values" and "Cardinality" columns?)
• What is the purpose of the "File" field? There's no description.
• The "Link" field is also incredibly vague.

Assigning to @pameeela to provide answers on these inconsistencies.

Needs work anyway...

Note that this will remove the Locations recipe entirely in favor of an Address field on the Event content type.

Sorry all for the confusion and changing info, I've made some updates to the spreadsheet based on various conversations and to answer questions.

There's a fair bit to do here, in addition to removing the locations recipe we'll need to move all the geolocation stuff over so we can get the map on our event display. I'd be OK to do that in a follow up though if we want to stick to updating the content type here.

Self-assigning to merge the Locations stuff into Events.

I think I have this where I want it - the fields match what's in the content strategy, at least in terms of their type. Some of the names are different (body instead of field_content, for example), but that's a problem across all content types anyway.

I think @pameeela can review this.

This is beyond awesome, I was not expecting the location/map stuff to get sorted!

Just made some minor tweaks, initially was super confused about why there was still a location node but think I figured that out. Also changed the body to optional, I know the sheet said required but I've changed that now.

I'll take that as an RTBC.

Merged into 0.x. Thanks everyone!

Automatically closed - issue fixed for 2 weeks with no activity.