Live data from Hacker News

Octopress 3.0 is coming

octopress.org

11–20 of 36 posts

Re: Octopress 3.0 is coming

#11
post #3

Been using octopress for a little over a year now, and this post sums up everything thats been a pain in the ass for me when it comes to upgrades/customization/etc. HERE HERE! Can't wait for this to be out!

I hope, however, that the author gives some thought to being able to freeze content, perhaps at the plugin level. I would hate to use a plugin, generate output, and find that at some point in the future, when the gem hasn't been maintained, the rest of my site suffers because I'm no longer able to mix current code with a plugin used at some point in the past. It would be great if I could have some sort of 'freeze' functionality that would take all the plugin level output as it exists today, lock it down, and update the rest of the site without having that plugin installed any more.

Re: Octopress 3.0 is coming

#12

I love the whole idea of static site generators. Jekyll, Middleman, etc. They're hard things to "hand-off" to a client. I'd love to see more work going into an interface for content managers (make it easy for them to update basic settings, add content, etc.). Prose, and Siteleaf get at this a bit.

Webhook (http://www.webhook.com/) is something you might be interested in. It's a static site generator that includes an admin interface. When the client changes something in the CMS, the generator is re-run and the site deployed automatically.

Re: Octopress 3.0 is coming

#13

Looks awesome. Now if there was a clean way to do incremental rebuilds and pushes, I would be very happy. Octopress is awesome until you start to accumulate hundreds or thousands of posts that must be regenerated and pushed to the target. The regeneration process is intrinsically serial at this point and does not take advantage of multiple threads or processes.

Agreed. This is a problem that I hope Jekyll manages to solve and it looks like they may be getting closer: https://github.com/jekyll/jekyll/pull/3116

Re: Octopress 3.0 is coming

#14

I love the whole idea of static site generators. Jekyll, Middleman, etc. They're hard things to "hand-off" to a client. I'd love to see more work going into an interface for content managers (make it easy for them to update basic settings, add content, etc.). Prose, and Siteleaf get at this a bit.

Statamic (http://statamic.com/) and Kirby (http://getkirby.com/) work like this. Neither is free/open-source though.

Re: Octopress 3.0 is coming

#15

I love the whole idea of static site generators. Jekyll, Middleman, etc. They're hard things to "hand-off" to a client. I'd love to see more work going into an interface for content managers (make it easy for them to update basic settings, add content, etc.). Prose, and Siteleaf get at this a bit.

There may be some ideas in Netobjects Fusion, http://netobjects.com

Wow, that's a blast from the past. I remember using 4.0 in high school in the 1990s.

Re: Octopress 3.0 is coming

#16

Looks awesome. Now if there was a clean way to do incremental rebuilds and pushes, I would be very happy. Octopress is awesome until you start to accumulate hundreds or thousands of posts that must be regenerated and pushed to the target. The regeneration process is intrinsically serial at this point and does not take advantage of multiple threads or processes.

I have my own little blogging engine based on https://github.com/debrouwere/render and what I've found is that the bottleneck is almost always IO. Rendering templates is so fast it simply does not matter whether you run it on a gazillion cores or not. Getting data from disk and then writing it to disk means you're dealing with contention, where parallelizing stuff can actually make it slower. So it can actually make sense to do all of this serially.

But of course, that doesn't mean you can't do incremental rebuilds. If the data is older than both the HTML and the template, then there's no need to rerender. More generators should support this, either internally or by making it easier to run them as part of a Make build.

Re: Octopress 3.0 is coming

#17
post #12

I love the whole idea of static site generators. Jekyll, Middleman, etc. They're hard things to "hand-off" to a client. I'd love to see more work going into an interface for content managers (make it easy for them to update basic settings, add content, etc.). Prose, and Siteleaf get at this a bit.

Webhook ( http://www.webhook.com/ ) is something you might be interested in. It's a static site generator that includes an admin interface. When the client changes something in the CMS, the generator is re-run and the site deployed automatically.

Hey, that looks nice! kind of reminded me of django-cms a bit (although theyŕe different beasts).

EDIT: It doesn look like it's available for linux though...

Re: Octopress 3.0 is coming

#18

I love the whole idea of static site generators. Jekyll, Middleman, etc. They're hard things to "hand-off" to a client. I'd love to see more work going into an interface for content managers (make it easy for them to update basic settings, add content, etc.). Prose, and Siteleaf get at this a bit.

I thought about building a CMS in this way, but it was easier to build it as a normal CMS and stick Cloudfront in f front of it.

Re: Octopress 3.0 is coming

#19

Earlier quoted context omitted.

There may be some ideas in Netobjects Fusion, http://netobjects.com

Wow, that's a blast from the past. I remember using 4.0 in high school in the 1990s.

Jekyll reminded me of Netobjects, I was surprised to find out the software brand is still around and still providing a GUI for static site generation.

Re: Octopress 3.0 is coming

#20
post #11
post #3

Been using octopress for a little over a year now, and this post sums up everything thats been a pain in the ass for me when it comes to upgrades/customization/etc. HERE HERE! Can't wait for this to be out!

I hope, however, that the author gives some thought to being able to freeze content, perhaps at the plugin level. I would hate to use a plugin, generate output, and find that at some point in the future, when the gem hasn't been maintained, the rest of my site suffers because I'm no longer able to mix current code with a plugin used at some point in the past. It would be great if I could have some sort of 'freeze' fu…

You can specify a specific version of a plugin in the Gemfile and it will never change, but you'll be able to update everything else.
Post reply on HN