New docs

[reubenharry]

Mkdocs. Covers both docs and website. Looks nicer. Still on netlify.

[netlify]

✅ Deploy Preview for monad-bayes-old-docs canceled.

Name	Link
🔨 Latest commit	ed41148
🔍 Latest deploy log	https://app.netlify.com/sites/monad-bayes-old-docs/deploys/63b489aaecd5ba000896d3cd

[netlify]

❌ Deploy Preview for monad-bayes-site failed.

Name	Link
🔨 Latest commit	ed41148
🔍 Latest deploy log	https://app.netlify.com/sites/monad-bayes-site/deploys/63b489aaa3befc000945f700

[netlify]

✅ Deploy Preview for monad-bayes canceled.

Name	Link
🔨 Latest commit	93c12f8
🔍 Latest deploy log	https://app.netlify.com/sites/monad-bayes/deploys/63b58f70d69bc400087faecd

[reubenharry]

@mknorps @idontgetoutmuch Here are what the new docs look like: https://monad-bayes.netlify.app/ The motivation was that currently I'm hosting two separate sites, one for the docs and one for the notebooks, and this both looks cleaner and is easier to maintain. I think this repo is set up such that I can't merge this in myself, so if one of you could, that would be great, and then I can delete the old websites.

[mknorps]

The site looks elegant! It has better user experience and you modernized it well. I like it very much.

Apart from the comments within the code, I have few comments and suggested changes regarding the PR:

• in docs/images plot.pgn and plot copy.pgn are duplicates. Remove the copy.
• How does tintin work here? I see a .tintin.yml file but no reference to it in teh code and requirements.
• Do we still need monad-bayes-site folder?
• For the structure of the project it would be better if the code to generate documentation was in a separate folder.
• is monad-bayes-site.cabal and stack.yaml within docs still needed?

[mknorps]

Change trigger to push on master and add cache.

[reubenharry]

Wasn't sure how to add cache, but added master.

[mknorps]

This should work:

      - name: Setup caching
        uses: actions/cache@v3
        with:
          key: ${{ github.sha }}
          path: .cache

Check out: https://gaseri.org/en/blog/2022-11-01-publishing-material-for-mkdocs-website-to-github-pages-using-custom-actions-workflow/

[reubenharry]

For some reason, the --force and Python 3.8 were both necessary for CI and netlify to work respectively, but I changed the other things.

[mknorps]

For some reason, the --force and Python 3.8 were both necessary for CI and netlify to work respectively, but I changed the other things.

That is inconvenient, but we can leave with this for now.

And what about:

Do we still need monad-bayes-site folder?
For the structure of the project it would be better if the code to generate documentation was in a separate folder.

Is also mathjax no longer needed?

[reubenharry]

And what about:

Do we still need monad-bayes-site folder?

I thought I removed it. I don't see it in the repo locally.

For the structure of the project it would be better if the code to generate documentation was in a separate folder.

Now done.

Is also mathjax no longer needed?

Re-added.

[mknorps]

Thank you! The code structure looks better :)
One last thing - remove mkdocs.yaml from the main directory.

If you want to experiment a bit with caching, as I suggested in this comment it would be great, but if you do not have time for this now, please create an issue for later not to forget about it.

[reubenharry]

OK, removed, and issue created.

[reubenharry]

Hm, netlify works fine, but something with CI fails. I'm a bit stumped. Any ideas?

[reubenharry]

Oh right, it's failing for the old site. Let me remove it...

[reubenharry]

Now passes CI, should be ready to merge.

[mknorps]

It looks OK now. Thank you for improving the documentation!

I created #239 to take care of the developer's environment regarding developing documentation.