What are some tools that I can use to achieve this workflow:

>>56231728
A closet
A server
A terminal emulator on your GNU + Linux system
A webpage opened to http://www.google.com

>>56231770
XD

>>56231728
You can hook travis CI into your shithub to build/test whenever you push code. You write your config, install and build steps in a .travis.yml file (yaml, I know). Long shit can be chucked in a bash script and referenced in the file.

You have after_succes after_failure tags to run different shit if your build passes or not (like building a docker container and pushing it to some registry, or piping shit to an API, or whatever)

As to updating a website, you're on your own nigga. Are you asking for 3rd party recommendations? Are you planning to write a restful api?

>>56231861
Yeah I was thinking travis too cause I already use it for some python projects, thanks for the tips.

Yeah, 3rd party recommendation and no API, just a tool that builds and renders what I point to. readthedocs does that for .rst, so why wouldn't there be something for latex/mathjax? I should check if GitHub Pages has something on this

>>56231939
I guess a compromise would be to render them on the travis part. A succesfull build means that you also converted your latex to the desired format right? (I'm rusty on my latex) And see if you can push that format to some 3rd party that, while not supporting latex, might support whatever your output is.