Yep, you nailed it. We also sort by what you haven't read, so you'll scroll past each article, then you'll be able to search for it because you know it exists. We've experimented with an array of different hieratical and graph structures, but they all grow stale and misleading.

The issue with written instructions is that people hide it in nested folders, deep outlines, and walls of text. This creates a death spiral, why write when no-one reads. I've been experimenting with different solutions to visible internal documentation and are about to release the culmination of my efforts in a product called Triqla. http://triqla.com

Checkout the -v option :)

That doesn't seem to do anything for me. What am I looking for?

You want the -v option to git commit, not to git add.

git commit -v displays the patch below the message part you're writing, so that you can review the patch as you write the message.

This BEST stuff looks great and I'm looking forward to using it. But it will be a nightmare to search for if this stuff takes off. You should consider changing it to something more unique.

Oo this is great everyone! I really like that sexy Stribe documentation. Thank you

You should hack in Swift. Would bring extreme amounts of traffic as Swift only runs on OSX and behind paywall.