@@ -7,8 +7,6 @@ Read on to learn more about viewing documentation in plain text (i.e., markdown)
77documentation yourself. Why build it yourself? So that you have the docs that correspond to
88whichever version of Deep Learning Pipelines you currently have checked out of revision control.
99
10- ## Generating the Documentation HTML
11-
1210We include the Deep Learning Pipelines documentation as part of the source (as opposed to using a hosted wiki, such as
1311the github wiki, as the definitive documentation) to enable the documentation to evolve along with
1412the source code and be captured by revision control (currently git). This way the code automatically
@@ -18,23 +16,14 @@ you have checked out or downloaded.
1816In this directory you will find textfiles formatted using Markdown, with an ".md" suffix. You can
1917read those text files directly if you want. Start with index.md.
2018
21- The markdown code can be compiled to HTML using the [ Jekyll tool] ( http://jekyllrb.com ) .
22- ` Jekyll ` and a few dependencies must be installed for this to work. We recommend
23- installing via the Ruby Gem dependency manager. Since the exact HTML output
24- varies between versions of Jekyll and its dependencies, we list specific versions here
25- in some cases (` Jekyll 3.4.3 ` ):
26-
27- $ sudo gem install jekyll bundler
28- $ sudo gem install jekyll-redirect-from pygments.rb
29-
19+ ## Generating the Documentation HTML
20+ To generate the documentation HTML, you can run the script from the base directory:
3021
31- Then run the prepare script to setup prerequisites and generate a wrapper "jekyll" script
32- $ ./prepare -s <path_to_spark_home> -t <path_to_tensorframes_home>
22+ $ dev/build-docs.sh
3323
34- Execute ` ./jekyll build ` from the ` docs/ ` directory to compile the site. Compiling the site with Jekyll will create a directory
35- called ` _site ` containing index.html as well as the rest of the compiled files.
24+ It compiles the site with Jekyll will create a directory called ` _site ` containing index.html as well as the rest of the compiled files.
3625
37- You can modify the default Jekyll build as follows:
26+ You can modify the default Jekyll build in the docs docker container as follows:
3827
3928 # Skip generating API docs (which takes a while)
4029 $ SKIP_API=1 ./jekyll build
@@ -43,13 +32,9 @@ You can modify the default Jekyll build as follows:
4332 # Build the site with extra features used on the live page
4433 $ PRODUCTION=1 ./jekyll build
4534
46- Note that ` SPARK_HOME ` must be set to your local Spark installation in order to generate the docs.
47-
4835## Pygments
4936
50- We also use pygments (http://pygments.org ) for syntax highlighting in documentation markdown pages,
51- so you will also need to install that (it requires Python) by running ` sudo pip install Pygments ` .
52-
37+ We also use pygments (http://pygments.org ) for syntax highlighting in documentation markdown pages.
5338To mark a block of code in your markdown to be syntax highlighted by jekyll during the compile
5439phase, use the following sytax:
5540
@@ -60,8 +45,7 @@ phase, use the following sytax:
6045
6146## Sphinx
6247
63- We use Sphinx to generate Python API docs, so you will need to install it by running
64- ` sudo pip install sphinx ` .
48+ We use Sphinx to generate Python API docs.
6549
6650## API Docs (Scaladoc, Sphinx)
6751
0 commit comments