This is a test

.gitignore

@@ -0,0 +1,6 @@
+#
+#gitignore
+#
+
+# exclude build directory
+build/

README.md

@@ -1,2 +1,3 @@
 # Documentation
-CORAL Documentation Project
+
+***Beta*** CORAL Documentation Project  

build/html/_sources/docstyleguide.txt

@@ -8,8 +8,22 @@ The purpose of the style guide is to help keep the documentation consistent in s
 ### Setting Up ###
 
 The CDP is managed in a repo on GitHub found at [https://github.com/Coral-erm 
-](https://github.com/Coral-erm  "https://github.com/Coral-erm ").  The project uses the [Sphinx Python Documentation Generator](http://www.sphinx-doc.org/en/stable/) and [CommonMark](http://commonmark.org/).  The documentation files are edited in a combination of [reStructuredText](https://en.wikipedia.org/wiki/ReStructuredText) and [Markdown](https://en.wikipedia.org/wiki/Markdown), both markup languages supported by GitHub.  In addition, [Read the Docs](https://readthedocs.org/) is used for hosting the documentation and providing additional documentation conversion and indexing tools.   
+](https://github.com/Coral-erm  "https://github.com/Coral-erm ").  The project uses the [Sphinx Python Documentation Generator](http://www.sphinx-doc.org/en/stable/) and [ReCommonMark](http://recommonmark.readthedocs.io/en/latest/).  The documentation files are edited in a combination of [reStructuredText](https://en.wikipedia.org/wiki/ReStructuredText) and [Markdown](https://en.wikipedia.org/wiki/Markdown), both markup languages supported by GitHub.  In addition, [Read the Docs](https://readthedocs.org/) is used for hosting the documentation and providing additional documentation conversion and indexing tools.   
 
 
-### Documentation Versioning ###
+### File Structure and File Naming Conventions ###
+
+#### Images ####
+
+1) Create a subfolder under /img using the same name as the markdown file in which the images will be used.  
+
+For example, the following folder name for organizations.md
+
+	/img/organizations/
+
+
+2) Add images to the subfolder created in step 1.  Name the images with a prefix identifying the markdown file they are associated with, separated Uppercase letters with a brief description of the image. Note: The underscore character causes GitHub to incorrectly process the image filenames in Markdown, which leads to problems in building files in the ReadtheDocs.
+
+For example: **organizationsAccountsView.png** for a a screenshot of the Organization's module accounts form.
+
 

build/html/_sources/gokb.txt

@@ -50,4 +50,6 @@ Resource's identifier of provider*
 
 Package content customization
 
-You can personalize package content once it is imported. You can also custom package you already got even if it was not imported from GOKb. The "custom screen" display the current package's children. If the checkbox is checked: the resource will be kept, else it will be removed from database when you will click on 'Confirm customization' button.
+You can personalize package content once it is imported. You can also custom package you already got even if it was not imported from GOKb. The "custom screen" display the current package's children. If the checkbox is checked: the resource will be kept, else it will be removed from database when you will click on 'Confirm customization' button.
+
+This is a test!!!

build/html/_sources/index.txt

@@ -16,6 +16,7 @@ CORAL Documentation Project
    licensing
    organizations
    usagestats
+   management
    technical
    glossary
    faq