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!
Octopress 3.0 is coming
11–20 of 36 posts
Re: Octopress 3.0 is coming
#12I 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.
Re: Octopress 3.0 is coming
#13Looks 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.
Re: Octopress 3.0 is coming
#14I 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.
Re: Octopress 3.0 is coming
#15I 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
Re: Octopress 3.0 is coming
#16Looks 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.
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
#17I 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.
EDIT: It doesn look like it's available for linux though...
Re: Octopress 3.0 is coming
#18I 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.
Re: Octopress 3.0 is coming
#19Earlier 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.
Re: Octopress 3.0 is coming
#20Been 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…