formatting

Author: wiheto

docs/contributing_tutorials/adding_a_new_template.rst

@@ -13,7 +13,7 @@ If the space for you template already exists, then you should follow the tutoria
 
 This tutorial assumes you have done all the steps in the preceding tutorial: :ref: `prerequisites_to_contributing`.
 
-__Note__ at present, this tutorial will require writing access to the TemplateFlow repo.
+**Note** at present, this tutorial will require writing access to the TemplateFlow repo.
 If you do not have access here, it may be best to open up an issue asking for a template space to be created.
 
 Big picture
@@ -31,25 +31,28 @@ Step 1: create a new dataset
 First make sure you are in your local templateflow directory.
 If you do not have a local templateflow copy, run:
 
-::.
+.. code-block:: bash
+
     git clone https://github.com/templateflow/templateflow/
     cd templateflow
 
 Now set the variable ``TEMPLATENAME`` to whatever your template will be called.
 Also set your Github username to the variable ``GITHUBUSERNAME``.
 Finally, write a description of your template.
 
-::.
+.. code-block:: bash
+
     TEMPALTENAME='tpl-test'
     GITHUBUSERNAME='yourusername'
     TEMPALTEDESCRIPTION="This is a test template"
     GITHUBREPO='templateflow'
 
-At the moment, always keep templateflow as GITHUBREPO, this may be changed in the future 
+At the moment, always keep templateflow as GITHUBREPO, this may be changed in the future.
 
 With these variables set you can then run the following code with no modifications:
 
-::.
+.. code-block:: bash
+
     datalad create -d . -D "$TEMPALTEDESCRIPTION" $TEMPALTENAME
     cd $TEMPALTENAME
     datalad create-sibling-github --github-organization $GITHUBREPO --github-login $GITHUBUSERNAME --access-protocol ssh $TEMPALTENAME
@@ -69,14 +72,16 @@ It will then return to the templateflow directory.
 
 The 5th line in the above code edits the file .gitmodules to replace:
 
-::.
+.. code-block::
+
     [submodule "tpl-test"]
             path = tpl-test
             url = ./tpl-test
 
 with:
 
-::.
+.. code-block::
+
     [submodule "tpl-test"]
             path = tpl-test
             url = https://github.com/templateflow/tpl-test
@@ -90,7 +95,7 @@ Step 2: Add a template_description.json
 Within this directory we place a template_description.json which is needed in all templates.
 The json file contains the following:
 
-::.
+.. code-block:: json
     {
         "Authors": ["Noone"],
         "Acknowledgements": "Curated and added to TemplateFlow by Thompson WH",

docs/contributing_tutorials/prerequisites_to_contributing.rst

@@ -26,6 +26,8 @@ There are three different types of contributions you can make to TemplateFlow.
 This contribution involves adding a new space that does not currently exist.
 Let us say you have made a new pediatric space that you transform your images to; this would be a new template space.
 All the different MNI templates are each considered their own template space.
+Currently this requires writing permissions to the TemplateFlow repo.
+For now, if you do not have access open up an issue in the templateflow repo to say which template spaces should be added.
 
 **Nifti images within an existing template space**.
 This contribution involves adding to a template space that currently exists.
@@ -60,13 +62,17 @@ Once you have the prerequisites set up, you can initialize the OSF directory ont
 
 In a new directory type:
 
-> osf init
+.. code-clock:: bash
+    
+    osf init
 
 This will prompt you for your username and TemplateFlow project number.
 This project number is ``ue5gx``.
 
 You can check that your directory has been correctly set up by typing:
 
-> osf ls
+.. code-clock:: bash
+
+    osf ls
 
 You should see the contents of the OSF project folder appear in the console.

docs/contributing_tutorials/uploading_to_existing_template.rst

@@ -108,12 +108,16 @@ Finally, the contents of new_files.csv need to be uploaded via DataLad.
 
 To do this first, move the local image file into a tmp folder.
 
-> mv tpl-test/*_atlas-test*.nii.gz ~/tmp/
+.. code-block:: bash
+
+    mv tpl-test/*_atlas-test*.nii.gz ~/tmp/
 
 Then you add the new urls to DataLad. Add a message
 
-> datalad addurls new_files.csv '{link}' '{name}' --message 'My test atlases'
-> datalad publish
+.. code-block:: bash
+
+    datalad addurls new_files.csv '{link}' '{name}' --message 'My test atlases'
+    datalad publish
 
 Example script when subdirectories are presents
 ================================================