codeforboston / codeforboston/maple
Legislator Profile - Header
- Dominant language
- TypeScript
- Stars
- 56
- Forks
- 175
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 13
Description
## Summary
This issue covers the implementation of the Header of the new Legislator Profile page.
## Success Criteria
- [ ] Implement the design of the Legislator Profile Header, including
- [ ] Legislator Name
- [ ] Party
- [ ] District
- [ ] Contact Info (Email/Phone/Socials)
- [ ] Follow Button (Works just like any other "Follow User")
- [ ] Contact Button (Can just open a `mailto:` link to the legislator's email for now)
- [ ] Legislative Stats, including:
- [ ] Terms Served
- [ ] INVESTIGATE: Can we track members across general courts consistently by member code? Leaning toward yes, but it's not guaranteed so we should pick an long-serving member and track them back.
- [ ] If not available, we may need to open another issue for a separate scraper.
- [ ] Num Bills Sponsored / Cosponsored
- [ ] This is available in `generalCourts//bills`, but we may need to add a new index.
- [ ] The counts are also not currently precomputed - this may be a good use for the firestore `count` aggregation
- [ ] Funds Raised (Not available yet)
- [ ] `N/A` is fine for now - this data is coming with the Campiagn Finance pipeline ticket
## Screenshots
## Additional Links
- Mockup: https://maple-leg-profiles.netlify.app/
Contributor guide
Assessment
This issue has not been assessed yet.