devdocs/specs/core-ui-design.txt

@@ -117,8 +117,8 @@ LOGO
 COLOURS
     - Canucks colours of course, Blue primary and green secondary. RI already uses them, get the hex codes there.
     - No indigo or pastels 
-
-
+  - https://material.io/design/color/#color-usage-palettes
+  - https://www.materialpalette.com/
 
 =-=-=-=-=-
 Ref material kept for new icons possibly:

devdocs/todo.txt

@@ -1,20 +1,29 @@
 # TODO (J.F.C. - Just fucking code it already)
 
-Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOiIxNTQxNTE5NTA5IiwiZXhwIjoiMTU0NDExMTUwOSIsImlzcyI6ImF5YW5vdmEuY29tIiwiaWQiOiIxIiwiYXlhbm92YS9yb2xlcyI6IjE2NDI2In0.aGI1su24D5zWkMDiYPlBx3xfCuQ8qkLdO7b5YPeOPoE
+Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOiIxNTQyNjY5Njc3IiwiZXhwIjoiMTU0NTI2MTY3NyIsImlzcyI6ImF5YW5vdmEuY29tIiwiaWQiOiIxIiwiYXlhbm92YS9yb2xlcyI6IjE2NDI2In0.93IjHRXQA9c8Z0U9qcsS73KcbG3HzYWkRzF3LwCB_rY
 
 
 ## IMMEDIATE ITEMS
 
-
-	- Loading indicator for xhr stuff
-		- The thin line one I saw is pretty skookum
-	- Dummy form with all RAVEN required input controls on it for testing
-		- As if a widget but not actual widget api calls yet so can expand this form later and save time
-	- Dirty form check and prevent route leave: https://router.vuejs.org/guide/advanced/navigation-guards.html#in-component-guards
-	- Document a release procedure while doing the next step:
-	- Post a dist version up to the dev server so can test with all our devices and note what works and what doesn't
-	- Test initial shell and dummy input form on all devices including a simple e2e test of some kind to get a start on that aspect
-		- Test as PWA on all devices
+	- Colors
+		- what are the application colors going to be and start using them now.
+	- Widget list component that works with real data
+		- Displays as a smaller item with maybe a count of widgets only that is expandable into a list of widgets
+		- paging, sorting, filtering (by tag), items per page
+			- Stored locally with client so each client app can have individual settings (i.e. phone vs desktop can have alternate settings for same user)
+		- Each item can be edited if they have the rights or viewed etc by opening into crud component
+			- List should remember where the user was when they go to edit and back again
+			- What to do if they edit?  Refresh the list but keep the same page location?
+	- Widget crud component that works with real data
+		- Dirty form check and prevent route leave: https://router.vuejs.org/guide/advanced/navigation-guards.html#in-component-guards
+		- broken rule display 
+	
+	- Release an internal test version to the DEVOPS server
+		- Scrap running it in Docker and go bare metal copying config for running .net apps from ayanova.com server?  
+		- Document the release procedure while doing the next step:
+		- Test with all our devices and note what works and what doesn't and adjust accordingly
+		- Test initial shell and dummy input form on all devices including a simple e2e test of some kind to get a start on that aspect
+			- Test as PWA on all devices
 
 
 - Stage 2 AFTER POSTED TEST ROUND COMPLETED