Integrate build scripts with whatwg/html.

[mikewest]

It seems strange to me that the build scripts are separate from the only source file that will ever use them. I'd suggest integrating them with the main HTML repository (perhaps in a build/ subdirectory) so that symlinks or copying of source files is no longer a necessary step in the process.

[domenic]

I'm pretty strongly against this. Source repository history should not be intermingled with build tool revisions.

I tried to make it pretty clear from the

TODO: Don't require throwing everything into one directory before doing the build; instead, let the source and cldr-data be in seperate directories, and the output be put in another directory.

in the readme that the hacks you need to do here are a temporary state of affairs. That TODO is my preferred solution here.

[mikewest]

If it seemed like this system would be used for other documents (a la
Bikeshed), I think I'd agree with you. But given that there are no other
consumers of the scripts, they're fairly tightly tied to the source
document, and vice versa. What's the harm in tying the histories together?

[domenic]

It seems much less clean than what I propose, for no real gain. My modular version allows e.g. creation of a web service which takes as input the source repository, whereas mingling the files together would mean you'd have to extract out only the source files before sending them to such a service.

[domenic]

Going in the direction outlined in #15 instead. I am pretty confident it will be a nice experience when it's all ready, especially combined with #10 :).