codeforboston / codeforboston/maple

[Design] MGL Topics - Browse and Bill Pages

Open
#1,418 0 comments 0 reactions 0 assignees View on GitHub
design
Dominant language
TypeScript
Stars
56
Forks
175
Avg merge
2d 5h
Merged PRs (30d)
13

Description

This ticket describes how we want to leverage the "MGL Topic" data we will store on the back-end. This will impact 1) Bill page; 2) Browse Bills; and 3) Browse Testimony.

NOTE - we will develop "tags" (ie., those generated by LLMs) separately - as opposed to these "Topics". Once the back-ends are set up for both, we can decide how to combine/distinguish on the front end.

1. Bill Page
We need to add this title information to each bill page. However, some bills will have no data here, and some will have dozens (ie. some bills do not mention the MGL, and others amend dozens of different chapters of the MGL). My thought is that we include a box above or below the "Committee" box, which contains the a max of X rows (3?) and can be expanded when there is more information than can be shown in the box.
The box could be titled "Topics (Laws Amended)". So for example, this bill: https://www.mapletestimony.org/bills/193/S2528
The box could contain information formatted like:
"Public School (Ch. 71)
Libraries (Ch. 78)
Audita Querala, Certiorari, Mandamus, Quo Warranto"
[Yes - these are strange words]

2. Browse Bills + Browse Testimony [same req]
On the "Browse Bills" and "Browse Testimony" Page, insert another filter box on the left side, which lists all of the Title names. Each title can be expanded to display the chapter names. Users should be able to filter by title or chapter ie. select the relevant check box. Selecting a "title" will auto-select all the chapters within it. It should look like the screenshot below, except that it would be the filter/checkbox, and the "Part" is ignored.
![image](https://github.com/codeforboston/maple/assets/71357256/cb0600ed-081d-49f2-b9e3-04170ced4d32)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.