diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index b842f794..5de2f830 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -77,23 +77,28 @@ DONE: Turn widget edit ROLES into a static select populated from server
 	- Use the enumpicklist route to get a list of roles and use it for the widget UI	
 DONE: Widget - NOTES FIELD 
 TODO: TAGS!!! 
-	- Adding a new tag doesn't flag the record as dirty! (selecting does though)
-	- Localize the text enter a tag
+	- Adding a new tag doesn't flag the record as dirty! (selecting does though)	
 	- Layout: tags seems to buried into the rest of the form fields, maybe needs more whitespace around it, or a box
 	- COMPONENTIZE	
 	- Could auto-insert tags in suggestion list like the current year or month or year/month/day or user name or ??
 
 TODO: Custom fields
+	- Componentize
 TODO: Record history display / check other AyaNova 7 options / buttons that need to carry forward
 	- Some of this stuff is stage 2 for the edit form
 	- Record history could be displayed on a timeline: https://vuetifyjs.com/en/components/timelines
+	- componentize
 TODO: WIKI
+	- componentize
 TODO: Attached documents
+	- componentize
 
 RETEST HERE ON ALL DEVICES
 
 TODO: NOW THAT FORM IS THERE MOSTLY, CLEAN UP CODE FOR RE-USE in many other forms
 	- Don't need to replicate common code so put it somewhere else
+	- Are any of the controls better as a component and self contained to save the size of the form code and complexity?
+		- What I mean is, for example, a text entry field could be standardized then re-used as a component if it's props and settings take up so much space etc
 	- formstate shit is also menu shit really so can they be combined somehow, like present two sets of menu options one read only and one fully read-write?
 		- some forms will have special needs but could handle them outside of the regular boilerplate shit?
 TODO: Outstanding case with vuetify bug in clear button when readonly, check if fixed and if it isn't might need a workaround