ClickHouse/docs/tools
Ivan Blinkov 0a4a5b36cc
Some WIP on documentation refactoring (#2659)
* Additional .gitignore entries

* Merge a bunch of small articles about system tables into single one

* Merge a bunch of small articles about formats into single one

* Adapt table with formats to English docs too

* Add SPb meetup link to main page

* Move Utilities out of top level of docs (the location is probably not yet final) + translate couple articles

* Merge MacOS.md into build_osx.md

* Move Data types higher in ToC

* Publish changelog on website alongside documentation

* Few fixes for en/table_engines/file.md

* Use smaller header sizes in changelogs

* Group up table engines inside ToC

* Move table engines out of top level too

* Specificy in ToC that query language is SQL based. Thats a bit excessive, but catches eye.

* Move stuff that is part of query language into respective folder

* Move table functions lower in ToC

* Lost redirects.txt update

* Do not rely on comments in yaml + fix few ru titles

* Extract major parts of queries.md into separate articles

* queries.md has been supposed to be removed

* Fix weird translation

* Fix a bunch of links

* There is only table of contents left

* "Query language" is actually part of SQL abbreviation

* Change filename in README.md too

* fix mistype
2018-07-18 13:00:53 +03:00
..
mkdocs-material-theme Some WIP on documentation refactoring (#2659) 2018-07-18 13:00:53 +03:00
build.py Some WIP on documentation refactoring (#2659) 2018-07-18 13:00:53 +03:00
concatenate.py Some WIP on documentation refactoring (#2659) 2018-07-18 13:00:53 +03:00
easy_edit.sh Add helper script to simplify editing docs in both languages in parallel 2018-07-11 11:05:24 +03:00
README.md Add README.md for docs/tools 2018-07-11 16:45:13 +03:00
requirements.txt Clean up docs folder by moving all build-related tools to subdirectory 2018-07-09 15:14:26 +03:00

How ClickHouse documentation is generated?

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

Finally the infrustructure that builds ClickHouse official website just puts that directory structure into the same Docker container together with rest of website and deploys it to Yandex private cloud.

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

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

For the first time you'll need to 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 it's preview. It's better to use previous methods too though.

How to subscribe on documentation changes?

At the moment there's 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.yandex.