Add issue levels doc (#414)

docs/readme.md

@@ -20,6 +20,8 @@ items:
     title:  Installation Guide
   - path: liquid-tags.md
     title:  Liquid Tags
+  - path: vocabulary.md
+    title: Vocabulary
 ---
 
 # Welcome to the dev.to documentation!

docs/vocabulary.md

@@ -0,0 +1,13 @@
+## Vocabulary / Team Jargon
+
+### Issue Levels
+
+* Level 1: Mission critical. Tends to impact all users. (i.e. production stuck in an infinite heroku deployment)
+
+* Level 2: Not mission critical but needs to be taken care of as quickly as possible. Tends to impact a subset of users. (i.e. form submission broken on mentorship settings)
+
+* Level 3: Issue that can wait until the next sprint planning, but definitely needs to be discussed. Often an edge case that sparks discussion -- is this a patch or do we need to re-architect something? (i.e. running out of memory where a few pages get 500 errors)
+
+* Level 4: Issue is not affecting users. Likely an internal tool that needs to be fixed. (i.e. slack notifications not pinging)
+
+* Level 5: Tech that stopped working but also isn't related to users/the site. (i.e. the gumball machine we use to generate random winners is broken)