The tool needs to somehow track if the user has accepted the cookies for each site. If they have, the warning shouldn't display. If they haven't, then the warning should display. Could probably do this through yet another cookie.

Once Issue #2 is completed, the library needs documentation on how to use it. This should be easily digestible for all levels of developers so that they can easily know how to use this simple tool.

This tool should be easy to install on any website. It's a vanilla JS library that should be able to plug and play on any site. The set-up should be minimal and the dependencies should be nonexistant. Basically, the developer should be able to add this as an npm dependency or download the js file as a static resource. They then simply include it on the page and call the initialize function to use the tool.

To accomplish this, the file(s) need to be built and consumable. To accomplish this, a few things need to happen:

1. Decide on a build tool to use
2. Set up the tool so that one file is built
3. Publish the built file to npm and as a static resource... somewhere (github?)
4. Decide on tests to execute as part of the pipeline