ivy/doc
Ken McMillan 088259a310 finding submodule z3 in test 2019-09-11 15:52:41 -07:00
..
_data fixing ivy_to_cpp problem 2018-05-28 16:08:20 -07:00
_includes fixing bugs in new fragment checker 2018-05-11 17:27:45 -07:00
_layouts trying to fix website https 2019-09-03 11:33:46 -07:00
_sass adding implement 2016-07-26 18:39:31 -07:00
css fixing bugs in new fragment checker 2018-05-11 17:27:45 -07:00
examples fixed initial key setup 2019-09-10 16:46:34 -07: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 trying to fix website https 2019-09-03 11:33:46 -07:00
commands.md fol command is actually fo 2018-07-04 09:16:32 -07:00
credits.md adding web site 2016-05-24 15:36:18 -07:00
decidability.md doc fixes 2018-05-21 12:10:42 -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 finding submodule z3 in test 2019-09-11 15:52:41 -07:00
language.md doc fixes 2018-05-21 12:10:42 -07:00
proving.ivy fixing up proving doc 2018-05-16 16:43:01 -07:00
proving.md fixing some problems with ivy_to_cpp 2018-05-17 13:34:49 -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.