ppl 3.0.0 → 4.0.3

data/gh-pages/_posts/2013-04-23-1.24.0.md

@@ -0,0 +1,16 @@
+---
+title: 1.24.0
+summary: Preferred email addresses
+date: 2013-04-23
+layout: changelog
+section: development
+categories: [changelog]
+permalink: /development/changelog/1.24.0.html
+---
+
+Preferred email addresses and phone numbers can be marked as such as of
+`1.24.0`. This is good news if you have contacts with several similar addresses
+or numbers who only tend to check one of them. Now you can mark their preferred
+contact details with the `--preferred` flag and ppl will remember this
+preferential status for you. Preferred numbers and addresses are displayed with
+a `*` before them.

data/gh-pages/_posts/2013-04-24-1.25.0.md

@@ -0,0 +1,21 @@
+---
+title: 1.25.0
+summary: Customizable Output
+date: 2013-04-24
+layout: changelog
+section: development
+categories: [changelog]
+permalink: /development/changelog/1.25.0.html
+---
+
+This release brings the very basic first customizability to the output of ppl's
+commands. As of this version, it's possible to pass a `--format` option to [`ppl
+email`](/documentation/commands/email) and [`ppl
+ls`](/documentation/commands/ls) to specify the exact nature of the output
+required. Also part of this new version is the ability to configure preset
+format strings for [`ppl ls`](/documentation/commands/ls)  in `~/.pplconfig` and
+invoke them by name using the `--pretty` option.
+
+Obviously, this type of functionality has the potential to be added to just
+about all of ppl's output. In time, that will happen. For now, this gets the
+basic functionality out there for use.

data/gh-pages/_posts/2013-05-09-2.0.0.md

@@ -0,0 +1,33 @@
+---
+title: 2.0.0
+summary: ppl post overhaul
+date: 2013-05-09
+layout: changelog
+section: development
+categories: [changelog]
+permalink: /development/changelog/2.0.0.html
+---
+
+As a result of its backwards compatibility breaking changes, the overhaul of
+[ppl post](/documentation/commands/post) brings us to version 2.0.0. The
+behaviour and usage of this command have changed completely in order to cope
+with storing multiple postal addresses per contact.
+
+Here is a short summary of what has changed:
+
+* Running `ppl post` no longer lists contacts' full addresses.
+  Instead it lists contacts' address *IDs*.
+* Running `ppl post <contact>` no longer shows that contact's single postal
+  address. Instead it lists *all* that contact's postal addresses.
+* Postal address now have their own IDs. In order to change a postal address,
+  the ID of both the contact and the address itself must be given.
+* It is now possible to mark a postal address as "preferred", similarly to email
+  addresses and phone numbers.
+
+From a technical point of view, the downside of this release is the minor
+violation of [RFC2426](http://www.ietf.org/rfc/rfc2426.txt) that it introduces.
+The `ADR` field's `TYPE` attribute is intended as a means of tagging addresses
+with extra information such as "home" or "work", but as of 2.0.0, ppl
+misappropriates this attribute as the home of the unique ID of each postal
+address.
+

data/gh-pages/_posts/2013-05-09-version-2.0.0-released.md

@@ -0,0 +1,32 @@
+---
+title: ppl 2.0.0 released
+date: 2013-05-09
+layout: news
+section: news
+categories: [news]
+---
+
+It's been almost exactly six months since the very [first
+commit](https://github.com/hnrysmth/ppl/commit/e45917e06afd255271bad51ce216642e7277ce86),
+and I'm proud to announce that ppl has now reached the dizzy heights of version
+2.0.0! This is a milestone release for more than one reason, and I'm very happy
+that this project has made it to this point.
+
+Most important of all, the reason for the major version bump is that [ppl
+post](/documentation/commands/post) has been overhauled to support storing
+multiple postal addresses per contact. This overhaul introduced a number of
+backwards-incompatible changes to the behaviour of that command and ppl's
+underlying vCard integration, hence the bump to 2.0.0.
+
+The other reason why this is quite a milestone release is that support for
+multiple postal addresses was really the last major missing piece of the puzzle
+in terms of core ppl functionality. There are still some bits and pieces of
+vCard functionality that aren't yet exposed, but those that remain now are
+mostly edge cases. It's satisfying to see ppl approach the functionality goals I
+had for it when I started.
+
+This is by no means the end of the development process. There's a long way to go
+still in terms of ppl's flexibility for integration with other software. In the
+meantime, this version represents a big step forward, and the culmination of six
+months of hard work.
+

data/gh-pages/_posts/2013-07-20-2.1.0.md

@@ -0,0 +1,36 @@
+---
+title: 2.1.0
+summary: Better name management
+date: 2013-07-20
+layout: changelog
+section: development
+categories: [changelog]
+permalink: /development/changelog/2.1.0.html
+---
+
+With thanks to [@pigmonkey](https://github.com/pigmonkey) for raising this as
+[issue #42](https://github.com/hnrysmth/ppl/issues/42) on GitHub, version 2.1.0
+brings increased control over the names of contacts. This is intended to improve
+interoperability with other address book software, including the Android
+system's contact list.
+
+Short, lower case contact IDs are great for a CLI program, but on a phone, you
+probably want to see full names. This update provides full access to all the
+bits & pieces of vCard's `N` (name) field:
+
+* Family name(s)
+* Middle name(s)
+* Given name(s)
+* Prefix
+* Suffix
+
+See the documentation of [ppl name](/documentation/commands/name/) for more
+details on how to use this new functionality.
+
+Also included is some slightly different behaviour under the hood of [ppl
+add](/documentation/commands/name/).  This command now attempts to "have a
+guess" at the structure of the name of a newly-added contact. It'll treat the
+first word of the full name as the contact's given name, and the rest of the
+string as their family name. This is a shamefully anglocentric approach to name
+parsing, but at least it's a start.
+

data/gh-pages/_posts/2013-07-20-2.2.0.md

@@ -0,0 +1,20 @@
+---
+title: 2.2.0
+summary: ppl scrape overwrite prevention
+date: 2013-07-20
+layout: changelog
+section: development
+categories: [changelog]
+permalink: /development/changelog/2.2.0.html
+---
+
+Thanks again to [@pigmonkey](https://github.com/pigmonkey) for [issue #32](https://github.com/hnrysmth/ppl/issues/32),
+reporting some unhelpful destructive behaviour in [ppl
+scrape](/documentation/commands/scrape/). In this version, some additional
+checking has been added to that command to prevent it from overwriting existing
+contacts.
+
+In the event that the scraped contact ID happens to match that of an existing
+contact, ppl scrape will now notice this collision and append numbers to the new
+ID until it no longer matches any existing contact's IDs.
+

data/gh-pages/_posts/2013-10-12-2.3.0.md

@@ -0,0 +1,19 @@
+---
+title: 2.3.0
+summary: ppl grep
+date: 2013-10-12
+layout: changelog
+section: development
+categories: [changelog]
+permalink: /development/changelog/2.3.0.html
+---
+
+With thanks to [@ajford](https://github.com/ajford) for the excellent [feature
+request](https://github.com/hnrysmth/ppl/issues/43), version 2.3.0 brings a new
+command: [ppl grep](/documentation/commands/grep/). This command leverages the
+extremely high speed search `git grep` repository search in order to provide
+near-instant search results.
+
+    $ ppl grep smith
+    john.vcf:EMAIL:john.smith@example.org
+

data/gh-pages/_posts/2014-03-30-2.3.1.md

@@ -0,0 +1,25 @@
+---
+title: 2.3.1
+summary: Simple Bug Fixes
+date: 2014-03-30
+layout: changelog
+section: development
+categories: [changelog]
+permalink: /development/changelog/2.3.1.html
+---
+
+Once again, I'm grateful to [@alexGschaider] for his patience. This minor
+version fixes a couple of annoying little problems that he's bumped into.
+
+The first problem was a pretty terrible error message which was displayed when a
+`.vcf` file contains invalid vCard data. This has now been fixed, and the error
+message replaced with something much more sensible.
+
+    $ ppl show badcontact
+    ppl: badcontact.vcf contains invalid data
+
+The second was yet another `Encoding::CompatibilityError`, just like back in the
+bad old days before ppl even supported UTF-8 at all. Hopefully this will be the
+last one of those now!
+
+[@alexGschaider]: https://github.com/axelGschaider

data/gh-pages/_posts/2015-01-05-2.3.2.md

@@ -0,0 +1,18 @@
+---
+title: 2.3.2
+summary: scrape output fix
+date: 2015-01-05
+layout: changelog
+section: development
+categories: [changelog]
+permalink: /development/changelog/2.3.2.html
+---
+
+I'm very grateful to [@hobarrera](https://github.com/hobarrera) for contributing
+this fix to [ppl scrape](/documentation/commands/scrape/). A simple mistake in
+the output formatting code was causing it to appear slightly garbled, like this:
+
+    Add "Hugo Osvaldo Barrera #<Ppl::Entity::EmailAddress:0x00000001ffbd28>>"
+    to your address book [Y/n]?
+
+So thanks for fixing that, Hugo!

data/gh-pages/_posts/2015-12-03-get-involved.md

@@ -0,0 +1,29 @@
+---
+title: Get Involved!
+date: 2015-12-03
+layout: news
+section: news
+categories: [news]
+---
+
+The time has come to give this project a nudge into a slightly different mode of
+operation. Enough people are interested in the long term health of this little
+CLI app that I think it'd benefit from opening the doors a bit to potential
+collaborators and maintainers. So I've converted the project into a proper
+[GitHub organization](https://github.com/hnrysmth) and I'm inviting you to
+come and join it.
+
+I see lots of people come and go with great ideas for this project. I love 99%
+of the ideas and suggestions that pop up but I just can't keep up with all the
+different demands on my time. That's the bottleneck that's holding the project
+back and it's silly, really.
+
+For a while I've been wanting to do something about this. If you want to help
+out in any way, however small, speak up on GitHub, [email me](mailto:henry@henrysmith.org),
+or get in touch on [Twitter](https://twitter.com/hnrysmth). I'd love to add you
+to the organization and let you *just get started* making your ideas happen.
+Even if you just like the project, but don't have any immediate plans to do
+anything in particular, that's fine! If you've never contributed to an open
+source project before, don't let that put you off. Everyone's welcome!
+
+

data/gh-pages/_posts/2015-12-05-2.3.3.md

@@ -0,0 +1,16 @@
+---
+title: 2.3.3
+summary: non-ASCII input fix
+date: 2015-12-05
+layout: changelog
+section: development
+categories: [changelog]
+permalink: /development/changelog/2.3.3.html
+---
+
+This release is [@tba](https://github.com/tba)'s [non-ASCII input fix PR](https://github.com/hnrysmth/ppl/pull/56)
+
+It's a fix enabling ppl to save non-ASCII names when scraping contact data
+from emails.
+
+It took altogether too long for me to merge this and I apologise!

data/gh-pages/_posts/2016-01-02-2.4.0.md

@@ -0,0 +1,19 @@
+---
+title: 2.4.0
+summary: Better commit author
+date: 2016-01-12
+layout: changelog
+section: development
+categories: [changelog]
+permalink: /development/changelog/2.4.0.html
+---
+
+If you've ever looked at the commit history that ppl generates in your address
+book you'll have noticed the ugly-looking commit author. [@drewbug] certainly
+noticed and took the time to do something about it.
+
+As of this version, ppl pulls in your Git config and uses your `user.name` and
+`user.email` if available. If not, it falls back to the old (ugly) author
+generation.
+
+[@drewbug]: https://github.com/drewbug

data/gh-pages/_posts/2017-05-01-2.4.1.md

@@ -0,0 +1,12 @@
+---
+title: 2.4.1
+summary: Upgrade to rugged ~> v0.24.0
+date: 2017-05-01
+layout: changelog
+section: development
+categories: [changelog]
+permalink: /development/changelog/2.4.1.html
+---
+
+This release is just a merge of one PR from [@acant](https://github.com/acant). It upgrades to a much more
+modern version of the rugged gem.

data/gh-pages/_posts/2017-10-23-sleep-mode.md

@@ -0,0 +1,18 @@
+---
+title: Sleep Mode
+date: 2017-10-23
+layout: news
+section: news
+categories: [news]
+---
+
+This project seems to be in a good stable state. There's a small active
+userbase who are mostly content with the software as-is. Not a lot of
+maintenance or feature work is necessary these days and I can't justify
+spending money on a domain for a project that's just chilling like this.
+
+I'm converting the whole thing into a single, easy-to-look-after repo in my
+own personal GitHub account and disabling autorenew on `ppladdressbook.org`.
+Wanna make it clear that I consider this a fairly decent set of circumstances
+for the project to be in btw. It mostly just works and that's for the best
+cos I don't really have a lot of time to maintain and fix it any more.

data/gh-pages/_posts/2018-01-03-3.0.1.md

@@ -0,0 +1,12 @@
+---
+title: 3.0.1
+summary: Fix name deletion bug
+date: 2018-01-03
+layout: changelog
+section: development
+categories: [changelog]
+permalink: /development/changelog/3.0.1.html
+---
+
+Fix for a [name deletion bug](https://github.com/hnrysmth/ppl/issues/74) reported by [@the-reverend](https://github.com/the-reverend).
+

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

@@ -0,0 +1,119 @@
+
+@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;
+  }
+}
+