per-project options

[G3z]

how about add configuration to te package.json ?
it would be cool to use a custom css or to specify you don't want to overwrite the css if is in the _docs_ directory
(so you can make a new doc, change the css and you shouldn't care about future updates)
something like:

docco-configuration :  {
    css: "style/docs.css",
    overwrite_css: false,
    write_timestamp: false
}

would be awesome don't you think ?

[mbrevoort]

Using the package.json is an interesting idea. I was never happy
clobbering the docs directory. Custom CSS and other config including
with a plug-in type option would be awesome. Like for enabling Dox, or
cloc or package.json parsing, or docpad integration to generate a more
rich set of pages.... Like it.

Sent from my iphone

On Dec 3, 2011, at 9:31 AM, G3z
reply@reply.github.com
wrote:

how about add configuration to te package.json ?
it would be cool to use a custom css or to specify you don't want to overwrite the css if is in the _docs_ directory
(so you can make a new doc, change the css and you shouldn't care about future updates)
something like:

docco-configuration : {
css: "style/docs.css"
overwrite_css: false
write_timestamp: false
}

would be awesome don't you think ?

---

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

[G3z]

what other options would you think should be added ?
i'm working on path so calling docco-husky form main folder is sufficient

[vytch]

I like the idea of having a config.json path as an option.

something like:

docco-husky -config config.json -name project source/js/src/*

Thanks anyway for this great feature.