11–20 of 38 posts
If you're interesting in this, you should also check out Octopress, which sits on top of Jekyll and provides a nice default theme, handy addons (for google site search, disqus comments, twitter/facebook sharing, etc.), and deployment scripts. http://octopress.org/
If you're interesting in this, you should also check out Octopress, which sits on top of Jekyll and provides a nice default theme, handy addons (for google site search, disqus comments, twitter/facebook sharing, etc.), and deployment scripts. http://octopress.org/
Does GitHub support Jekyll plugins? I doubt they'd be willing to run arbitrary code for everyone...
The problem until recently was that there weren't appropriate tools for the job, but this article should prove that's now changing.
Earlier quoted context omitted.
Does GitHub support Jekyll plugins? I doubt they'd be willing to run arbitrary code for everyone...
Well, they're not really Jekyll plugins -- just Javascript plugins on the front-end (hence disqus comments instead of your own database of comments, google custom search instead of your own internal search engine, etc.)
What 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…
I dislike Octopress for several reasons: - 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 wa…
Earlier quoted context omitted.
Well, they're not really Jekyll plugins -- just Javascript plugins on the front-end (hence disqus comments instead of your own database of comments, google custom search instead of your own internal search engine, etc.)
Sorry, I was referring to these plugins: http://octopress.org/docs/plugins/
Ever since I installed Wappalyzer in my browser (detects what frameworks and technologies a website uses) more and more often I come across websites that I am shocked use so many backend and frontend frameworks. I'm shocked because that means they are spending unnecessary amounts of money, time and effort on hosting (e.g. Wordpress hosting), development and maintenance when the entire site would be perfectly well-ser…
Ever since I installed Wappalyzer in my browser (detects what frameworks and technologies a website uses) more and more often I come across websites that I am shocked use so many backend and frontend frameworks. I'm shocked because that means they are spending unnecessary amounts of money, time and effort on hosting (e.g. Wordpress hosting), development and maintenance when the entire site would be perfectly well-ser…
Developmentseed.org used to be a Drupal site, fwiw.
Earlier quoted context omitted.
Sorry, I was referring to these plugins: http://octopress.org/docs/plugins/
Oh, I get it. Those plugins are "compile-time" -- so they happen during the HTML generation process, before going up to github -- all github ever sees is static HTML and CSS files.