Currently, images are interpreted relative to this project's html5bp/ directory. This makes it difficult to include image assets inline. With a cwd option, the consumer code could set the relative location from which to interpret the generated HTML document. This feature would also simplify the cssPath option (where users currently have to specify a path in terms of this module's html5bp/ directory).
I'm thinking this could be implemented using PhantomJS's setContent method, which allows for setting the page content and URL separately. In this case, the HTML5 Boilerplate's index.html file would have to be made into a template so that the resources it references could be loaded independently of the user-specified cwd.
Does the feature make sense? How about the proposed implementation?
YES. That's a great plan. Maybe name it something different because this could get confusing with the output path used by the CLI. A PR would be gratefully accepted.
Random user feedback: this issue was a show-stopper when I tried using this module. :-(