This largely depends on what the of legislative data are that we decide we'd like to use, and what data each one provides to us. We'll also need to consider which parts of this flow are manual (curated) versus which we aim to automate.

This issue depends on the issues that are focused on schema design, so that we know what the final target of this process looks like.

Example of a map that we can copy can be found here.
https://github.com/actonmass/campaign-map

1. Clean the information in the EDR 3rd party pop-up so that it only displays the information relevant to EDR (not the other bills)
2. Consider the sub pop-up, or mymaps side panel functionality. Similar to https://easytodogood.com/resolutiontracking/. Can probably be done entirely in Leaflet (i.e., not in a separate React component)
3. Bring in Colin's UI/designer friend for input

I'm imagining the filters as check boxes. Check the professor box, and only see professor icons on the map

I was thinking that we could change the color of the icon. But maybe it'd be easier to add a little plus or minus next to the icon.

Matt to add to the google drive - so it can be pulled into the site.

Create a new page, titled "other legislative endorsements" (which will be placed under the "2021 Priorities" menu), populate the page with the attached content. See #63
Other Endorsements.docx

User personas are an abstraction of the groups of people who we would expect to use a tool like this. I think it would be helpful to make concrete a list of these personas as a first design step to prioritize our features. Groups like admin (us), law students, student groups, community groups, informed citizens, etc — and their expected needs and goals in using a tool like this. Thoughts?

We should probably use something like jest for adding unit testing

Maybe let's check with Matt first, but his current site: https://easytodogood.com has a blog

Name of institution
Student groups:
Student group x

• Position:
• Statement:

Professors:
-Position:
-Statement:

4 tiers

1. Green: Legislator is on record "I will vote for this if it's introduced as a standalone bill"
2. Light green: Legislator has been a substantial advocate for this bill in the past
3. Lighter green: Legislator has advocated for this bill in the past
4. Grey: Legislator has not advocated for this bill in the past

Above the map on each priority page - the relevant paragraph should be inserted. See attached for the paragraphs.
Priority Summaries.docx

Per our meeting on 2/2, there will be a map on each page in the "2021 Priorities" menu. The "Advocacy Maps" page is meant to be general-purpose info about the maps (@mvictor55 needs to clarify this), and maybe doesn't need to be in the nav, but rather linked from each page that has a map.

When 3rd party icon (ex. professor) is clicked on, a popup should appear with the information sourced from our "3rd party table". It will display: name; school (unless it's a non-profit); statement; any external link they indicate

instead of hardcoded in the map component

fetch( "https://docs.google.com/spreadsheets/d/e/2PACX-1vQ4l7bRcBIgwsEPGM_s9zF9csIeTgE2No_4tA6MuDCBUbfmWY_e9mAfzPpCJTsIK_hUzOyJ8CmdGMsX/pub?gid=641305740&single=true&output=csv") is hard coded in the map component.

We should fetch this and pass it into the map component as a prop

1. Create three new pages, which will hold the letters we produced for each legislative priority. Each page will have one letter. Title these pages with the name of the legislative priority as shown in the menu under "2021 priorities". Populate the content of each page with the relevant letter in the attached document

2. On each priority legislation page, under the persuasive content and above the map, the following should be inserted:
   "You can read our full letter on this issue, here". The "here" should be hyperlinked and direct to the relevant "persuasive letter" page as described above.

Priority Letters.docx

Insert the contact information - phone, email, twitter - for each legislator in their pop-up.

Adjustments to the menu:

1. Delete menu items: "Democracy in MA - Overview"; "Advocacy Maps"; "GGP Blog"
2. The menu items under "2021 priorities" should be: Election Day Registration; Early/Mail Voting; Publicly Financed Campaigns.
3. Add a 4th item under the 2021 priorites: "Other Legislative Endorsements"

In sum the menu should look like:
About GGP | 2021 Priorities | Contact Us
Election Day Registration
Early/Mail Voting
Publicly Financed Campaigns
Other Legislative Endorsements

Note - we should discuss the homepage layout

Current schema, we need to determine what fields to add
Data types: https://docs.aws.amazon.com/appsync/latest/devguide/scalars.html

type Bill @model @auth(rules: [{allow: public}]) {
  id: ID!
  name: String!
  description: String
  dateIntiated: AWSTimestamp
  supporter: AWSJSON
}

The search function should always include third parties + the currently selected chamber.

• Make David, Peter, Riley, Byron, Scott, and Marcos contributors on the project.

We need icons for: professors; student groups; non-profits. Need to make sure we're not infringing copyrights.

A table to store congressman some ideas on fields:
Party
District
Date Elected

• Heroku or AWS or Netlify
• Choose one, go with it.

3 sections. Need, want, would be nice.

Create a graphql api file so the frontend can fetch data from the backend

A nice UI component that supports google forms

Create a graphql api file so the frontend can fetch data from the backend
methods:
fetchCongressman()
fetchBills(year or congressional term)
- This should join congressman onto bills

Create 3 google sheets - one per priority. Each google sheet has two tabs - one for legislators and one for third parties.

I'm pretty sure there are addons to do this.

Inside the Map component fetch the senate GeoJSON.

With the site built in Next.js, content of "About GGP", "Democracy in MA - Overview" is in HTML, and harder to edit for non-technical maintainers.

How to accommodate?

Copy the map from the Election Day Registration (EDR) page to the other 2 priority pages. Note - the names of the other priority pages are changing. We will also need to replicate the google sheets structure from EDR for the other two priorities so we can set up the back-end. Once it's set up, I'll scrape and grade our legislators for the other two priorities

See mockup on the drive for visual.
Relevant info: Name; district; how they voted (also the text, "Sen. XYZ is a strong supporter of EDR")

We want this to populate from the results of our google form. (we can probably use a manual sheet for now). I think Brian said we need a column for coordinates.

Per our meeting on 2/2, the form is a good proof-of-concept, but @mvictor55 will manage third-parties manually for now. See #26 for where it was added.