New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better document the build #666
Conversation
…ementation/../../../../assets/levels_en.png"
…es in CSV and JSON files
Quite happy with this now. I can update the documentation in the handbook to use the Makefile, but now you can:
translate_codelists.py now uses the build directory and doesn't overwrite the same files in different languages (which could cause issues if commands were run out-of-order), instead writing the translated codelists to different language directories. Note that you can use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From a quick look through, this all seems to be good.
…consistent with the default conf.py
Also, as far as I can tell, the building of .pot files is unnecessary to building the documentation (though it's necessary for collecting the source files that get pushed to Transifex). Is that correct?
I find build_docs.sh much easier to read now; the interdependency between commands is clear, and the script no longer requires jumping in and out of the
standard
directory.