Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Using Jekyll and GitHub Pages for Our Site

developmentseed.org

Post reply on HN
Print view View original

31–38 of 38 posts

Re: Using Jekyll and GitHub Pages for Our Site

#31

Post by simonbrown »

LeafStorm wrote: post #25
jordanlev wrote: post #22

Earlier quoted context omitted.

I agree that a lot of frameworks are overkill, but if you put yourself in the frame of mind of a non-programming designer or a layperson who just needs to manage content on their site, using a static HTML generation tool is out of the question. I've been using octopress/jekyll recently and think it's amazing and really love it, but there's no way in a million years I could give that to a client to manage their own we…

An interesting idea that I had once is a server-side application that can edit the site files, save them to Git or Mercurial, and then compile them statically and push to a server via FTP, SFTP, WebDAV, S3 API, or rsync.

CushyCMS does that, but without DVCS (although it does support versioning).

Re: Using Jekyll and GitHub Pages for Our Site

#32

Post by Jgrubb »

AdesR wrote: post #17
amirhhz wrote: post #13

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.

DevSeed used to be one of the bigger name Drupal consultancies. They've been moving into other stuff over the last year and a half, for what that's worth.

edit: I just figured out that you probably already knew that. Cheers.

Re: Using Jekyll and GitHub Pages for Our Site

#33

Post by LeafStorm »

winton wrote: post #28
LeafStorm wrote: post #24

I have never used Jekyll. I do, however, frequently use nanoc[1] - it takes a bit more effort to set up, but it is far more flexible, because instead of ridiculous configuration files, you are actually writing Ruby code (in a very nice DSL, might I add) that controls how each set of files is compiled. One thing I did with it was create a Web site with recipes on it. The recipe files didn't have any actual content, ev…

And even more simple and powerful than nanoc: http://stasis.me

Except that Stasis has no support for on-the-fly creation of items from your Ruby code, no distinction between filters for content and for layouts, no support for non-filesystem data sources, no dependency tracking, and no metadata per item, among other things.

It may be more simple, but it is nowhere near as powerful.

Re: Using Jekyll and GitHub Pages for Our Site

#36

Post by subpixel »

winton wrote: post #28
LeafStorm wrote: post #24

I have never used Jekyll. I do, however, frequently use nanoc[1] - it takes a bit more effort to set up, but it is far more flexible, because instead of ridiculous configuration files, you are actually writing Ruby code (in a very nice DSL, might I add) that controls how each set of files is compiled. One thing I did with it was create a Web site with recipes on it. The recipe files didn't have any actual content, ev…

And even more simple and powerful than nanoc: http://stasis.me

Different, but also interesting:

http://get-serve.com/

"Serve provides the equivalent of the Views part of the Rails MVC. Edit and tweak your websites on-the-fly with the Serve server. And when you are ready to deploy, you have two options. Either export to a pure HTML static site or deploy the source on any Ruby-friendly web host."

One of many interesting ways to design/build a static site. You could then basically use Jekyll as a deploy tool to GitHub pages.

As a designer, I can attest the difficulty of developing using Jekyll, b/c to see your work you need to switch on the Jekyll server, and no changes will compile until you flip the switch again. I know Octopress fixes that, but I'm still wrestling with how to ditch the included theme and build my own.

Re: Using Jekyll and GitHub Pages for Our Site

#37

Post by winton »

LeafStorm wrote: post #33
winton wrote: post #28

Earlier quoted context omitted.

And even more simple and powerful than nanoc: http://stasis.me

Except that Stasis has no support for on-the-fly creation of items from your Ruby code, no distinction between filters for content and for layouts, no support for non-filesystem data sources, no dependency tracking, and no metadata per item, among other things. It may be more simple, but it is nowhere near as powerful.

You can do all of this via controllers. You can execute any Ruby code you want before each template renders.

There is distinction between filters for content and layouts, simply use the layout filename in a before block.

You can execute any Ruby you want. You can use ActiveRecord, Redis, whatever. Load YAML for metadata. None of this stuff needs to be baked in, Ruby already does it.

Re: Using Jekyll and GitHub Pages for Our Site

#38

Post by winton »

cal2 wrote: post #29
winton wrote: post #28

Earlier quoted context omitted.

And even more simple and powerful than nanoc: http://stasis.me

Huh? I think Stasis is great in theory, but a few things are preventing me from using it full time. Namely that I can't pass simple options to a template engine (of which I do a lot). It appears that you're the author. Can you offer any information on how Stasis is, in some ways, better than nanoc?

You are right. I would appreciate a fork to fix this very minor issue, but if not I will be getting to it very soon.

It can do everything nanoc does, but the execution is much simpler and much more natural. This is not just my opinion, but what I have heard from lots of people.

My apologies for the self-promotion, just trying to get the word out.

Post reply on HN