From 442312eca8ad4a3ec39d507b112ab7be30c62a9a Mon Sep 17 00:00:00 2001
From: antonchanning <antonchanning@gmail.com>
Date: Mon, 21 May 2018 15:08:00 +0100
Subject: [PATCH] A BlockPress Use Case

Issue #9
---
 docs/content/github_pages.html | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/docs/content/github_pages.html b/docs/content/github_pages.html
index 71d1004..a179331 100644
--- a/docs/content/github_pages.html
+++ b/docs/content/github_pages.html
@@ -1,2 +1,17 @@
 <h1>BlockPress in Github Pages</h1>
-<p>A test of BlockPress running in Github Pages</p>
+
+<p>You are looking at an instance of BlockPress code running in Github Pages.</p>
+
+<h2>A BlockPress use case</h2>
+
+<p>What does this mean? It means github projects that have a steem
+based blog, can now use blockpress for their github pages, and embed their blog directly.
+Every time they post a new blog, or someone replies with a comment, it will be instantly
+available on their github pages.</p>
+
+<p>Such a blockpress user will be able to take advantage of our range of themes and palettes,
+  or easily create their own.</p>
+
+<p>And this is just the start, as blockpress development continues and we add new features
+  and modules, such a site will be able to take advantage of an inceasing range of content
+  options!</p>