* Update side panel copy to Living copy
* Update lead paint short description
* Rebase main and update areaDetail snapshots
* Update cypress test on dataset used in beta header
* QA review updates
* Update deploy-fe-main to point to new CDN (d3r)
* Allow open source map
- create new getOSBaseMap function
- set secret on GitHub actions
- read secret into J40Map.tsx
- add secret to gatsby-config
- remove secret from .env.*
* Fix typo on yml file
* Add placeholder for API TOKEN
- add placeholder in docker compose
- add placeholder in .env.dev
- remove console.log
* Add Mapbox API Token to main deploy
* Run markdown link checker only on markdown changes
This makes sure that this action only runs if the pull request is on the
main branch and is changing markdown files.
Fixes: https://github.com/usds/justice40-tool/issues/1114
* Remove push to main trigger
* Ignore eeoc.gov in link checker
Sometimes it seems down from the perspective of github actions.
* First pass of updating documentation for new users
Trying to look at this from the perspective of someone new to the
project, and create some pathways to make it easier for people to get to
the content they are looking for.
* Make it clear that docker is doing the setup
* Link installation again from the main README
* Add some docs about the github actions
* Add markdown link check
* Move git installation first
* Add config for markdown link checker
* Fix some links
* Correct handling of repo root relative links
* Fix broken links in data roadmap
* Fix more broken links
* Fix more links
* Ignore link that's returning a 403 to the checker
It actually works if you go in a browser.
* Fix another broken link
* Ignore more urls that don't work
* Update the readme under docs
* Add some more dataset links
* More strongly call out the quickstart
* Try to call out even more the quickstart link
* Fix dead links
* Add note about initialization time
* Remove broken link from spanish install guide
These will be updated later with a full translation
Showing obscure vulnerabilities that only exist in the dev setup creates
more noise and means that they just get ignored (because they are
probably low priority). Silencing them means when we get a vulnerable
dependency alert we know to pay attention to it.
Comes from https://github.com/dependabot/dependabot-core/issues/2521 and
501bbef578.
