ivy/doc
Darío Hereñú eeaf7fa85d Typo on #29
And some minor fixes (proposal)
2017-12-22 16:24:41 -08:00
..
_data finished leader example in testing tutorial 2016-09-20 18:40:25 -07:00
_includes adding website deployment cruft 2016-05-24 16:59:48 -07:00
_layouts adding web site 2016-05-24 15:36:18 -07:00
_sass adding implement 2016-07-26 18:39:31 -07:00
css adding web site 2016-05-24 15:36:18 -07:00
examples workaround for Jekyll relative path bug 2017-12-14 18:55:57 -08:00
images adding implement 2016-07-26 18:39:31 -07:00
.gitignore adding website deployment cruft 2016-05-24 16:59:48 -07:00
README Typo on #01 2017-12-22 16:23:10 -08:00
_config.yml adding web site 2016-05-24 15:36:18 -07:00
credits.md adding web site 2016-05-24 15:36:18 -07:00
deploy adding website deployment cruft 2016-05-24 16:59:48 -07:00
index.md fixing home page again 2016-05-26 17:32:32 -07:00
install.md Typo on #29 2017-12-22 16:24:41 -08:00
language.md Typos 2017-12-22 16:21:21 -08:00
proving.md working on prover 2017-07-02 18:56:32 -07:00

README

This directory can be builds into a web site using Jekyll
(https://jekyllrb.com/).

Viewing the site locally:

$ jekyll serve --port 8989 --watch

(open http://localhost:8989)

Deploying the site to Github pages:

The script "deploy" will do the following:

1) Clone the repository into a temp directory and check out the
gh-pages branch.

2) Remove all the files from git and copy this directory into the project.

3) Add all the files to git, commit the changes and push to Github.

This has the odd effect that all the files are freshly created in git
each time you deploy, but it works around the problem that Github
project web sites use a separate branch for the site content instead
of a directory.