Automating the website build process

[siavashserver]

Since we aren't using any fancy Jekyll plugins, we can let GitHub to directly build and host the website by moving the sources to glfw.github.io repository.

[elmindreda]

That would be so good to have working.

Should the Doxygen generated directories live in this repo as well?

[siavashserver]

Yes, so they can be copied over during build process as well.

[elmindreda]

Does e53f035 seem reasonable?

[siavashserver]

Does e53f035 seem reasonable?

Yup.

I have also made a few changes here a3f2ff9 to fix issues with stylesheet paths; that's probably due to GitHub Pages stack being different (Jekyll 3.9) .

I'm not really familiar with how custom domain binding works, you might need to somehow copy/keep CNAME in sources as well.

[elmindreda]

Yes, the CNAME file needs to move here and possibly we should also rename this repo to glfw.github.io? I'm not sure what the functional differences are between a project site and an organization site beyond naming, but this is technically the latter.

[siavashserver]

I guess that's all that needs to be done and we should be good to go ^^"

[elmindreda]

It worked perfectly! Awesome work!

[elmindreda]

Hmm, nearly. css/arrow.png isn't getting copied for some reason. Never mind, it's back now.

[siavashserver]

I love these refreshing 6:00 AM mini heart attacks, glad it's up and running on first try :D

I'm not sure how much useful it might be, but it seems like that documentation regeneration can be somehow automated through these GitHub Actions as well:

• Doxygen Action
• GitHub Pages action
• Deploying to external repositories