Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Newer
Older
100644 38 lines (29 sloc) 1.616 kb
9d507e5a »
2011-01-02 initial commit
1 ---
2 title: No comments
3 ---
4 ## In-between transitions
5
6 So, I moved my blog home from [use Perl](http://use.perl.org/~masak/journal)
7 to here. The actual blog posts have already been successfully ported;
8 see [this post](http://strangelyconsistent.org/blog/its-just-a-tree-silly)
9 for a bit about the process.
10
11 What remains is the comments from the old blog. It's the same trick there,
12 really. I haven't done it yet because comments weren't part of the minimal
13 featureset I needed to get the blog going. But they're pretty high on my list.
14
15 In summary, here's the plan:
16
17 1. Convert the comments from the old blog and put them in place.
18 2. Create a little form on blog posts, enabling readers to make new comments.
19
20 ## Waitwait... isn't this site static?
21
22 Well, yes. Wouldn't it be a nice little trick to allow comments on a statically
23 generated blog? I'm sure it's not unheard of.
24
25 What I want to do is this. A user types in a comment, using Markdown that
26 gets rendered in real time as HTML. (stackoverflow uses this, it's a program
27 called [Showdown](http://attacklab.net/showdown/). I like the idea a lot.) As
28 the user hits "submit", a message pops up saying "thanks, your comment has
29 been submitted for review", making it clear that it'll not show up on the
30 website at once.
31
32 Comments that were just made sit in a special quarantine directory waiting to
33 be reviewed and approved. This could even be done online in some way, and
34 approved using a login and password. An offline script (invoked manually)
35 pulls down the approved comments, and makes sure it appears the next time the
36 blog is regenerated.
37
38 That's the plan.
Something went wrong with that request. Please try again.