ClickHouse/docs/tools
2020-03-21 13:50:48 +03:00
..
mkdocs-material-theme Minor improvements in docs build and content (#9752) 2020-03-19 14:51:22 +03:00
translate More complete "es" translation (#9791) 2020-03-21 12:17:06 +03:00
build.py fix mistype 2020-03-21 13:50:48 +03:00
concatenate.py Major website front page refactoring (#9300) 2020-03-13 22:35:03 +03:00
deploy-to-test.sh Try to purge website cache less aggressively (#9668) 2020-03-15 13:53:00 +03:00
easy_diff.py Major website front page refactoring (#9300) 2020-03-13 22:35:03 +03:00
easy_edit.sh Build Japanese docs (#7938) 2019-12-02 12:21:34 +03:00
github.py Docs build and grammar fixes (#9750) 2020-03-19 11:31:06 +03:00
make_links.sh [experimental] add "es" docs language as machine translated draft (#9787) 2020-03-21 07:11:51 +03:00
mdx_clickhouse.py Switch docs to python3 and update MkDocs to 1.1 (#9711) 2020-03-18 16:02:32 +03:00
output.md [experimental] add "es" docs language as machine translated draft (#9787) 2020-03-21 07:11:51 +03:00
README.md [experimental] add "es" docs language as machine translated draft (#9787) 2020-03-21 07:11:51 +03:00
release.sh python3 in release.sh 2020-03-21 07:56:32 +03:00
requirements.txt Bump pyyaml from 5.3 to 5.3.1 in /docs/tools (#9746) 2020-03-19 11:25:26 +03:00
test.py More complete "es" translation (#9791) 2020-03-21 12:17:06 +03:00
util.py Fix error handling in docs 2020-02-03 13:33:47 +03:00
website.py Switch docs to python3 and update MkDocs to 1.1 (#9711) 2020-03-18 16:02:32 +03:00

How ClickHouse documentation is generated?

ClickHouse documentation is built using build.py script that uses mkdocs library and its dependencies to separately build all version of documentations (all languages in either single and multi page mode) as static HTMLs. The results are then put in correct directory structure. It can also generate PDF version.

release.sh also pulls static files needed for official ClickHouse website from ../../website folder, packs them alongside docs into Docker container and tries to deploy it (possible only from Yandex private network).

How to check if the documentation will look fine?

There are few options that are all useful depending on how large or complex your edits are.

Install Markdown editor or plugin for your IDE

Usually those have some way to preview how Markdown will look like, which allows to catch basic errors like unclosed tags very early.

Use build.py

Itll take some effort to go through, but the result will be very close to production documentation.

For the first time youll need to install wkhtmltopdf and set up virtualenv:

$ cd ClickHouse/docs/tools
$ mkdir venv
$ virtualenv venv
$ source venv/bin/activate
$ pip install -r requirements.txt

Then running build.py without args (there are some, check build.py --help) will generate ClickHouse/docs/build folder with complete static html website.

You can just directly open those HTML files in browser, but usually it is more convenient to have some sort of HTTP server hosting them. For example, you can launch one by running cd ClickHouse/docs/build && python -m SimpleHTTPServer 8888 and then go to http://localhost:8888 in browser.

Commit blindly

Then push to GitHub so you can use its preview. Its better to use previous methods too though.

How to subscribe on documentation changes?

At the moment theres no easy way to do just that, but you can consider:

  • Hit the “Watch” button on top of GitHub web interface to know as early as possible, even during pull request.
  • Some search engines allow to subscribe on specific website changes via email and you can opt-in for that for https://clickhouse.tech.