parkr

6 ms·

31.
by parkr 14y ago
Using Jekyllwothout any ruby experience should be a snap. It's all controlled by the CLI. You create posts and run `jekyll` and you're in business.
32.
by parkr 14y ago
Why would you want to pay for people to come to your site? Don't you have to pay Amazon for that bandwidth usage?
33.
by parkr 14y ago
"Build time" means "generation time", or "compile time". It's the amount of time it takes Jekyll to build the site from the source to the static HTML, etc. Right now, it's really slow. If you have over 100 posts, it practically warrants a c
34.
The Immediate Future of Jekyll(blog.parkermoore.de)
47 points by parkr 14y ago|40 comments
35.
by parkr 14y ago
I worked at Cornell's College of Agriculture and Life Sciences, in their Communications Dept (Administrative) to completely rewrite http://cals.cornell.edu with Jekyll. Our workflow included Github, the Github desktop clients, SublimeText
36.
by parkr 14y ago
It's in his best interest to stay in the project. He'll have others working on it, and he'll want to ensure that he has some say in the direction of the project. You're safe to hold your breath. ;)
37.
Tom Preston-Werner: Development of Jekyll to be revived in 2013(github.com)
119 points by parkr 14y ago|32 comments
38.
by parkr 14y ago
Good point! This letter was written after I've done much of that. Unfortunately, nothing has been done yet. But that's definitely the attitude that one should take (unfortunately, it's just deteriorated over time). The reason I sent this em
39.
An Open Letter to Tom Preston-Werner(blog.parkermoore.de)
5 points by parkr 14y ago|2 comments
40.
by parkr 14y ago
I definitely disagree, especially given that their example for its efficiency is "table-based layouts". That's a huge no-no. Tables are for tabular data only.
41.
by parkr 14y ago
Too bad this has been discontinued! Would have been an awesome course to take.