Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Comparing changes

Choose two branches to see what's changed or to start a new pull request. If you need to, you can also compare across forks.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also compare across forks.
base fork: BenWard/benward
base: fa8c9975e3
...
head fork: BenWard/benward
compare: c3f13ba4d5
  • 3 commits
  • 4 files changed
  • 0 commit comments
  • 1 contributor
View
12 jekyll/_includes/share.html
@@ -1,7 +1,11 @@
{% capture short_url %}{{site.shortdomain}}/{{page.global_date | date: "%s" | base_60}}{% endcapture %}
<div id="respond" class="share">
- <h2>Share this page</h2>
- <a class="twitter-share-button" href="http://twitter.com/share?text={{page.title | cgi_escape}}&amp;via={{site.author.twitter | cgi_escape}}" data-count="none" data-align="right">Tweet</a>
- <kbd><a rel="canonical nofollow" href="{{site.url}}{{page.url}}">{{site.url}}{{page.url}}</a></kbd>
- <!--<kbd><a rel="shortlink nofollow" href="{{short_url}}">{{short_url}}</a></kbd>-->
+ <h2>Share &amp; Respond</h2>
+ <p>To share this entry, or reference it in a post of your own, link to the following:</p>
+ <p>Permalink: <kbd><a rel="canonical nofollow" href="{{site.url}}{{page.url}}">{{site.url}}{{page.url}}</a></kbd>
+ <!--Shortlink: <kbd><a rel="shortlink nofollow" href="{{short_url}}">{{short_url}}</a></kbd>--></p>
+ <p>
+ <a class="twitter-share-button" href="http://twitter.com/share?text={{page.title | cgi_escape}}&amp;via={{site.author.twitter | cgi_escape}}" data-count="none" data-align="right">Tweet</a>
+ <a class="twitter-mention-button" href="http://twitter.com/intent/tweet?screen_name={{site.author.twitter | cgi_escape}}&amp;related={{site.author.twitter | cgi_escape}}" data-count="none" data-align="right">Tweet to @{{site.author.twitter}}</a>
+ </p>
</div>
View
6 jekyll/_layouts/archive_year.html
@@ -5,7 +5,6 @@
<header>{% include archive_navigation.html %}</header>
<h1>Posts from <time>{{page.period['year']}}</time></h1>
{% assign section = "0" %}
- {% assign subsect = "0" %}
{% for post in page.posts %}
{% capture month %}{{post.date | date: '%m'}}{% endcapture %}
{% capture day %}{{post.date | date: '%e'}}{% endcapture %}
@@ -22,10 +21,7 @@
{% endif %}
<li><article class="hentry">
<h3><a rel="bookmark" href="{{post.url}}">{{post.title}}</a></h3>
- {% if subsect != day %}
- <time class="published" datetime="{{post.global_date}}">{{post.global_date | date: '%e'}}</time>
- {% assign subsect = day %}
- {% endif %}
+ <time class="published" datetime="{{post.global_date}}">{{post.global_date | date: site.dateformat}}</time>
<div class="entry-summary">{% if post.summary %}{{post.summary}}{% else %}{{post.excerpt}}{% endif %}</div>
</article></li>
{% endfor %}
View
14 jekyll/_posts/blog/2012/2012-03-24-unfinished-again.md
@@ -2,9 +2,9 @@
layout: blog
category: blog
title: "Unfinished Again"
-date: "2012-03-24T19:30:00-07:00"
+date: "2012-03-25T16:49:00-07:00"
summary: "This site has been here in some form or other for ten years, most of them as a blog, and seven of those running WordPress. But from time to time you just have to tear it up and start again. Here then begins an adventure in Jekyll-powered, git-stored, version-controlled blogging. Not that it will ever end."
-tags: ["technology", "blogging"]
+tags: [blogging, wordpress, jekyll]
geo:
name: "San Francisco"
xy: 37.77493,122.41942
@@ -26,15 +26,15 @@ I set up WordPress with Textile, so all my posts from 2004 through 2010 are writ
## Comments.
-The commentary on commentary has hit popularism this year, but it boils down to three tangential things that arrive in the same place:
+The commentary on commentary has been a popular meme already this year, but for me it boils down to three tangential things that arrive in the same place:
-* Often the quality of comments left on a site are low. Of those that are of high quality, they're trapped in a packed stream of all the others.
+* Often the quality of comments left on my site are low. Of those that are of high quality, they're trapped in a packed stream of all the others.
* Filtering spam is a ridiculous pass-time.
-* Philosophically, I'm an own your words kinda guy. I think that ideally, everyone should have their own space on the web and they should respond to one another by expanding discussion with something of substance. I think that since hosted blog services are now commodities: Tumblr, WordPress, Posturous, et al, and that this is an accessible enough option for people. For communicating the proliferation of these distributed discussions (and for pieces of feedback that don't warrant an entire post), we have made up for the automated spam infested failures of Trackback and Pingback with the manual, personal success of Twitter.
+* Philosophically, I believe you should own your words. I think that ideally, everyone should have their own space on the web and they should respond to one another by expanding discussion with something of substance. I think that since hosted blog services are now commodities: Tumblr, WordPress, Posturous, et al, and that this is an accessible enough option for people. For communicating the proliferation of these distributed discussions (and for pieces of feedback that don't warrant an entire post), we have made up for the automated spam infested failures of Trackback and Pingback with the manual, human success of Twitter.
Together, these justify not having comments on my blog. All the old discussions are still here—of course—and all have their original `#comment-1234` permalinks on the pages, but they've been exported into the entries now, and I'm not hosting any subsequent discussion.
-<aside>All that said, a curious thing happened in the course of rebuilding all my pages though, which is that I went and read a lot of old comments and found them regularly delightful. I wouldn't say that my removal of the function is necessarily final.</aside>
+<aside><p>That said, a curious thing happened in the course of rebuilding all my pages, which is that I went and read a lot of old comments and found a lot of them delightful. I wouldn't say that my removal of the function is necessarily final.</p></aside>
In place of commenting on the site, I'd like people to message me on Twitter (<a href="https://twitter.com/intent/tweet?related=BenWard&amp;screen_name=BenWard">like this</a>), or other systems (email, IM, etc.), and simply tell me about interesting follow-ups they have or have seen. I'm an admirer of other sites (such as [Matt Gemmell](http://mattgemmell.com/2011/11/29/comments-off/)'s, and [John Gruber](http://daringfireball.net)'s) who don't have comments, but who make an effort to post follow-up entires documenting expansion and dissent. I'd like to give it a try.
@@ -48,7 +48,7 @@ The second benefit of the content being in git rather than a database is that th
---
-There's an awful lot more to cover about the how and why of building a site this way. There are costs to it to, of course. For now though, I'm really pleased with my redesign. There's infinitely more to do, but I rather hope you like what I've done with it. There's a lot more to write, so here are some forthcoming posts that you should hassle me about if it seems like too much time has passed:
+There's an awful lot more to write about the how and why of building a site this way. There are costs to it to, of course. For now though, I'm really pleased with my redesign. There's more to do, and it will never be “done”, but I rather hope you like what I've made. Here are some forthcoming post summaries that you should hassle me about if it seems like I've forgotten to write them:
* Experience with Jekyll, ruby, git and how everything currently in the back works. There are various hacks and plug-ins I've made for Jekyll I can repackage and share.
* The design philosophy behind the site. It's very simple, and I want to draw attention to how and why. There's no numerical pagination, for example.
View
32 jekyll/css/six.css
@@ -106,6 +106,11 @@ blockquote {
border-width: 0 0 0 4px;
}
+article aside {
+ margin-left: -16px;
+ font-size: 80%;
+}
+
/* Standard margin for article block content: */
p, dl, ol, ul {
margin: 0 0 16px;
@@ -191,6 +196,7 @@ article.hentry nav a {
display: inline-block;
text-align: center;
margin: 16px 0;
+ white-space: nowrap;
}
section.hfeed nav a:first-child,
@@ -200,7 +206,7 @@ article nav a:first-child {
section.hfeed nav a:last-child,
article nav a:last-child {
text-align: right;
- position: relative; margin-right: -3%; /* Adjust right-align for rounding */
+ float: right;
}
section.hfeed nav a,
@@ -219,16 +225,6 @@ section.hfeed.recent nav a {
position: relative;
}
-.archives.annual section li time {
- position: absolute;
- top: 2px;
- left: -48px;
- font-weight: bold;
- font-size: 32px;
- width: 40px;
- padding-right: 8px;
-}
-
/** Section: Page Footer */
body > footer {
font-size: 80%;
@@ -324,15 +320,9 @@ ul.tags li a {
.share {
position: relative;
}
-.share .twitter-share-button {
- position: absolute;
- right: 0;
-}
-.share dl {
- margin-right: 100px;
+.share p {
+ font-size: 80%;
}
-.share dt { margin: 4px 0; }
-.share dd { margin: 0; }
.share kbd {
font-family: Verdana, sans-serif;
font-size: 80%;
@@ -388,5 +378,7 @@ ul.tags li a {
}
section.hfeed header,
article header { margin: -16px -16px 16px -16px; }
-
+ section.hfeed nav a,
+ article.hentry nav a { font-size: 80%; }
+ article > aside { margin-left: -8px; }
}

No commit comments for this range

Something went wrong with that request. Please try again.