Using Jekyll and GitHub Pages for Our Site
developmentseed.org
Using Jekyll and GitHub Pages for Our Site
1–10 of 38 posts
Re: Using Jekyll and GitHub Pages for Our Site
#2I do the same, except I host at NearlyFreeSpeech.NET, which just feels right.
Re: Using Jekyll and GitHub Pages for Our Site
#3Re: Using Jekyll and GitHub Pages for Our Site
#4Still, I guess I can hack that into the code somehow…
One "prepackaged" jekyll configuration that looks quite interesting is Octopress: http://octopress.org/
Re: Using Jekyll and GitHub Pages for Our Site
#5What I always found a bit annoying about jekyll (at least without plugin or forks) is that something like http://developmentseed.org/blog/2011/ or http://developmentseed.org/blog/2011/09/ doesn't work, i.e. the set of archive pages is pretty limited. You get one big one, and then a simple numeric pagination. I used some perl script ages ago (blosxom?), and it did just that. Still, I guess I can hack that into the cod…
https://github.com/josegonzalez/josediazgonzalez.com/tree/ma...
Re: Using Jekyll and GitHub Pages for Our Site
#6Re: Using Jekyll and GitHub Pages for Our Site
#7What I always found a bit annoying about jekyll (at least without plugin or forks) is that something like http://developmentseed.org/blog/2011/ or http://developmentseed.org/blog/2011/09/ doesn't work, i.e. the set of archive pages is pretty limited. You get one big one, and then a simple numeric pagination. I used some perl script ages ago (blosxom?), and it did just that. Still, I guess I can hack that into the cod…
Would/do Jose Diaz-Gonzalez's plug-ins solve your problem? https://github.com/josegonzalez/josediazgonzalez.com/tree/ma...
Re: Using Jekyll and GitHub Pages for Our Site
#8What I always found a bit annoying about jekyll (at least without plugin or forks) is that something like http://developmentseed.org/blog/2011/ or http://developmentseed.org/blog/2011/09/ doesn't work, i.e. the set of archive pages is pretty limited. You get one big one, and then a simple numeric pagination. I used some perl script ages ago (blosxom?), and it did just that. Still, I guess I can hack that into the cod…
- No proper attribution to code that they clearly didn't write themselves. It's not that hard people.
- Time could be better spent making the Jekyll docs clearer. The time they spent creating this could have gone into official documentation efforts and creating a better default in the core
- Would be nice if they could add chuck those plugins into their own repository. That way it would be possible to add them to the plugin list I created on the official Jekyll Wiki
I also wish it had a better base template, but I'm no designer, so what the hell do I know.
Re: Using Jekyll and GitHub Pages for Our Site
#9What I always found a bit annoying about jekyll (at least without plugin or forks) is that something like http://developmentseed.org/blog/2011/ or http://developmentseed.org/blog/2011/09/ doesn't work, i.e. the set of archive pages is pretty limited. You get one big one, and then a simple numeric pagination. I used some perl script ages ago (blosxom?), and it did just that. Still, I guess I can hack that into the cod…
Would/do Jose Diaz-Gonzalez's plug-ins solve your problem? https://github.com/josegonzalez/josediazgonzalez.com/tree/ma...