diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index e309b78c..58b4a709 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -66,16 +66,29 @@ CURRENT TODOs
 
 @@@@@@@@@@@ ROADMAP STAGE 2:
 
+DBDUMP
+	tentative plan:
+		wiki export isn't monolithic but instead goes with object export and is exported out to the objects folder structure since it need to be imported that way at the same time
+		use WikiPageExistanceChecker on each object that is wikiable in v7 to check and separately export that as well
+		wiki in v7 are in html format so just need an html to rtf converter
+		internal images will be much fuckery
+		file attachments must be done simultaneously in the same process as they go hand in hand
 
 
-		
+		 internal static bool WikiPageExists(Guid SourceObjectID)
+        {
 
+            return ((WikiPageExistanceChecker)DataPortal.Fetch(new Criteria(SourceObjectID))).mExists;
 
-todo: THIS!  At this point, upload to dev server and thoroughly test with devices, it seems a bit slow at times
-	- Might need to hide attachments until user clicks on something to reveal as it seems odd to fetch every open
+        }
 
-todo: careful and thorough PERF tests remotely and local
-	- https://www.digitalocean.com/community/tutorials/how-to-use-chrome-dev-tools-to-find-performance-bottlenecks?utm_source=DigitalOcean_Newsletter
+  /// <summary>
+        /// Get's content with AyaNova RI ready AyaImage: tags and AyaNova: urls 
+        /// </summary>
+        /// <param name="bForEditing">true=don't build file list</param>
+        /// <param name="baseSiteURL"></param>
+        /// <returns></returns>
+        public string GetContentAsRIReadyHTML(bool bForEditing, string baseSiteURL)
 
 todo: after attachments - DATADUMP - v7 wiki to RAVEN markdown 
 		- https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3468
@@ -85,6 +98,42 @@ todo: Datadump EXPORT and RAVEN IMPORT of all attachment / wiki stuff
 	- v7 attached files, internal documents all handled
 	- Code it now
 
+
+
+todo: dbdump v7 DOCUMENTS / linked files feature
+	- users might have a folder of attached docs source files that they really want to keep and not some others that are less important?
+	- Maybe need a single destination object that just holds the attached docs in order to prevent dupes?
+	
+	- Maybe an attached docs special folder that they can dump files into that are important and if an object has a link to them it can look in there to see if it's present or not?
+	- This will need some thinking to avoid duplicate imports and to determine what the user wants to do in reality
+		- there are potential issues around making attached docs into locally stored ones such as duplicating unnecessarily etc
+		- Attachments are allowed to be duplicates, there is no reference counting system or anything so ...
+	- Needs a good think, maybe it's not something we can support?
+		- Or, maybe it needs to be something done at the v7 end first, like users need to choose what to keep or not somehow?
+	- Maybe it needs to just make a link in the wiki to the docs?
+	- import maybe *looks* for the linked docs in locations provided by user or expects to be in location provided
+	- will automatically scan entire folder structure, get all file names and then work on importing / attaching
+	- so user just needs to ensure they are *somewhere* in a folder specified so that AyaNova can find them and import them
+	- this is as an alternative to putting them into the dbdump export file, it exports the links but the import will take the links provided in the dbdump as well as the location to search
+	for the files and do the rest.
+	- Or maybe dbdump looks for the linked files, confirms their existence, checksums them and then uses that as the basis to re-find them at the import end?
+		- this way even if the name is different it doesn't matter, it will find them.
+		- this helps because there could be many dupes linked to the same file etc.
+		- Actually that's an issue, what if they were trying to save space so had ONE copy of a file linked from all over the place and then v8 comes along and replicates it over and over again
+
+
+---------------------------------------------
+		
+
+
+
+todo: THIS!  At this point, upload to dev server and thoroughly test with devices, it seems a bit slow at times
+	- Might need to hide attachments until user clicks on something to reveal as it seems odd to fetch every open
+
+todo: careful and thorough PERF tests remotely and local
+	- https://www.digitalocean.com/community/tutorials/how-to-use-chrome-dev-tools-to-find-performance-bottlenecks?utm_source=DigitalOcean_Newsletter
+
+
 todo: after attachments - integration tests update
 
 todo: EventLog Processor at server has TWO! separate skip and take portions in the same query, wtf?
@@ -132,6 +181,9 @@ TODO: PRIORITIZE THE FOLLOWING BLOCK AND move INTO appropriate STAGES
 todo: before moving on to the next thing, triage these suggestions as there are many impactful ones
 	- https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3745
 
+todo: OPS routes!
+	- Backup, restore, import etc
+	- These need to be done fairly early on in order to have shit to play with for testing etc
 
 todo: Login form customizable for logo etc?
 	- https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3592