Explore Page - Githubissues

This work is a hybrid of #76 and #83 and then some. There is a small bit of polish to add, but is basically a rendition of explore page complete with concept of Narrative. Lots o' good juicy things in here, it is sizable and there are a couple of things that need polishing.

Changeset Summary (can explain more in detail in-person):

Migrated data points to public/boundaries and will fetch them via window.fetch in React App
Theme changes:
- Added concept of 'Tokens' (Copy text atoms)
- Small restructure on Theme type
- More discrete font size
Data point visibility is off by default and based on narrative selected, will turn visibility on for appropriate data points
Narrative concept

Things that still need to change:

Refactor and abstract out, as necessary, elements in ExplorePage
Toggle Panel needs to look more like the mock:
- Remove panel border
- Custom checkbox/switch style
- Font? Probably give each switch more space in-between

There is a warning occurring about an uncontrolled element becoming controlled and it isn't obvious which/where the component is...

Warning: A component is changing an uncontrolled input to be controlled. This is likely caused by the value changing from undefined to a defined value, which should not happen. Decide between using a controlled or uncontrolled input element for the lifetime of the component.

The thing I learned after taking a break and then doing this is, wrt atomic-design, never force an idea into a framework; express the idea and see if there are patterns that can be abstracted out and align with framework

codeforboston / mattapan-mapping

Explore Page #89