22f51f103c
* CLICKHOUSE-4063: less manual html @ index.md * CLICKHOUSE-4063: recommend markdown="1" in README.md * CLICKHOUSE-4003: manually purge custom.css for now * CLICKHOUSE-4064: expand <details> before any print (including to pdf) * CLICKHOUSE-3927: rearrange interfaces/formats.md a bit * CLICKHOUSE-3306: add few http headers * Remove copy-paste introduced in #3392 * Hopefully better chinese fonts #3392 * get rid of tabs @ custom.css * Apply comments and patch from #3384 * Add jdbc.md to ToC and some translation, though it still looks badly incomplete * minor punctuation * Add some backlinks to official website from mirrors that just blindly take markdown sources * Do not make fonts extra light * find . -name '*.md' -type f | xargs -I{} perl -pi -e 's//g' {} * find . -name '*.md' -type f | xargs -I{} perl -pi -e 's/ sql/g' {} * Remove outdated stuff from roadmap.md * Not so light font on front page too * Refactor Chinese formats.md to match recent changes in other languages * Update some links on front page * Remove some outdated comment * Add twitter link to front page * More front page links tuning * Add Amsterdam meetup link * Smaller font to avoid second line * Add Amsterdam link to README.md * Proper docs nav translation * Back to 300 font-weight except Chinese * fix docs build * Update Amsterdam link |
||
|---|---|---|
| .. | ||
| mkdocs-material-theme | ||
| build.py | ||
| concatenate.py | ||
| easy_edit.sh | ||
| mdx_clickhouse.py | ||
| README.md | ||
| requirements.txt | ||
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 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 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.