issue-28: Convert specifications into markdown#39
Conversation
The first attempt at converting from the Google Doc file to the .md file did not work very well. This is the manual cleanup. It also includes some cleanup to the document itself.
.md file names are all caps by conventions.
Create a workflow so that the specifications will automatically get made from the .md file for the .docx file.
sudonym-i
left a comment
sudonym-i
left a comment
There was a problem hiding this comment.
Looks good, one note:
Do you have a strong preference on where we place the SPECIFICATIONS.md file?
I generally prefer to only have files in root if they have a really good reason for being there, otherwise things sometimes get cluttered. Not a deal-breaker, just thought it was worth mentioning.
otherwise- LGTMIG
I'm on board with this, also reminded me that I didn't remove the old specifications.docx or update the README.md with the hyperlinks. Going to head home, resolve conflicts, restructure, update the lose ends. |
Missing double spaces for the first image line break.
4 participants
README.md edit was a little bit lax, but it doesn't seem like a good use of time currently
Fixes #28
Changes that are sneakily snuck in:
It's not a habit for me to do sneaky changes, but not doing so would have meant significant overhead to go through the document multiple times vs just the one time.