Skip to content

Remove Ruby/nanoc dependency #120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ajpiano opened this issue Jul 9, 2012 · 2 comments
Closed

Remove Ruby/nanoc dependency #120

ajpiano opened this issue Jul 9, 2012 · 2 comments
Assignees
Labels

Comments

@ajpiano
Copy link
Member

ajpiano commented Jul 9, 2012

Nanoc has taken us pretty far with this site, but the frankenbuild of using node.js to shell out to nanoc (requiring a functioning ruby environment) is hairy and adds a superfluous dependency. The building of the markdown content into html can be handled by a node-based static site generator like Wintersmith instead, and the custom logic in our Rules file can also be ported there as well.

TLDR: requiring node, php, ruby, and python to build the site fully locally feels insane (and inconvenient)

@ghost ghost assigned ajpiano Jul 9, 2012
@addyosmani
Copy link
Member

Completely agree.
On Jul 9, 2012 6:51 PM, "adam j. sontag" <
reply@reply.github.com>
wrote:

Nanoc has taken us pretty far with this site, but the frankenbuild of
using node.js to shell out to nanoc (requiring a functioning ruby
environment) is hairy and adds a superfluous dependency. The building of
the markdown content into html can be handled by a node-based static site
generator like Wintersmith
instead, and the custom logic in our Rules file can also be ported there as
well.

TLDR: requiring node, php, ruby, and python to build the site fully
locally feels insane (and inconvenient)


Reply to this email directly or view it on GitHub:
#120

@ajpiano ajpiano mentioned this issue Jul 11, 2012
@ajpiano
Copy link
Member Author

ajpiano commented Oct 15, 2012

OMG CLOSING THIS ISSUE YES YES YES

@ajpiano ajpiano closed this as completed Oct 15, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants