ppl 4.0.3 → 4.0.5

data/gh-pages/_stylesheets/ppl/color.less

@@ -1,119 +0,0 @@
-
-@base03  : #002b36;
-@base02  : #073642;
-@base01  : #586e75;
-@base00  : #657b83;
-@base0   : #839496;
-@base1   : #93a1a1;
-@base2   : #eee8d5;
-@base3   : #fdf6e3;
-@yellow  : #b58900;
-@orange  : #cb4b16;
-@red     : #dc322f;
-@magenta : #d33682;
-@violet  : #6c71c4;
-@blue    : #268bd2;
-@cyan    : #2aa198;
-@green   : #859900;
-
-@lightGrey: #FAFAFA;
-@darkGrey: #F0F0F0;
-
-a:link, a:visited {
-  color: @blue;
-}
-
-body {
-  background-color: @lightGrey;
-  color: @base01;
-}
-
-div.content {
-  background-color: @lightGrey;
-}
-
-code {
-  background-color: @base3;
-}
-
-h2 { color: @base03; }
-h3 { color: @orange; }
-
-pre {
-  background-color: @base03;
-  color: @base2;
-  display: block;
-}
-
-.front-page {
-  h1.big-welcome, .little-welcome {
-    color: @base03;
-  }
-}
-
-.btn {
-	&.btn-primary {
-		background-color: @blue;
-		color: @base2;
-	}
-}
-
-.navbar {
-  .navbar-inner {
-    background-color: @darkGrey;
-  }
-  .brand {
-    color: @base03;
-    font-weight: bold;
-    text-shadow: none;
-  }
-}
-
-.command-list {
-  h2 {
-    color: inherit;
-  }
-}
-
-.navbar .nav > li > a {
-  color: @base02;
-}
-
-.navbar .nav > .active > a,
-.navbar .nav > .active > a:hover,
-.navbar .nav > .active > a:focus {
-  background-color: @orange;
-  color: @base3;
-}
-
-.nav-list  {
-  background-color: @darkGrey;
-  border: 1px solid rgb(221, 221, 221);
-}
-.nav-list > li:hover > a {
-  background-color: inherit;
-  color: inherit;
-}
-.nav-list > li.active:hover > a,
-.nav-list > li.active > a {
-  background-color: @orange;
-  color: @base3;
-}
-
-footer.global {
-  color: @base1;
-
-  a:link, a:visited {
-    color: @base0;
-  }
-}
-
-.nav-sidebar {
-  dt.active,
-  dt.active a,
-  dd.active {
-    background-color: @orange;
-    color: @base3;
-  }
-}
-

data/gh-pages/_stylesheets/ppl/layout.less

@@ -1,54 +0,0 @@
-
-.front-page {
-
-  .row.welcome {
-    margin-top: 32px;
-  }
-
-  h1.big-welcome {
-    margin: 32px 0 0 0;
-  }
- 
-  .little-welcome {
-    margin: 16px 0 0 0;
-  }
-
-  .row.what,
-  .row.latest {
-    margin-top: 32px;
-  }
-
-}
-
-h3 {
-  margin: 16px 0 8px 0;
-}
-
-.navbar .nav > li > a {
-  padding: 12px 15px 12px;
-}
-
-.content {
-  padding-top: 20px;
-  padding-bottom: 128px;
-}
-
-footer.global {
-  border-top: 1px solid #D4D4D4;
-  padding: 16px 0;
-}
-
-.nav-sidebar {
-  margin: 0;
-  dt { padding: 4px 4px 0px 4px; }
-  dd { padding: 0px 4px 4px 4px; }
-  dd { margin: 0 0 16px 0; }
-}
-
-dl.version-history {
-  dd {
-    margin: 0 0 1em 0;
-    padding: 0;
-  }
-}
-

data/gh-pages/_stylesheets/ppl/style.less

@@ -1,185 +0,0 @@
-
-@import "color.less";
-@import "layout.less";
-@import "typography.less";
-
-
-/*
-body {
-	background-color: #fdffdf;
-	color: #586e75;
-	font-family: "Inconsolata", sans-serif;
-	font-size: 18px;
-	margin: 0;
-	padding: 0;
-	line-height: 1.5;
-}
-
-code {
-	font-family: "Inconsolata", monospace;
-	font-size: inherit;
-}
-
-pre {
-	background-color: #073642;
-	border: 1px solid #002b36;
-	color: #93a1a1;
-	display: block;
-	font-family: "Ubuntu Mono", monospace;
-	font-size: 18px;
-}
-
-.front-page .welcome,
-.front-page .what {
-	margin-top: 64px;
-}
-
-.front-page h1.big-welcome {
-	color: #002b36;
-	font-size: 64px;
-	margin: 32px 0 32px 0;
-}
-
-.front-page .little-welcome {
-	color: #002b36;
-	font-size: 24px;
-}
-
-.front-page .welcome-example code {
-	line-height: 20px;
-	font-size: 20px;
-}
-
-.front-page .welcome-example .bash-prompt {
-	color: #859900;
-}
-
-.front-page .what h2 {
-	color: #002b36;
-	font-size: 20px;
-}
-
-.navbar-inner {
-	background-color: #fdf6e3;
-}
-
-.navbar .brand {
-	padding: 5px 20px 0px;
-}
-
-.navbar .nav > li > a {
-	color: #586e75;
-}
-
-.navbar .nav > .active > a,
-.navbar .nav > .active > a:hover,
-.navbar .nav > .active > a:focus {
-	background-color: #cb4b16;
-	color: #eee8d5;
-	text-shadow: none;
-}
-
-.nav-tabs.nav-stacked > li > a {
-	background-color: #fdf6e3;
-	border-color: none;
-	color: #586e75;
-}
-
-.nav-tabs.nav-stacked > li.active > a {
-	background-color: #cb4b16;
-	color: #eee8d5;
-}
-
-.commands h1 {
-	font-size: 32px;
-	font-weight: normal;
-	margin: 0 0 32px 0;
-}
-
-h2 {
-	font-size: 32px;
-	font-weight: normal;
-	margin: 0 0 32px 0;
-}
-
-h3 {
-	font-size: 20px;
-	font-weight: normal;
-}
-
-/*
-SOLARIZED HEX     16/8 TERMCOL  XTERM/HEX   L*A*B      RGB         HSB
---------- ------- ---- -------  ----------- ---------- ----------- -----------
-base03    #002b36  8/4 brblack  234 #1c1c1c 15 -12 -12   0  43  54 193 100  21
-base02    #073642  0/4 black    235 #262626 20 -12 -12   7  54  66 192  90  26
-base01    #586e75 10/7 brgreen  240 #585858 45 -07 -07  88 110 117 194  25  46
-base00    #657b83 11/7 bryellow 241 #626262 50 -07 -07 101 123 131 195  23  51
-base0     #839496 12/6 brblue   244 #808080 60 -06 -03 131 148 150 186  13  59
-base1     #93a1a1 14/4 brcyan   245 #8a8a8a 65 -05 -02 147 161 161 180   9  63
-base2     #eee8d5  7/7 white    254 #e4e4e4 92 -00  10 238 232 213  44  11  93
-base3     #fdf6e3 15/7 brwhite  230 #ffffd7 97  00  10 253 246 227  44  10  99
-yellow    #b58900  3/3 yellow   136 #af8700 60  10  65 181 137   0  45 100  71
-orange    #cb4b16  9/3 brred    166 #d75f00 50  50  55 203  75  22  18  89  80
-red       #dc322f  1/1 red      160 #d70000 50  65  45 220  50  47   1  79  86
-magenta   #d33682  5/5 magenta  125 #af005f 50  65 -05 211  54 130 331  74  83
-violet    #6c71c4 13/5 brmagenta 61 #5f5faf 50  15 -45 108 113 196 237  45  77
-blue      #268bd2  4/4 blue      33 #0087ff 55 -10 -45  38 139 210 205  82  82
-cyan      #2aa198  6/6 cyan      37 #00afaf 60 -35 -05  42 161 152 175  74  63
-green     #859900  2/2 green     64 #5f8700 60 -20  65 133 153   0  68 100  60
-
-
-
-header.global {
-	padding: 32px 0;
-}
-
-header.page {
-	color: #EEE8D5;
-	padding: 0 0 32px 0;
-}
-
-header.global h1,
-header.page h2,
-footer.global,
-article.page .content {
-	margin: 0 auto;
-	width: 800px;
-}
-
-header.global h1 a {
-	color: #859900;
-	font-size: 32px;
-	font-weight: normal;
-	text-decoration: none;
-}
-
-header.page h2 {
-	color: #859900;
-	color: #268bd2;
-	font-size: 20px;
-	font-weight: normal;
-}
-
-article.page .content {
-	color: #839496;
-	font-size: 18px;
-}
-
-article.page .content h3 {
-	color: #EEE8D5;
-	font-weight: normal;
-	font-size: 20px;
-	margin: 0 0 16px 0;
-}
-
-article.page .content p {
-	margin-top: 0;
-}
-
-footer.global {
-	color: #586E75;
-	margin: 32px auto;
-}
-
-*/
-

data/gh-pages/_stylesheets/ppl/typography.less

@@ -1,59 +0,0 @@
-
-body {
-  font-family: "Arvo", sans-serif;
-  font-size: 16px;
-  line-height: 24px;
-}
-
-code {
-  font-family: "Inconsolata", monospace;
-  font-size: 16px;
-}
-
-h1, h2, h3, h4, h5, h6 {
-  font-size: 1em;
-  font-weight: normal;
-}
-
-h2 {
-  font-size: 22px;
-  font-weight: bold;
-  small {
-    font-size: 16px;
-  }
-}
-
-h3 {
-  font-size: 18px;
-  font-weight: bold;
-}
-
-.front-page {
-  h1.big-welcome {
-    font-size: 32px;
-  }
-  .little-welcome {
-    font-size: 18px;
-  }
-}
-
-.command-list {
-  h2 {
-    font-size: 18px;
-    font-weight: normal;
-  }
-}
-
-.navbar .nav > .active > a,
-.navbar .nav > .active > a:hover,
-.navbar .nav > .active > a:focus {
-  text-shadow: none;
-}
-
-footer.global {
-  font-size: 12px;
-  a:link, a:visited {
-    text-decoration: underline;
-  }
-}
-

data/gh-pages/development/changelog/index.md

@@ -1,18 +0,0 @@
----
-title: Changelog
-layout: development
-section: development
----
-
-<dl class="version-history">
-{% for post in site.categories.changelog %}
-  <dt>
-    <a href="{{site.url}}/development/changelog/{{post.title}}">
-      {{post.title}}
-    </a>
-  </dt>
-  <dd>
-    {{post.summary}}
-  </dd>
-{% endfor %}
-</dl>

data/gh-pages/development/changelog/split.rb

@@ -1,51 +0,0 @@
-#!/usr/bin/env ruby
-
-require "rugged"
-
-repo = Rugged::Repository.new("/home/hnrysmth/src/ppl")
-index = File.read("development/changelog/index.md")
-
-changes = index.split("### ")
-
-def find_date(repo, version)
-  tag = repo.refs.find { |r| r.name == "refs/tags/#{version}" }
-  commit = repo.lookup(tag.target).target
-  commit.time
-end
-
-def generate_post(front_matter, body)
-  post = ["---"]
-  front_matter.each do |name, value|
-    post << "#{name}: #{value}"
-  end
-  post << "---"
-  post << ""
-  post << body
-
-  post.join "\n"
-end
-
-changes.each do |change|
-
-  version = change.scan(/^([0-9.]+)/)[0]
-  next if version.nil?
-
-  version = version[0]
-  date = find_date(repo, version).strftime("%Y-%m-%d")
-  body = change.split("\n")[2..-1].join("\n")
-
-  post = generate_post({
-    :title      => version,
-    :date       => date,
-    :layout     => "changelog",
-    :section    => "development",
-    :categories => "[changelog]",
-    :permalink  => "/development/changelog/#{version}",
-  }, body)
-
-  filename = "_posts/#{date}-#{version}.md"
-
-  File.open(filename, "w") { |f| f.write(post) }
-
-end
-

data/gh-pages/development/index.html

@@ -1,32 +0,0 @@
----
-title: Development
-layout: development
-section: development
----
-
-<p>
-  You'd like to contribute to the development of ppl? Great!
-  Here's a quick introduction.
-</p>
-
-<h3>Report A Bug</h3>
-<p>
-  This project uses Github Issues to track bug reports. The tracker is at
-  <a href="https://github.com/hnrysmth/ppl/issues">github.com/hnrysmth/ppl/issues</a>.
-</p>
-
-<h3>Get The Code</h3>
-<p>
-  The main source repository for ppl is hosted on GitHub at <a
-  href="https://github.com/hnrysmth/ppl">github.com/hnrysmth/ppl</a>.
-</p>
-
-<h3>Do Your Best</h3>
-<p>
-  For low-level code style issues relating to issues such as syntax and
-  indentation, <a href="https://github.com/styleguide/ruby">GitHub's Ruby
-  Styleguide</a> is the standard to follow*. This project doesn't necessarily
-  follow the guide perfectly, but pull requests that improve adherence to the
-  guide are welcomed whereas pull requests that stray even further are
-  discouraged.
-</p>

data/gh-pages/development/roadmap/index.md

@@ -1,15 +0,0 @@
----
-title: Roadmap
-layout: development
-section: development
----
-
-As of January 2018 this project is in quite a stable state, with no major
-increases in functionality planned. That being said, I'm not actually against
-adding more functionality to this thing if somebody out there feels like taking
-on the implementation work. I'm very very open to adding lots more stuff, just
-not interested in creating it myself.
-
-Please don't hesitate to get in touch if you have ideas for ppl that you want to
-build and contribute!
-

data/gh-pages/documentation/about/index.html

@@ -1,63 +0,0 @@
----
-title: About ppl
-layout: page
-section: documentation
----
-
-<h2>About ppl</h2>
-
-<div class="row">
-  <div class="span8">
-    <h3>Why?</h3>
-    <p>
-      ppl was created to address the need for a decentralized address book
-      storage system. There are a lot of different contact details storage
-      solutions out there and they all have their own strengths. What was
-      lacking was one that I felt I could count on to entrust with the "master
-      copy" of all the disparate contact information I possess.
-    </p>
-    <p>
-      It's also intended to address the apparent lack of a proper CLI address
-      book. There are people who enjoy the conversational nature of CLI
-      interaction. You ask "Whose birthdays are coming up soon?", the computer
-      answers immediately, and your interaction with the software is over with
-      no further requirements that you close a window or slide a widget.
-    </p>
-
-    <h3>Why the CLI?</h3>
-    <p>
-      The command-line is a good fit for address book software because data
-      about contacts is usually 100% plain text. It also works well because a
-      given user interaction with an address book typically consists of one
-      short operation: reading or writing a single piece of data. And since we
-      normally want to keep our address book data for our entire lives, the
-      command-line's immunity to the shifting sands of GUI toolkits and
-      discontinued SaaS products is a big plus.
-    </p>
-
-    <h3>Why Git?</h3>
-    <p>
-      ppl uses git as its storage backend. Git's decentralised approach really
-      suits this usage as it allows continued read/write access to the address
-      book in the face of network downtime and cloud outages. And because git
-      never destroys data, no botched sync attempt can permanently wipe an
-      entire address book by accident.
-    </p>
-
-    <h3>Who?</h3>
-    <p>
-      This software was conceived and created by me, Henry Smith.
-      I have a bunch of <a href="http://github.com/hnrysmth/">other stuff on
-      GitHub too</a>!
-    </p>
-
-    <h3>When?</h3>
-    <p>
-      According to the project's git logs, work on ppl first began on November
-      10th 2012. Apparently I had nothing more exciting to be doing at 11pm on a
-      Saturday night.
-    </p>
-
-  </div>
-</div>
-

data/gh-pages/documentation/commands/add/index.md

@@ -1,43 +0,0 @@
----
-title: ppl add Manual Page
-layout: command
-section: documentation
-command: add
----
-
-### Name
-
-ppl add - Add a new contact
-
-### Synopsis
-
-    ppl add <contact> <name>
-
-### Description
-
-This command adds a new contact to the address book. The first parameter,
-`<contact>`, is an alphanumeric string used to uniquely identify the contact
-within the address book. The second parameter, `<name>`, is the contact's actual
-name.
-
-The `<contact>` parameter must not already be in use as the identifier of
-another contact in the address book. Ideally you'll want to pick something short
-and easy to type, so if you're adding a contact named "John Doe", then "john" or
-"jdoe" might be good choices if they aren't already in use.
-
-The `<name>` parameter should be the full name of the contact, and is identical
-to its namesake expected by the [ppl name](../name) command.  Usually, this
-means it needs to be enclosed in quotation marks to indicate that all the words
-in the name are part of the same parameter. 
-
-The first word in the `<name>` will also be stored as the contact's given name,
-with the remainder of the string being treated as their family name.
-
-### Examples
-
-    ppl add jdoe "John Doe"
-
-### See Also
-
-[ppl name](../name)
-

data/gh-pages/documentation/commands/age/add/index.md

@@ -1,40 +0,0 @@
----
-title: ppl add Manual Page
-layout: command
-section: documentation
-command: add
----
-
-### Name
-
-ppl add - Add a new contact
-
-### Synopsis
-
-    ppl add <contact> <name>
-
-### Description
-
-This command adds a new contact to the address book. The first parameter,
-`<contact>`, is an alphanumeric string used to uniquely identify the contact
-within the address book. The second parameter, `<name>`, is the contact's actual
-name.
-
-The `<contact>` parameter must not already be in use as the identifier of
-another contact in the address book. Ideally you'll want to pick something short
-and easy to type, so if you're adding a contact named "John Doe", then "john" or
-"jdoe" might be good choices if they aren't already in use.
-
-The `<name>` parameter should be the full name of the contact, and is identical
-to its namesake expected by the [ppl name](../name) command.  Usually, this
-means it needs to be enclosed in quotation marks to indicate that all the words
-in the name are part of the same parameter. 
-
-### Examples
-
-    ppl add jdoe "John Doe"
-
-### See Also
-
-[ppl name](../name)
-