2015-03-02 21:47:19 : Updating layout for new blocks.
»
Find 3a8c3faf3cf2ac8144b1050f4c387551018b567b on GitHub.
Updating layout for new blocks.
summary: Because nothing happens all at once.
date: 2013-01-31 14:56:39
---
{+{% block post %}+}
{% mark excerpt %}
Inspired by [@jsvine's](https://twitter.com/jsvine) experiments in version-control at [drafts.jsvine.com](http://drafts.jsvine.com), I thought I'd expose some of the bones that tick beneath my [site](http://samjacoby.com/posts/2012/8/21/hello-world/). I run these pages through the [Hyde](http://hyde.github.com) static-site generator--[Jekyll's](https://github.com/mojombo/jekyll) underloved Pythonic-cousin--which despite being a little complex for the job, I like.
{% endmark %}
@@ -16,3 +17,4 @@ At any rate, you'll now see a 'Change History' on the bottom of each page I've w
The plug-in, itself, is [here](https://github.com/samjacoby/hyde/commit/a92073bb46775499e1d510c2c71009ddd8101218) in a not-very-palatable form. Pretty minimal, but you get the idea. The syntax-highlighting is a smidgen of jQuery.
{{ macros.render_footnote("github-1", "†", "My sister pointed out that _git_ looks suspiciously-like a typo for _get_. It is not. Git is a popular piece of software that allows you to keep track of all of the edits you make on text files and easily collaborate and share your changes with others. While originally intended for software development, it's finding uses in a number of projects.")}}
{+{% endblock %}+}
2015-02-16 14:28:44 : Adding excerpts to all posts, basically.
»
Find 07a57fe3ebb846616f1ae7d0aa3cfbc0f1920d57 on GitHub.
Adding excerpts to all posts, basically.
summary: Because nothing happens all at once.
date: 2013-01-31 14:56:39
---
{+{% mark excerpt %}+}
Inspired by [@jsvine's](https://twitter.com/jsvine) experiments in version-control at [drafts.jsvine.com](http://drafts.jsvine.com), I thought I'd expose some of the bones that tick beneath my [site](http://samjacoby.com/posts/2012/8/21/hello-world/). I run these pages through the [Hyde](http://hyde.github.com) static-site generator--[Jekyll's](https://github.com/mojombo/jekyll) underloved Pythonic-cousin--which despite being a little complex for the job, I like.
{+{% endmark %}+}
I mostly use [git](http://github.com){{ macros.render_footnote("github-1", "†") }} as a glorified save button, not a collaborative tool (on this site at least)--so all I needed to do was expose my changesets (already online on [GitHub](http://https://github.com/samjacoby/samjacoby.com/)).
2013-04-10 10:37:28 : Just some tweaks. Adding (?) to tracking.
»
Find c5ca1d768138928e0cd6c67194451d873ad663c9 on GitHub.
Just some tweaks. Adding (?) to tracking.
---
Inspired by [@jsvine's](https://twitter.com/jsvine) experiments in version-control at [drafts.jsvine.com](http://drafts.jsvine.com), I thought I'd expose some of the bones that tick beneath my [site](http://samjacoby.com/posts/2012/8/21/hello-world/). I run these pages through the [Hyde](http://hyde.github.com) static-site generator--[Jekyll's](https://github.com/mojombo/jekyll) underloved Pythonic-cousin--which despite being a little complex for the job, I like.
I mostly use [git](http://github.com){{ macros.render_footnote("github-1", "†") }} as a glorified save button, not a collaborative tool (on this site at least)--so all I needed to do was expose my changesets (already online on [-[GitHub]](http://https://github.com/samjacoby/samjacoby.com/)).-]{+[GitHub](http://https://github.com/samjacoby/samjacoby.com/)).+}
I slapped together a small plugin that parses the logs of the repo that backs the site, and renders them on the page per-file in a reasonably-digestible manner. It would've made more sense to be using mercurial (which is written in Python), but alas, GitHub is too damn good.
@@ -13,4 +13,4 @@ At any rate, you'll now see a 'Change History' on the bottom of each page I've w
The plug-in, itself, is [here](https://github.com/samjacoby/hyde/commit/a92073bb46775499e1d510c2c71009ddd8101218) in a not-very-palatable form. Pretty minimal, but you get the idea. The syntax-highlighting is a smidgen of jQuery.
{{ macros.render_footnote("github-1", "†", "My sister pointed out that _git_ looks suspiciously-like a typo for [-_get_, so it's worth mentioning that git-]{+_get_. It is not. Git+} is a popular piece of software that allows you to keep track of all of the edits you make on text files and easily collaborate and share your changes with [-others.")}}-]{+others. While originally intended for software development, it's finding uses in a number of projects.")}}+}
2013-02-01 12:52:39 : A clarification for Sarah.
»
Find 0d9c168a4dba090b23791f2aef551a00b8390b52 on GitHub.
A clarification for Sarah.
---
Inspired by [@jsvine's](https://twitter.com/jsvine) experiments in version-control at [drafts.jsvine.com](http://drafts.jsvine.com), I thought I'd expose some of the bones that tick beneath my [site](http://samjacoby.com/posts/2012/8/21/hello-world/). I run these pages through the [Hyde](http://hyde.github.com) static-site generator--[Jekyll's](https://github.com/mojombo/jekyll) underloved Pythonic-cousin--which despite being a little complex for the job, I like.
I mostly use [-git-]{+[git](http://github.com){{ macros.render_footnote("github-1", "†") }}+} as a glorified save button, not a collaborative tool (on this site at least)--so all I needed to do was expose my changesets (already online on [-[GitHub](http://https://github.com/samjacoby/samjacoby.com/)).-]{+[GitHub]](http://https://github.com/samjacoby/samjacoby.com/)).+}
I slapped together a small plugin that parses the logs of the repo that backs the site, and renders them on the page per-file in a reasonably-digestible manner. It would've made more sense to be using mercurial (which is written in Python), but alas, GitHub is too damn good.
At any rate, you'll now see a 'Change History' on the bottom of each page I've worked on--and if you're so inclined, can thumb-through my misspellings, fudged-dates, and all the rest. Tantalizing.
The plug-in, itself, is [here](https://github.com/samjacoby/hyde/commit/a92073bb46775499e1d510c2c71009ddd8101218) in a not-very-palatable form. Pretty minimal, but you get the idea. The syntax-highlighting is a smidgen of jQuery.
{+{{ macros.render_footnote("github-1", "†", "My sister pointed out that _git_ looks suspiciously-like a typo for _get_, so it's worth mentioning that git is a popular piece of software that allows you to keep track of all of the edits you make on text files and easily collaborate and share your changes with others.")}}+}
2013-01-31 17:12:15 : Fix minor typo "us" -> "use".
»
Find f5aa1721e2f5640faf548a14056e5bd52571c334 on GitHub.
Fix minor typo "us" -> "use".
---
Inspired by [@jsvine's](https://twitter.com/jsvine) experiments in version-control at [drafts.jsvine.com](http://drafts.jsvine.com), I thought I'd expose some of the bones that tick beneath my [site](http://samjacoby.com/posts/2012/8/21/hello-world/). I run these pages through the [Hyde](http://hyde.github.com) static-site generator--[Jekyll's](https://github.com/mojombo/jekyll) underloved Pythonic-cousin--which despite being a little complex for the job, I like.
I mostly [-us-]{+use+} git as a glorified save button, not a collaborative tool (on this site at least)--so all I needed to do was expose my changesets (already online on [GitHub](http://https://github.com/samjacoby/samjacoby.com/)).
I slapped together a small plugin that parses the logs of the repo that backs the site, and renders them on the page per-file in a reasonably-digestible manner. It would've made more sense to be using mercurial (which is written in Python), but alas, GitHub is too damn good.
2013-01-31 17:02:35 : Adding and revising so I sound smarter.
»
Find df390c9e8431e591c942ccfd5e757422a70983b6 on GitHub.
Adding and revising so I sound smarter.
summary: Because nothing happens all at once.
date: 2013-01-31 14:56:39
---
Inspired by [@jsvine's](https://twitter.com/jsvine) experiments in version-control at [drafts.jsvine.com](http://drafts.jsvine.com), I thought I'd expose some of the bones that tick beneath [-this-]{+my+} [site](http://samjacoby.com/posts/2012/8/21/hello-world/). I [-put-together-]{+run these pages through the [Hyde](http://hyde.github.com) static-site generator--[Jekyll's](https://github.com/mojombo/jekyll) underloved Pythonic-cousin--which despite being a little complex for the job, I like. +}
{+I mostly us git as a glorified save button, not a collaborative tool (on this site at least)--so all I needed to do was expose my changesets (already online on [GitHub](http://https://github.com/samjacoby/samjacoby.com/)).+}
{+I slapped together+} a small plugin that parses the [-git repositories-]{+logs of the repo+} that [-have been backing this site for awhile,-]{+backs the site,+} and [-throws-]{+renders+} them[-up-] on the [-page. You'll-]{+page per-file in a reasonably-digestible manner. It would've made more sense to be using mercurial (which is written in Python), but alas, GitHub is too damn good. +}
{+At any rate, you'll+} now see a [-`Change History` towards-]{+'Change History' on+} the bottom of [-every-]{+each+} page I've worked [-on. This one's got it.-]{+on--and if you're so inclined, can thumb-through my misspellings, fudged-dates, and all the rest. Tantalizing.+}
{+The plug-in, itself, is [here](https://github.com/samjacoby/hyde/commit/a92073bb46775499e1d510c2c71009ddd8101218) in a not-very-palatable form. Pretty minimal, but you get the idea. The syntax-highlighting is a smidgen of jQuery.+}
2013-01-31 16:19:55 : Adding post on Git tracking.
»
Find cd6f5902d3168e860d22af3046541be39c70b966 on GitHub.
Adding post on Git tracking.
@@ -0,0 +1,6 @@
{+---+}
{+title: Tracking Changes +}
{+summary: Because nothing happens all at once. +}
{+date: 2013-01-31 14:56:39+}
{+---+}
{+Inspired by [@jsvine's](https://twitter.com/jsvine) experiments in version-control at [drafts.jsvine.com](http://drafts.jsvine.com), I thought I'd expose some of the bones that tick beneath this [site](http://samjacoby.com/posts/2012/8/21/hello-world/). I put-together a small plugin that parses the git repositories that have been backing this site for awhile, and throws them up on the page. You'll now see a `Change History` towards the bottom of every page I've worked on. This one's got it.+}