Writing "incredibly fast" and not providing any clues of how fast is it is not exactly the best way to promote an application IMO.<p>Update: okay, it generates simplest site possible with 250 posts in 7 seconds. This is not the worst performance (it's faster than Jekyll), but I won't call this 'incredibly fast'. :\<p>And why the downvote, by the way? Is pointing out statements, which may not hold any value, wrong? Especially if they do not hold any value?
This looks like a nice, Node port of Jekyll. Not really how I prefer to blog.<p>My idea for a blogging platform (maybe even a service), if I ever get to it, would be a combination of <i>Jekyll and Posterous</i>. In other words, you'd have:<p>* A Jekyll dir structure on the server<p>* You write a post via Email<p>* The email is POSTed to the service via MailGun<p>* The service writes a new HTML file in the Jekyll dir and runs `jekyll build`<p>BAM, you have the speed of a static site, the wysiwyg editing features of whatever email client you use, and the ability to post from any computer/phone/tablet (not just one with git configured).
Seems interesting, I've always appreciated the simplicity of a Jekyll-type approach.<p>Apologies for semi-hijacking to mention it but, I take a slightly different approach in my personal blog (custom, messy code) - I rsync markdown documents to my webserver which are compiled into HTML and put into a redis in-memory collection which the server uses to render the blog. That gives you in-memory caching for free and avoids having a whole bunch of static files having to be generated every time. I use node on the backend and angular on the frontend to allow for a single-page website.<p>Currently the solution involves regenerating all HTML each time files are rsync by a script run remotely via SSH, however I ultimately intend for it to use an inotify-style approach to only import files that have actually changed, running both locally and remotely, so publishing an article need only require you to write some markdown and save it in a particular folder.<p>Though of course all this (currently) requires you to have a server such as linode to which you can rsync + have a remote serving script watch a folder, I mention it so to ask whether anybody would be interested in me cleaning it up and open sourcing it?