c
still need to clearly write how users submit poets
Sometimes users might want to use imported third party tools in their code.... we should install the most common tools within the xaqt docker images and list these things within...
the goal behind exposing the code for each poet was to allow poet designers to share their approaches with other poet designers in the community. It would be nice if...
 # TODO - [ ] setup automated test coverage tooling! (coveralls?) # Untested Code - [ ] poet upload - [ ] user `Validate` - [ ] poet `Validate`
the [`github.com/jmoiron/sqlx`](https://github.com/jmoiron/sqlx) package provides some nice extensions to the standard `database/sql` go package including support for struct tags for using with `Scan()` as well as more succinct handlers like `Get()`...
 # Overview we must be able to do two things: 1. email individual users for important updates (email verification on login, their poet errored, their poet's work is featured...
 the ui should be more of an ascii art aesthetic
NYPM needs a logo.... but we should def first change the favicon to not be the react logo -___-
test that all supported languages actually can be successfully run run