docs: Update docs/README.md

Author: MichaelCurrin

docs/README.md

@@ -1,19 +1,11 @@
 # Docsify Template
 > Live demo of a light docs site built on _Docsify-JS_ and running on Github Pages
 
-Convert your docs folder into a pretty docs website using _docsify_ and some minimal setup. This project can be used as a template or reference for your own.
+Demo site: [link](https://michaelcurrin.github.io/docsify-template/#/).
 
-See the [Docsify](https://docsify.js.org/) website.
+Convert your docs folder into a pretty docs website using [Docsify-JS](https://docsify.js.org/) and some minimal setup. This project can be used as a template or reference for your own.
 
 
-## How it works
-
-Note that this works without editing your existing docs and without building any HTML page.
-
-If you were using a static site generator like Jekyll, you might have to add front matter to your docs, in addition to setting Jekyll config for theme and menu layout.
-
-Also, with a static site generator you would build HTML files to serve, while with docsify there is a single page application running off of a _index.html_ - on each request, a markdown file is fetched by the client and rendered as HTML with a theme and menu.
-
 ## Setup
 
 ### Overview steps
@@ -22,7 +14,10 @@ Also, with a static site generator you would build HTML files to serve, while wi
     - **index page** - Homepage of the your docs site. This will setup the app using the _docsify_ library, set a theme and apply other configurations.
     - **sidebar** - Describes your menu layout. As _docsify_ is not aware of directory structure so it may not function as you hope without this file.
     - **cover page** - Optional landing page with background image and minimal text.
-2. Turn your Github repo into a Github pages site which builds from the docs directory.
+2. Update your Github repo's config so that you will get a Github Pages site built from your docs directory. _Docsify_ also works with _Netlify_ as per their docs, but this project just considers the Github Pages case.
+
+Note that this works _without_ editing your existing docs and _without_ building any HTML pages. The rendering is done on the client-side in a single page application, running on _index.html_.
+
 
 ## Setup a site
 
@@ -72,3 +67,10 @@ View the Docsify [Quickstart](https://docsify.js.org/#/quickstart) guide for ins
 The CLI tool is optional and is useful for the following:
 - Setup an initial _README.md_ (duplicated from project root), _index.html_ and _.nojekyll_ in your a target directory such as _docs_. You can do this by hand or using a template if you don't want the CLI to do it for you.
 - Serve the docs site locally, with hot reload.
+
+
+## Why not a static site generator?
+
+If you were using a static site generator like Jekyll, you might have to add front matter to your docs, in addition to setting Jekyll config for theme and menu layout.
+
+Also, with a static site generator you would build HTML files to serve, while with docsify there is a single page application running off of a _index.html_ - on each request, a markdown file is fetched by the client and rendered as HTML with a theme and menu.