Wedge

Public area => The Pub => Off-topic => Topic started by: MultiformeIngegno on March 31st, 2013, 07:55 PM

Title: Jekyll
Post by: MultiformeIngegno on March 31st, 2013, 07:55 PM

Jekyll is a blog-aware, static site generator in Ruby
http://jekyllrb.com
https://github.com/mojombo/jekyll

Seems interesting :)

Title: Re: Jekyll
Post by: Nao on March 31st, 2013, 08:23 PM

I mentioned it in an earlier post this week ;) along with templeet, which I actually used and love long ago!

Posted: March 31st, 2013, 08:22 PM

However I think that static sites are no longer as needed as they could be 10 years ago, as servers are now 10 to 100 times faster...

Title: Re: Jekyll
Post by: MultiformeIngegno on March 31st, 2013, 08:43 PM

It can be used to create blogs too.
This for example: http://blog.feedbin.me/ :)

Title: Re: Jekyll
Post by: Nao on April 1st, 2013, 12:31 AM

Templeet can do that, too :P
And with comments...

I don't see any comments in your example. Building a static blog with no comments is easy as pie. Doing static comments is much more complicated. Well, at least it was back in the day!

Anyway, I'm just not sure what you're trying to say by posting this link..? That we should consider doing a static version of Wedge..?

Title: Re: Jekyll
Post by: MultiformeIngegno on April 1st, 2013, 12:52 AM

No, no. I'm not sending subliminal messages or something. It's just to share things I see and look at how they are. Don't know, something like "everything is inspiration" ahaha :P
This case I was looking at source code of that blog I posted, and I noticed it was really clean. So I asked them what was the tool used.

Title: Re: Jekyll
Post by: Nao on April 1st, 2013, 01:08 PM

Well at least this all prompted me to look at linuxfr.org, previously the most prominent site to use Templeet, and read discussions on the fact that it switched to Ruby on Rails a couple of years ago...
Basically, the thinking was also that static sites are no longer that important, and that anyway, the site was too dynamic to allow for proper use of Templeet's best feature. I think they went with the second best caching method (and first for dynamic sites...), i.e. they're caching only parts of a page, and then serving these static blocks dynamically.
I don't think Wedge or SMF would go to these lengths, mostly because there are so many potentially pages in a forum, if you create a static cache of all those things you'll end up with a huge cache folder... I guess, the best that can be done is to do a temp cache (i.e. expiry date like in cache_put_data), ensuring that only the currently most visited pages will be statically cached, or at least partially.
That's the direction SMF was going, I think... At some point.