[x] The event feed is being changed to give us event ids, and drop event urls, which contain event ids. After that change we can update the event card to construct the urls on the client, based on event id. The url is constructed based on two properties: https://go.peoplepower.org/event/${event.campaign}/${event.id}.
[x] Related, the design shows a style for a "selected" item in the event list that corresponds with an event being clicked in the adjacent map. Once we have the event ids on hand it will be more straight forward to wire up that bit of state in the store, and feed it into the event list / card, highlighting a card when selected.
[x] The event feed is also being updated to include a field indicating that an event is an "ACLU official event" (unlike the other event types, this does not come from the categories field), and there is a particular card style associated with that. When it's available, wire it all together.
[x] The event feed is being changed to give us event ids, and drop event urls, which contain event ids. After that change we can update the event card to construct the urls on the client, based on event id. The url is constructed based on two properties:
https://go.peoplepower.org/event/${event.campaign}/${event.id}
.[x] Related, the design shows a style for a "selected" item in the event list that corresponds with an event being clicked in the adjacent map. Once we have the event ids on hand it will be more straight forward to wire up that bit of state in the store, and feed it into the event list / card, highlighting a card when selected.
categories
field), and there is a particular card style associated with that. When it's available, wire it all together.