For a website about CoffeeScript, why the ruby dependencies?
balupton opened this issue · 7 comments
Instead of Jekyll, Serve, Thin you can use DocPad - coded in CoffeeScript, and still generates a static website you can use on github, or any node.js host.
Here's a point.
Does the "Created With" section of that project excite anyone else as much as it excites me? I love seeing so many modules remixed into such high-level functionality so quickly.
This will certainly get a look from me.
Oops.. that wasn't what I wanted to do...
Anyway, personally I'd like to see something more wiki-ish; I don't think having to fork, edit and do a pull request is too accessible... I'd love to be able to contribute to the cookbook from e.g. my cellphone. DocPad certainly does look interesting, but surely one could add wiki-like functionality to it?
David Brady, the originator of this project, does not seem to be against the idea of a wiki. You can view some more of his ideas for the project here: http://www.heartmindcode.com/blog/2011/05/coffeescriptcookbook-com-how-you-can-help/
The decision to use Jekyll was based solely on the fact that GitHub already provides this functionality. The site is updated automatically when new commits are added. We are not opposed to changing the format that the content is stored, but IMO this is focusing on the wrong problem. What this project needs is more content.
That said, patches welcome.
@thirdtruck thanks mate :) - btw guys, I'm the author of DocPad so if anyone wants to brainstorm ideas for it - such as the wiki functionality - then just add me on skype as I'd love to implement them :) my skype username is balupton
@firefly, @JohnFord - agreed, a wiki is definitely possible and is easy to add - the question is just when.
@blowmage - agreed.
For the wiki stuff, how do you plan on having the wiki and still have pull-requests/revision-history? Or would having the wiki edits be associated with a github handle be the way to go?