To get started, check out: https://agenatrader.github.io/Tutorials/

MkDocs is a fast, simple and downright gorgeous static site generator that's geared towards building project documentation. Documentation source files are written in Markdown format, and configured with a single YAML configuration file. The tutorials in the sources directory of this repository, are built with mkdocs and publicly hosted on GitHub Pages at https://agenatrader.github.io/Tutorials/.

This description will show you how to create static websites and deploy it to the live system.

To edit these files you can use the GitHub Online Editor but we recommend to use a separate text editor. We recommend the text editor Atom. You can download it here.

The following things are prerequisites:

• Install GitHub Client, create a GitHub user and checkout the repository
• Install Python
• Install Python package mkdocs using pip
• Install Pandoc

After the installation of all packages we are able to start to parse our data and to deploy our site.

Clone the master repository to your local computer. Now that we have everything right in place, we are going to modify files and deploy the new site. In the following you will see a detailed description on how to build and deploy data into the gh-pages site. If you have no time just go directly to Short version on how to deploy

You just need to do the following step if the gh-pages branch was not created before. Our static website will be displayed via the gh-pages branch. So we need to create the branch by using the following commands via command line.

git checkout master # you can avoid this line if you are in master
git subtree split --prefix output -b gh-pages # create a local gh-pages branch containing the splitted output folder
git push -f origin gh-pages:gh-pages # force the push of the gh-pages branch to the remote gh-pages branch at origin
git branch -D gh-pages # delete the local gh-pages

All documents in this repository are written in markdown format and stored in the sources directory of this repository. To parse these markdown files into static websites we need mkdocs to do this work for us. mkdocs will parse these markdown files, translate it into static websites and store it into the site directory. All configuration is done in a single YAML configuration file to configure the parsing process. Open Console, navigate to your YAML configuration file and build the markdown files using the mkdocs build command.

mkdocs build

This will create a new directory named site. If you are getting a warning that the site directory has already created, you can use the clean parameter to delete this directory before recreation.

mkdocs build --clean

• Parsing markdown to ebook (epub)

We recommend to validate the ebook using pagina EPUB-Checker. You can download it here.

• Parsing markdown to word file

If you are using tags in your markdown file, mkdocs is creating wrong links for these images, so we need to change this by replacing ./media/ to ../media/ manually. Another option is to do this automatic by using sed on linux or macintosh:

sed -i .bak -e 's%./media/%../media/%g' site/Example_Indicator_Condition_Strategy_Basic/README/index.html  && rm site/Example_Indicator_Condition_Strategy_Basic/README/index.html.bak
sed -i .bak -e 's%./media/%../media/%g' site/Example_Indicator_Condition_Strategy_Advanced/README/index.html  && rm site/Example_Indicator_Condition_Strategy_Advanced/README/index.html.bak

We have already created a branch called gh-pages and all data from this branch will be displayed on GitHub Pages.

The latest deploy of this documentation was created with mkdocs version 0.16.0 (2016-11-04). Please use the following command to check your mkdocs version.

mkdocs --version

If you are running an older mkdocs version, please use the following command to update to a newer version.

pip install --upgrade mkdocs

Create a commit and send all of your changes into the master repository and sync with your remote repository.

Now we are ready to to execute the following shell script to build the website from our markdown files.

./buildanddeploy.sh -build

It is time to commit the new build into the master repository. Create a commit, send all of your changes into the master repository and sync with your remote repository.

If the build process has finished, we can start to deploy the website to the gh-branch of our remote repository.

./buildanddeploy.sh -deploy

Congrats! We are done. All changes are now online on GitHub Pages.