Rename folder to annotator_js and install as usual.  Admin setting location at /admin/config/configjs

2.0 STUFF
VERY IMPORTANT - when you upgrade, don't uninstall and resinstall this version.  It will DELETE ALL ANNOTATIONS IN DATABASE.  Just overwrite the older module directory with this one.

The update and delete functions don't work.  Believe it's on their end.

Showdown and annotator JS files are in JS folder.  Update the annotator.min.js file once released anytime after July 6th.  Keep Sai's modified file just in case.

We were getting an error in the console that the Editor using getGlobal is undefined.  So we had to alter the annotator.min.js.  It now includes this line 	var convt = new showdown.Converter(); among other changeswhich creates the converter object without using getGlobal.  Search for comments with 'Sai'  In the future, once they release a another .min file after July 6th, this shouldn't be needed.

The only real difference was changing the location of the paths in the routing table since 2.0 has different endpoints.  The libraries.yml file has different files.  Also annotator_js_start is different because plugins (now modules) are enabled differently.  We're not using any of the TinyMCE or Rich text Editor Stuff

END 2.0 STUFF

We still get an error after creating or deleting annotations.  This appeared after an upgrade to Drupal 8, beta 11.

We don't have a link in the admin menu to set which content types load the javascript, instead go here - /admin/config/configjs 

Tags don't work.  We don't have a column in the database.

Files:
annotator_js.routing.yml - sets the locations for the create,update,delete etc API functions.

annotator_js.libraryies.yml - the showdown must be loaded first. 
 
	showdown.js - For 1.2 it was copied from here, https://github.com/openannotation/annotator/blob/v1.2.x/lib/vendor/showdown.js  For 2.0 it was copied from https://cdn.rawgit.com/showdownjs/showdown/1.1.0/dist/showdown.min.js

annotatorjs.links.menu.yml - the structure.settings points to the last route in the route.yml file annotator_js.admin_display which in turns points to the form in configJS.php in ./src/form/ .  Sai kindly called this form "paragraph comments" to insure confusion.

We don't use templates, we can ignore the Twig.

In SRC
	The form already mentioned for the admin content type
	We don't think Test does anything
	Controller

