We are happy to hear your feedback. Please read our contributing guidelines and the code of conduct before you submit a pull request or open a ticket.
We recommend using Docker to build and test the documentation. Running via Docker is only required if you plan to make changes to the styling or layout of the site.
For content related changes and fixes, it's easiest to use GitHub's File Edit UI to make the changes and create the pull request.
The first step is cloning and going into the repository.
git clone [email protected]:codeship/documentation.git
cd documentation
Then build the container and save it as a tagged image.
docker build --tag codeship/documentation .
You can now run commands via that container. By default, it will build the site and start the Jekyll development server.
docker run -it -p 4000:4000 -v $(pwd):/docs codeship/documentation
To access the site open http://IP_OF_YOUR_DOCKER_SERVER:4000 in your browser. Usually, this is localhost:4000
.
On Windows, the Docker commands are executed via the Docker Quickstart Terminal. If localhost doesn't work, you might have to open a normal command prompt and type docker-machine ls
. There you can take the IP that is listed under URL and type the IP (with port 4000) into your browser to reach the documentation.
To update Rubygem based dependencies, update the Gemfile
(if required) and run
docker run -it -v $(pwd):/docs codeship/documentation bundle update
For NPM based dependencies, run the following two commands
docker run -it -v $(pwd):/docs codeship/documentation yarn upgrade
SCSS files are automatically linted using scss-lint. To run it, execute the following command
docker run -it -v $(pwd):/docs codeship/documentation bundle exec scss-lint
It's configured in .scss-lint.yml and the default configuration is available online as well.
docker run -it -v $(pwd):/docs codeship/documentation gulp lint
docker run -it -v $(pwd):/docs codeship/documentation bundle exec jekyll doctor
If you want to include a table of contents, include the following snippet in the markdown file
* include a table of contents
{:toc}
Generate a URL for the specified tag (database in the example below). This function is also available as a filter and can be used with a variable (tag in the example).
{% tag_url databases %}
{{ tag | tag_url }}
generates the output as follows (depending on configuration values):
/tags/databases/
Link to a particular Ubuntu man page. The Ubuntu version currently defaults to Ubuntu Trusty.
{% man_url formatdb %}
generates the following output:
http://manpages.ubuntu.com/manpages/trusty/en/man1/formatdb.1.html