diff --git a/devdocs/todo.txt b/devdocs/todo.txt
index f0028c5d..ddc8df86 100644
--- a/devdocs/todo.txt
+++ b/devdocs/todo.txt
@@ -26,8 +26,17 @@ DEVELOPMENT SCHEDULE
 WEEK OF 2018-10-22 - Learn Vue, select a UI framework	
 	
 	- skim through VUE docs to familiarize before coding
+
+	- skim: https://babeljs.io/docs/en/learn
+
 	- Read the style guide and if possible stick to it:
 		- https://vuejs.org/v2/style-guide/
+	
+	- Skim router docs:https://router.vuejs.org/
+	
+	- Skim the VUEX DOCS
+
+	- Check this shit out: https://github.com/vuejs/awesome-vue#components--libraries
 
 	- Make a basic PWA app code against RAVEN server a throwaway initial stab at RAVEN for learning what is needed to learn	
 		- Be sure it's component-ized properly: https://vuejs.org/v2/guide/components.html#Organizing-Components
diff --git a/devdocs/tools.txt b/devdocs/tools.txt
index 61710ad5..be712ab2 100644
--- a/devdocs/tools.txt
+++ b/devdocs/tools.txt
@@ -101,7 +101,11 @@ This tool will audit a PWA and ensure it meets all the requirements to work well
 - Gulp seems best for me: https://docs.microsoft.com/en-us/aspnet/core/client-side/using-gulp
 
 
-
+VUE NOTES / IMPORTANT INFO
+=-=-=-=-=-=-=-=-=-=-=-=-=-
+  - always use kebab-case for everything including component names, props, events etc.  
+    - this just avoids all manner of potential issues
+  - If a runtime error occurs during a component’s render, it will be passed to the global Vue.config.errorHandler config function if it has been set. It might be a good idea to leverage this hook together with an error-tracking service like Sentry, which provides an official integration for Vue.