added instruction on editing files

_data/sidebar_doc.yml

@@ -236,6 +236,20 @@ entries:
           product: all
           version: all
 
+    - title: Handling reviews
+      audience: writers, designers
+      platform: all
+      product: all
+      version: all
+      print: true
+      items:
+        - title: Commenting on files
+          url: /doc_commenting_on_files.html
+          audience: writers, designers
+          platform: all
+          product: all
+          version: all
+
     - title: Publishing
       audience: writers, designers
       platform: all

_data/urls.yml

@@ -1,19 +1,4 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+end: '</a>'
 
 
 titlepage:

_layouts/page.html

@@ -12,10 +12,11 @@ layout: default
    {% endif %}
 
     {% include toc.html %}
-    <a target="blank" href="https://github.com/{{site.github_editme_path}}{{page.url | replace: '.html', '.md'}}"><button type="button" class="btn btn-default" aria-label="Left Align"><span class="glyphicon glyphicon-download-alt" aria-hidden="true"></span> Edit me</button></a>
-  {{content}}
-
+    {% if site.github_editme_path %}
+    <a href="https://github.com/{{site.github_editme_path}}{{page.url | replace: '.html', '.md'}}" class="btn btn-default " role="button"><i class="fa fa-github fa-lg"></i> Edit me</a>
+    {% endif %}
 
+       {{content}}
 
 <div class="tags">
     {% if page.tags != null %}
@@ -23,7 +24,8 @@ layout: default
     {% include custom/conditions.html %}
     {% for tag in page.tags %}
     {% if projectTags contains tag %}
-    <a href="tag-{{tag}}.html"><button type="button" class="btn btn-primary navbar-btn cursorNorm">{{page.tagName}}{{tag}}</button></a>{% unless forloop.last %}{% endunless%}
+
+    <a href="tag-{{tag}}.html" class="btn btn-info navbar-btn cursorNorm" role="button">{{page.tagName}}{{tag}}</a>
     {% endif %}
     {% endfor %}
     {% endif %}

doc_commenting_on_files.md

@@ -10,20 +10,23 @@ published: true
 
 ## About the review process
 
-If you're using the doc as code approach, you should also consider using the same techniques for reviewing the doc as people use in reviewing code. This approach will involve using Prose.io as an interface. Users will have Github accounts and authorize Prose.io to access their Github.
+If you're using the doc as code approach, you might also consider using the same techniques for reviewing the doc as people use in reviewing code. This approach will involve using Github to edit the files. 
 
 There's an Edit me button on each page on this theme. This button allows collaborators to edit the content on Github.
 
+Here's the code for that button on the page.html layout:
 
-## Add the edit button to your pages
+```
+    {% if site.github_editme_path %}
+    <a href="https://github.com/{{site.github_editme_path}}{{page.url | replace: '.html', '.md'}}" class="btn btn-default " role="button"><i class="fa fa-github fa-lg"></i> Edit me</a>
+    {% endif %}
+```
 
 
-## Instruct reviewers to authorize Prose.io
+## Add reviewers as collaborators
 
-People who plan to review the project need to authorize Prose.io on their computers. 
+If you want people to collaborate on your project so that their edits get committed to a branch on your project, you need to add them as collaborators. For your Github repo, click **Settings** and add the collaborators on the Collaborators tab using their Github usernames.
 
-<img src="{{ "/images/authorizeongithub.png" | prepend: site.baseurl }}" alt="Authorize Prose.io" />
+If you don't want to allow anyone to commit to your Github branch, don't add the reviewers as collaborators. When someone makes an edit, Github will fork the theme. The person's edit then will appear as a pull request to your repo. You can then choose to merge the change indicated in the pull or not.
 
 
-
-<img src="{{ "/images/authorizegithubscreen2.png" | prepend: site.baseurl }}" alt="Authorze Prose.io on screen 2" />

doc_tags.md

@@ -89,7 +89,7 @@ Tags have a few components.
 	    {% include custom/conditions.html %}
 	    {% for tag in page.tags %}
 	    {% if projectTags contains tag %}
-	    <a href="{{site.project}}_tag-{{tag}}.html"><button type="button" class="btn btn-info navbar-btn cursorNorm">{{page.tagName}}{{tag}}</button></a>{% unless forloop.last %}{% endunless%}
+	       <a href="tag-{{tag}}.html" class="btn btn-info navbar-btn cursorNorm" role="button">{{page.tagName}}{{tag}}</a>
 	    {% endif %}
 	    {% endfor %}
 	    {% endif %}
@@ -104,7 +104,7 @@ Tags have a few components.
 	{% include custom/conditions.html %}
 	{% for tag in page.tags %}
 	{% if projectTags contains tag %}
-	<a class="noCrossRef" href="{{site.project}}_tag-{{tag}}.html"><button type="button" class="btn btn-info navbar-btn cursorNorm">{{page.tagName}}{{tag}}</button></a>{% unless forloop.last %}{% endunless%}
+	    <a href="tag-{{tag}}.html" class="btn btn-info navbar-btn cursorNorm" role="button">{{page.tagName}}{{tag}}</a>
 	{% endif %}
 	{% endfor %}
 	{% endif %}