[BUG] 404 error for azul.dll file

[Areopagitics]

Description

Windows 64-bit DLL (azul.dll - 2.6Mb) is missing on the main site; instead it goes to 404 page. May I suggest to put the guide directly on the readme on Github so that there is no need to be updating your website.

Version / OS

Windows 10

Steps to Reproduce

Under the releases page click on Windows 64-bit DLL (azul.dll - 2.6Mb)

Additional Information

This project looks amazing BTW! I tried out fltk-rust GUI and it's so easy to get started and have a program quick and running. I didn't like the performance though (found it a bit lagging), when I tried their spreadsheet example. I am hoping this will be a bit snappier.

[fschutt]

May I suggest to put the guide directly on the readme on Github

The guide would get too long, I originally used the GitHub wiki, but I also didn't want to make myself dependent on GitHub 100%, so that in the future I could always migrate away from GitHub without breaking links.

[dumblob]

The guide would get too long, I originally used the GitHub wiki, but I also didn't want to make myself dependent on GitHub 100%, so that in the future I could always migrate away from GitHub without breaking links.

Well, you'd anyway want to keep the acquired "namespace" on GitHub after "leaving" GitHub to not allow others take it and use it for other purposes. So you'd simply just put a link on the GitHub wiki pointing to the new location. Literally speaking it'd break links as they are, but it'd redirect to the GitHub wiki main page where there would be the link to the new wiki. In other words, this would guarantee the user with a wrong link will anyway get quickly to what he/she wanted.

Thus I'd also suggest going for the GitHub wiki for now 😉.

[Areopagitics]

May I suggest to put the guide directly on the readme on Github

The guide would get too long, I originally used the GitHub wiki, but I also didn't want to make myself dependent on GitHub 100%, so that in the future I could always migrate away from GitHub without breaking links.

I least for myself, I have no problem with a long guide on the readme, which I have seen many times and have followed quite easily. I would much prefer a long concise guide in one place, than have to jump around to different websites (when they are not working, then it's a real downer).

What could also be done is have a link to another guide file on github that can be updated easily, if you want to keep your readme nice and clean. Just my two cents to make it easier to enter this project. I think that's a huge draw for a project (not sure if that's what you want though).