When the file or directory being converted has an ancestor directory with athen all of the following conversions produce the same output:
ourbigbook.jsonfile, then your current working directory does not have any effect on OurBigBook output. For example if we have:
/project/ourbigbook.json /project/README.bigb /project/subdir/README.bigb
- directory conversion:
cd /project && ourbigbook .
cd / && ourbigbook project
cd project/subdir && ourbigbook ..
- file conversion:
cd /project && ourbigbook README.bigb
cd / && ourbigbook project/README.bigb
cd project/subdir && ourbigbook ../README.bigb
When there isn't a
ourbigbook.json, everything happens as though there were an empty
ourbigbook.jsonfile in the current working directory. So for example:
- outputs that would be placed relative to inputs are still placed in that place, e.g.
README.bigb -> index.htmlalways stay together
- outputs that would be placed next to the
ourbigbook.jsonare put in the current working directory, e.g. the