3 files changed, 22 insertions(+), 0 deletions(-)

A ISSUES/docs/stylize_css_reference.md
A ISSUES/docs/update_changelog.md
A ISSUES/docs/update_license.md

@@ 0,0 1,7 @@
+# Stylize HTML included in `css-reference.html` to visually seperate a tag from a description
+
+Currently, the included CSS Reference file is visually difficult to read.
+
+While the software may be developed with Visually Impaired users as a primary target demographic, that does not mean it should shy away from making its end-developer documentation easy to parse both with Rhapsode via audio, *and* visually for those who do not use the software but would like to step up their accessibility game.
+
+This could be achived with some simple HTML5/CSS styling, like changing the background color and changing tag font to Monospace.

@@ 0,0 1,3 @@
+# Update or Remove the CHANGELOG
+
+The changelog doesn't show anything aside from the initial release version. This should either be updated or removed.

@@ 0,0 1,12 @@
+# Include specific public domain license mechanism in LICENSE for audio
+
+The license file *(as of 6450441)* (in regards to audio files) does not specify a specific strong public domain clause or creative commons license:
+
+		```
+		Sound files are in the public domain. The rest of the code, and it's documentation,
+		is under the GNU GPL v3+.
+		```
+
+While not strictly necessary for public domain audio works (at least, to my [ariana.giroux@gmail.com] knowledge and in Canada), this is not something that will hold up in court. It is best to include a Creative Commons license that would apply to the audio files. My [ariana.giroux@gmail.com] suggestion would be to utilize a `CC BY` creative commons license.
+
+This license is extremely permissive, only requiring credit back to the original author via derivative and commercial applications. This is already required for the code base via the GPL, so including a similar requirement for the audio files is not a stretch.