Add website

[orzechow]

This closes #33

[orzechow]

@ll-nick Ready for review and merging.

We should change the GitHub Pages branch setting to main after merging.

[ll-nick]

Looks really good and the docker setup works (almost) like a charm, thank you! 🚀
Also very nice work in keeping the root directory clean. 🧹

Maybe you have an idea for these two things, otherwise feel free to merge :)

1. The browser tab title is currently: ARBITRATION_GRAPHS | Arbitration Graphs
   I tried changing it using a title: in the _config.yml but that only affects the second half. I did not manage to change the first half. I would imagine it being either only Arbitration Graphs or something like Arbitration Graphs | Home since we want to have different pages.
2. About the docker setup: I did not manage to get it to work at first because my root directory contained the compile_commands.json. Since that is a symlink generated in the dev container, it points to something like /home/blinky which is apparently something jekyll is not able not handle, even if you add it to the exclude: setting. I solved it by removing the link, not sure if there is a better option.

[ll-nick]

[ll-nick]

Oh and once we solved #49, we should definitely add a favicon 😉

[orzechow]

1. The browser tab title is currently: `ARBITRATION_GRAPHS | Arbitration Graphs`
   I tried changing it using a `title:` in the `_config.yml` but that only affects the second half. I did not manage to change the first half. I would imagine it being either only `Arbitration Graphs` or something like `Arbitration Graphs | Home`  since we want to have different pages.

Done, see ad495ac

2. About the docker setup: I did not manage to get it to work at first because my root directory contained the compile_commands.json. Since that is a symlink generated in the dev container, it points to something like `/home/blinky` which is apparently something jekyll is not able not handle, even if you add it to the `exclude:` setting. I solved it by removing the link, not sure if there is a better option.

I don't know how you've setup your dev container. But when using our docker compose setups, the compile_commands.json should be generated into the build folder and shouldn't be a symlink.

Maybe, you had issues with the demo build setup.
You can tell your cmake to lookout for demo/build instead of build. In VSCode that's sth like
"cmake.buildDirectory": "${workspaceFolder}/demo/build"
neovim will have sth similar.
The, you won't need the symlink workaround

[ll-nick]

Yeah, nevermind the compile commands thing. I am honestly not sure why the link was even there in the first place, my LSP works just fine without it 🤷‍♂️