You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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
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)
The text was updated successfully, but these errors were encountered: