[f_legislationtracking] Design & Web-App: All legislation page

[evamaxfield]

Just like the /persons and /events this would be the /matters route and page.

A page to display all matters and highlight some of them (most recent status changes, most recent amendments, etc.)

[tohuynh]

@JacksonMaxfield The proposed design is unlike our all events page. It's always single column and doesn't use our current legislation card https://councildataproject.org/cdp-frontend/?path=/story/library-cards-legislation--adopted

Which design should we use? I could see moving the status icon to the left of the status text in our current legislation card and adding the legislation description or context span (depending on whether the card is in the all legislations page or search legislations page).

[evamaxfield]

This is a great question. I think we should stick with the card design but merge some of the ideas in this design. Let me ask Neha about it.

[evamaxfield]

Neha response:

I think it’s a good idea for the design to be consistent throughout so sticking to the card design sounds good to me. I went with a list design because users can scan more search results when it’s in a list view. With cards, there tends to be fewer results the user can see before scrolling. But I see value in changing it to a card design if it means keeping it consistent with the other pages.

[tohuynh]

Component requirements:

• [f_legislationtracking] Update legislation card #188