devdocs/todo.txt

@@ -18,16 +18,23 @@ Changes needed to routes??
 CODING WORK
 +++++++++++
 
-Overall plan for now: anything standing in the way of making the initial client shell UI needs to be done first, everything else can wait	
-	- v7importusers (on hold?)
-		- Mostly done for now with the exception of client id and headoffice id which await the client and headoffice objects respectively and their importers
+*******************************************************
+CURRENT DEVELOPMENT OBJECTIVES: 
 
-	- USER OBJECT	
-		- Check biz rules in v7 for anything that might be missed in RAVEN biz rules
-		- NEED a document with checklist to go over to ensure that a v7 object ported to RAVEN is "DONE" i.e. not missing any biz rules or properties or something
+CLIENT SHELL: anything standing in the way of making the initial client shell UI needs to be done first, everything else can wait
+UI Shell is required for driving development processes of backend, once have client can make up initial test forms and then determine best way to write backend biz objects.
+Once that is done then can steam ahead on the biz objects but until I have the client I won't know the best way to code them so to avoid re-working shit do it in this order.
+********************************************************
+
+IMMEDIATE ITEMS:
+================
+
+	- USER OBJECT			
 		- User route and controller and biz object	
 		- User routes for create update delete the core User object (no user settings in it) {also see rights in BizRoles.cs as it is not fully fleshed out yet}
-		- UserOptions object will be used for user configurable settings, not core User stuff to avoid any rights issues or confusion or bypasses
+	
+	- USER OPTIONS OBJECT
+		- UserOptions object and routes will be used for user configurable settings, some of it initial shell (timezone, email etc), not core User stuff to avoid any rights issues or confusion or bypasses
 			- Make user options now even if it only has one setting, I will need it ongoing all the time for a ton of shit. 
 	
 	- Tag groups (modify tags already coded)
@@ -42,6 +49,11 @@ Overall plan for now: anything standing in the way of making the initial client
 Ensure all modern best practice security is properly enabled on helloayanova.com so testing is valid
 	- https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security#Deployment_best_practices
 
+
+************************************************************************************
+FUTURE ITEMS:
+=============
+
 CLIENT SHELL
 
 Once I can make the client I need to get into that and make the shell and initial interface with enough stuff to do basic testing initially