Documentation

2 files changed, 12 insertions, 10 deletions

diff --git a/src/site/plugins_overview.mkd b/src/site/plugins_overview.mkd
index 43f3a12a..f7872fdb 100644
--- a/src/site/plugins_overview.mkd
+++ b/src/site/plugins_overview.mkd
@@ -45,6 +45,8 @@ Administrators may manage plugins through the `plugin` SSH dispatch command:
 
 Through this command interface plugins can be started, stopped, disabled, enabled, installed, uninstalled, listed, etc.  Each command is supports the `--help` argument which will guide you in understanding the options and usage of the command.
 
+You may watch an Asciinema screencast of how to use the SSH transport and the plugin manager [here](https://asciinema.org/a/9342).
+
 ### Default Plugin Registry
 
 Gitblit provides a simple default registry of plugins. The registry is a JSON file and it lists plugin metadata and download locations.
@@ -62,13 +64,3 @@ If you develop your own plugins that you want hosted by or linked in the default
 The `plugins.json` file is parameterized with the `${self}` placeholder.  This parameter is substituted on download with with the source URL of the registry file.  This allows you to clone and serve your own copy of this git repository or just serve your own `plugins.json` on your own network.
 
 Gitblit also supports loading multiple plugin registries.  Just place another **properly formatted** `.json` file in `${baseFolder}/plugins` and Gitblit will load that as an additional registry.
-
-### Mac OSX Fonts
-
-Gitblit's core SSH commands and those in the *powertools* plugin rely on ANSI border characters to provide a pretty presentation of data.  Unfortunately, the fonts provided by Apple - while very nice - don't work well with ANSI border characters.  The following public domain fixed-width, fixed-point, bitmapped fonts work very nicely.  I find the 6x12 font with a line spacing of ~0.8 to be quite acceptable.
-
-[6x12.dfont](6x12.dfont)
-[6x13.dfont](6x13.dfont)
-[7x13.dfont](7x13.dfont)
-[7x14.dfont](7x14.dfont)
-
diff --git a/src/site/setup_transport_ssh.mkd b/src/site/setup_transport_ssh.mkd
index 7b53624b..0f359105 100644
--- a/src/site/setup_transport_ssh.mkd
+++ b/src/site/setup_transport_ssh.mkd
@@ -5,6 +5,8 @@
 

 The SSH transport is a very exciting improvement to Gitblit.  Aside from offering a simple password-less, public key workflow the SSH transport also allows exposes a new approach to interacting with Gitblit: SSH commands.  The Gerrit and Android projects have to be thanked for providing great base SSH code that Gitblit has integrated.

 

+You may watch an Asciinema screencast of using the SSH transport and it's command infrastructure [here](https://asciinema.org/a/9342).

+

 ### Cloning & Pushing

 

 By default, Gitblit serves the SSH transport on port 29418, which is the same as Gerrit.  Why was 29418 chosen?  It's likely because it resembles the IANA port assigned to the git protocol (9418).

@@ -90,4 +92,12 @@ You may control the access permission for each SSH key.  This is more of a safet
 | R          | SSH key may be used to clone/fetch              |

 | RW         | SSH key may be used to clone/fetch and push     |

 

+### Mac OSX Fonts

+

+Many of Gitblit's SSH commands rely on ANSI border characters to provide a pretty presentation of data.  Unfortunately, the fonts provided by Apple - while very nice - don't work well with ANSI border characters.  The following public domain fixed-width, fixed-point, bitmapped fonts work very nicely.  I find the 6x12 font with a line spacing of ~0.8 to be quite acceptable.

+

+[6x12.dfont](6x12.dfont)

+[6x13.dfont](6x13.dfont)

+[7x13.dfont](7x13.dfont)

+[7x14.dfont](7x14.dfont)