Anthony

Thanks for the note! I agree this is not clear in our docs, so happy to have this clarified. What is happening here is that each command is run in...

I can start by mocking this in the new templates and JS that drives the view. It would be good to decide on how to do the modeling for a...

Yeah, I like that plan! Any other decisions left here to discuss, or safe to bump this up to a work item?

I was just thinking about this one more. What if instead we flipped this a little and added a configuration option: ``` debug: true ``` Or, alternatively, a debug flag...

> It would add "another workflow to our build process" This doesn't feel this way to me, perhaps I'm not describing this well. Right now, there is a build button...

To push this forward, I'm going to preemptively add support for debug toggleing in the UI, and hack up detection for the commands that we do issue for informational purposes....

The templates now support `build_command.is_debug`, but this field can be renamed as needed. I'm going to hand this off for backend implementation and modeling. Without debug enabled:  With debug...

Yeah, it could be implemented later if we want, and is still probably independent from debug mode altogether. This build mode would probably mostly for support, and for projects that...

There is UI to show debug elements in the UI, but no debug level commands. We talked a bit above about next steps to call this done, namely adding `BuildCommand.is_debug`...

Also, I started on the templates by hacking in the configuration file with a mock command: ```readthedocs-build --show-config``` I sort of like this pattern and could see us using it...