Contains the documentation site implementation.
This section describes the best practices about what and how should be done in order to run the documentation locally.
- Install Docker (Community Edititon(CE) is enough) - please use the official Docker installation guide. Accept the default installation instructions (use Linux containers, etc.)
- From the Docker Settings window, share the drive where the documentation repos reside with Docker.
- Choose a repo you want to contribute to (e.g. https://github.com/telerik/xaml-docs.git, we will refer to that repo later as 'MY-REPO')
- Pull the repo onto your hard drive (e.g.
"D:\Work\xaml-docs")
IMPORTANT: In case you are not able to install and use Docker, please go to Instructions (without Docker), otherwise continue to the next section.
- Clone the current (seed) repo
git clone [email protected]:telerik/docs-seed.git- Go to the directory in which you've pulled it (e.g.
D:\Work\docs-seed) - Open a terminal of your choice (e.g., gitBash)
- Run the following command by passing the MY-REPO path (the quotes are mandatory):
sh copy_local.sh "D:\Work\xaml-docs"- Go to the MY-REPO directory
- Open a terminal of your choice (e.g., gitBash)
- Execute the following bash command in the root folder (where the Dockerfile is located)
sh start-docs.sh- This is it! You can find the documentation site on server address which is written in the terminal: http://0.0.0.0:4000/. If you can't open the previous URL, replace the '0.0.0.0' with 'localhost' - http://localhost:4000.
For example, for WPF documentation this would be: http://0.0.0.0:4000/devtools/wpf/
If you want to stop the web site and the container in which it has been served, navigate to the terminal in which you've executed the previous command and press
CTRL+C.
For WPF and Silverlight, see how to pass an additional config file.
- Install ruby 2.3.3 (64bit or 32bit)
- Install Ruby DevKit (64bit or 32bit)
- Ensure everything is correctly installed, especially if you have previous versions installed on the machine (e.g. check whether the 'config.yml' file in the DevKit root folder contains the correct path to the ruby folder and check whether the system environmnet variables are correctly set).
For more info on the above you can read the following article - http://jekyll-windows.juthilo.com/1-ruby-and-devkit/.
- Clone the current (seed) repo
git clone [email protected]:telerik/docs-seed.git- Go to the directory in which you've pulled it (e.g.
D:\Work\docs-seed) - Open a terminal of your choice (e.g., gitBash)
- Run the following command by passing the MY-REPO path (the quotes are mandatory):
sh copy_local.sh "D:\Work\xaml-docs"- Go to the MY-REPO directory
- Open a terminal of your choice (e.g., gitBash)
- Execute the following bash command in the root folder
bundle exec jekyll serve- This is it! You can find the documentation site on server address which is written in the terminal: http://127.0.0.1:4000/. If you can't open the previous URL, replace the '127.0.0.1' with 'localhost' - http://localhost:4000.
For example, for WPF documentation this would be: http://127.0.0.1:4000/devtools/wpf/
If you want to change the host or port just pass the --host or --port arguments to the command above as an addition (e.g.
bundle exec jekyll serve --host=0.0.0.0 --port=1234).
You executed sh start-docs.sh but you did not see any Jekyll output. Instead, the command ended with
the input device is not a TTY. If you are using mintty, try prefixing the command with 'winpty'
This happens whtn using Git Bash with the MinTTY console. This console does not allow combinations such as Ctrl+C to pass to the Docker container and so you get such an error.
The easiest way to resolve it is to prefix the command with winpty:
winpty sh start-docs.shAn alternative is to re-install Git Bash and choose the default Windows terminal this time. You can read more detailes in the following post: Docker for Windows: Interactive Sessions in MinTTY Git Bash.
When you want to stop serving the docs, you may have to repeat the Ctrl+C command or press Enter after it.
The scripts that copy the seed repo to the content repo (MY-REPO), also update the .gitignore file so as to avoid creating unstanged changes with work files that must not be commited. If you keep getting the .gitignore checked out, see what the change is with the original and commit to your repo the version that matches what the tool generates.
Docker is a resource-intensive tool. If you are not using it on a daily basis, consider preventing it from running on startup. Right click its tray icon > Settings > General, uncheck "Start Docker when you log in". This can save you time when booting up/logging in, but you will need to explicitly start Docker before working on documentation.
Also, it tends to require a lot of HDD space, which may be an issue if you are running it on an SSD drive with limited capacity. You can reduce its quota by opening the Settings dialog > Advanced and either changing the image location, and/or reducing its max size. This also lets you limit its RAM consumption.
You can benefit from the following features:
In case you want to add an additional config.yml file, pass it to the above command as follows:
sh start-docs.sh _silverlight.ymlTo be able to monitor the changes you are making on the built documentation, execute the following command in a new terminal in the root directory of the site:
sh watch.shPrerequisite: If you haven't yet, please install Node.js.
To only run jekyll build and not jekyll serve, you need to execute the following bash command:
sh build-docs.shThis can be useful if you want to (or already have) setup local IIS to point to the _site folder in your documentation repo. This allows you to also test redirects that jekyll serve does not support.