From f7822adea600f117b258f9c3285931bf33611301 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ren=C3=A9=20F=C3=B6hring?= <rf@bamaru.de>
Date: Sun, 23 Feb 2014 19:04:40 +0100
Subject: [PATCH] Update wording

---
 _layouts/default.html |  2 +-
 index.html            | 36 +++++++++++++++++++++++++++++-------
 participate.html      | 26 +++++++++++++++++++-------
 public/css/site.css   |  6 ++++++
 4 files changed, 55 insertions(+), 15 deletions(-)

diff --git a/_layouts/default.html b/_layouts/default.html
index d530a10..a466803 100644
--- a/_layouts/default.html
+++ b/_layouts/default.html
@@ -32,7 +32,7 @@ <h1 class="masthead-title"><em>#</em> Inch</h1>
 
 
       <div class="container pages-footer">
-        <h1 class="pages-title"><img src="/public/images/logo.png">nch Pages</h1>
+        <h1 class="pages-title"><a href="/"><img src="/public/images/logo.png">nch Pages</a></h1>
         <small>
           built with
           <a target="_blank" href="https://pages.github.com/">GitHub Pages</a>,
diff --git a/index.html b/index.html
index 4afe243..f7ff356 100644
--- a/index.html
+++ b/index.html
@@ -3,12 +3,32 @@
 title: Home
 ---
 
-<h1 class="pages-title"><img src="/public/images/logo.png">nch Pages</h1>
-
 <div class="repo-wrapper">
   <div class="repo-card">
     <div class="repo-info">
-      <h2>What is Inch Pages?</h1>
+
+{% markdown %}
+## Documentation badges for Ruby projects ![Inline docs](/public/images/badge-example.png)
+
+### Advantages for maintainers
+
+If you are a gem developer or maintain a library you probably already use badges in your README to show that your tests are passing and your code isn't a horrible mess in need of refactoring.
+
+Now you can also show that you documented your project properly.
+
+[Click here to request a badge for your project](/participate)
+
+### Advantages for developers
+
+If you are a Ruby developer, you know the pain of cloning a project you want to improve just to find out that it is completely undocumented.
+
+Then you have to form the mental equivalent of an AST to comprehend how it all fits together. Wouldn't it be great to see the present level of documentation directly in the README?
+
+<a target="_blank" href="http://twitter.com/intent/tweet?url=http://inch-pages.github.io/&text={{ "Documentation badges for Ruby!" | url_escape }}">Click here to spread the word</a>
+
+## FAQ
+{% endmarkdown %}
+      <h3>What is Inch Pages?</h3>
       <p>
         This project is an attempt to raise the visiblity of code documentation in Ruby.
         It provides <strong>badges to include in your project's README</strong>, to show people that documenting code is a cool thing.
@@ -19,25 +39,27 @@ <h2>What is Inch Pages?</h1>
         <a href="/participate">Get yours!</a>
       </p>
 
-      <h2>What is Inch?</h1>
+      <h3>What is Inch?</h3>
       <p>
         <a target="_blank" href="http://trivelop.de/inch">Inch</a> is a <strong>documentation measurement tool for Ruby</strong> that was created to help people document their code.
         It is a command-line utility that gives grades based on how complete the docs are (<a target="_blank" href="http://trivelop.de/inch">screenshots</a>).
       </p>
 
-      <h2>What is the goal?</h1>
+      <h3>What is the goal?</h3>
       <p>
         I really think that posting these badges in a project's README will benefit the project (because <strong>people can see that it's well documented</strong>) and the community by improving the visibility of documentation.
       </p>
       <p>
         Let's start a discussion, let's raise the visibility of documentation, let's talk.
-        <a target="_blank" href="https://twitter.com/rrrene">Hit me up on Twitter</a> or <a target="_blank" href="{{ site.inch_pages.new_issue_url }}">via issue</a>.
       </p>
 
-      <h2>Wait, who are you?</h1>
+      <h3>Wait, who are you?</h3>
       <p>
         I'm <a target="_blank" href="https://twitter.com/rrrene">@rrrene</a>, creator of <a target="_blank" href="http://github.com/rrrene/sparkr">sparkr</a> and <a target="_blank" href="http://github.com/rrrene/inch">Inch</a>.
       </p>
+      <p>
+        <a target="_blank" href="https://twitter.com/rrrene">Hit me up on Twitter</a> or <a target="_blank" href="{{ site.inch_pages.new_issue_url }}">create an issue</a> in the Inch Pages project.
+      </p>
     </div>
   </div>
 </div>
diff --git a/participate.html b/participate.html
index 7512ed4..03ede63 100644
--- a/participate.html
+++ b/participate.html
@@ -7,7 +7,7 @@
 <div class="repo-wrapper">
   <div class="repo-card">
     <div class="repo-info">
-      <h2>How do I get my own badge?</h1>
+      <h2>How do I get my own badge?</h2>
       <p>
         To get a badge for your own projects, <a href="{{ site.inch_pages.project_yaml_url }}">edit this file on GitHub</a> and <strong>add your project</strong> in the form <code>username/repo</code>:
       </p>
@@ -18,18 +18,30 @@ <h2>How do I get my own badge?</h1>
       <p>
       I will in turn send you a pull request with your updated README (and a link to your "Inch Page", so you can check it first).
       </p>
-      <h2>Why is this not an automated service?</h1>
-      <p>
-        I would really like this to be one, but unfortunately I'm currently pretty busy (preparing my first teaching assignment). <strong>If this project gains traction, I will work on a web-service</strong> with hooks, oauth et al.
-        But until then, this solution can help us to raise awareness for good documentation in our projects.
-      </p>
+
+{% markdown %}
+### So is this a fully featured CI service?
+
+No, not yet at least. This is a ***community driven project*** based on GitHub Pages, passion, pull requests and a bit of manual labor on my part.
+
+Inch Pages is a social project at heart.
+We can always implement a full-blown web-service after we have convinced a broader audience of the importance of inline documentation.
+
+But for now, the important bits for raising the visibility of code documentation are there: ***badges and status pages***.
+{% endmarkdown %}
+
       <p>
         So: <a href="{{ site.inch_pages.project_yaml_url }}">add your project!</a> Pull requests are fun!
       </p>
-      <h2>Wait, who are you?</h1>
+
+
+      <h3>Wait, who are you?</h3>
       <p>
         I'm <a target="_blank" href="https://twitter.com/rrrene">@rrrene</a>, creator of <a target="_blank" href="http://github.com/rrrene/sparkr">sparkr</a> and <a target="_blank" href="http://github.com/rrrene/inch">Inch</a>.
       </p>
+      <p>
+        <a target="_blank" href="https://twitter.com/rrrene">Hit me up on Twitter</a> or <a target="_blank" href="{{ site.inch_pages.new_issue_url }}">create an issue</a> in the Inch Pages project.
+      </p>
     </div>
   </div>
 </div>
diff --git a/public/css/site.css b/public/css/site.css
index 7b78195..037582d 100644
--- a/public/css/site.css
+++ b/public/css/site.css
@@ -1,6 +1,12 @@
 .pages-title {
   text-align: center;
 }
+.pages-title a {
+  color: inherit;
+}
+.pages-title a:hover {
+  text-decoration: none;
+}
 .pages-title img {
   vertical-align: bottom;
   opacity: 0.8;