Draft: Modernize Undertow website

[IRus]

Very ambitious PR:

1. Migrate from Jekyll to Hugo: faster builds
2. Create Github Action to automatically deploy changes from master
3. Move documentation from undertow-docs branches into flat folder structure in this repo, archive undertow-docs and make changes here
4. Update to latest bootstrap
5. Update asciidoctor and switch to sh script instead of maven
6. I will have to preserve permalinks for SEO, now documentation links are different

I guess the whole point was to make site more modern and integrated.

Compare documentation:

https://irus.github.io/undertow-io-site/documentation/2.0.0/introduction/
https://undertow.io/undertow-docs/undertow-docs-2.0.0/index.html

There is a few bugs, and no 2.1.0 docs yet, but it's can be easily updated as any other comments

5k+ files because of javadoc relocation. I'm thinking that instead of storing them in repo, it should be possible to unpack jar from maven central.

I also don't think that this PR is really possible to review. If overall idea is approved, I can provide multiple smaller PRs that would lead to the same outcome

[ropalka]

@fl4via just FYI

[rhusar]

@IRus Awesome stuff, I was thinking the same thing that the website really needs some modernization.

I like how the documentation (really, the most important part) looks like, but having a 'single page' has HUGE advantages as you can just quickly do a control+F from a browser and find what you need, rather than trying to find the section and then do a search. So, if we were to split this, we would need a proper search which is little bit problematic to implement on static pages. Thoughts?

You need to do a rebase, because it's not even mergeable at this point (This branch has conflicts that must be resolved) as something screwed the history.

PS: I was going to say that maybe you should have discussed the technology choice with the project leads @ropalka @fl4via (maybe that did happen?) but then I quickly realized no human is ever going to look at the code, only Claude, so it doesn't really matter as long as it works on GitHub :)

[IRus]

@rhusar Thank you for checking this out!

I like how the documentation (really, the most important part) looks like, but having a 'single page' has HUGE advantages as you can just quickly do a control+F from a browser and find what you need, rather than trying to find the section and then do a search. So, if we were to split this, we would need a proper search which is little bit problematic to implement on static pages. Thoughts?

Agree. One way to solve this can be a single page with anchors, i.e sidebar still the same, but a single page on the right.

You need to do a rebase, because it's not even mergeable at this point (This branch has conflicts that must be resolved) as something screwed the history.

I'm not planning to merge this exact branch, it's too much vibe-coding and changes for me to comfortably merge it. If idea accepted, I would like to provide multiple smaller pin-point PRs.

[rhusar]

@rhusar Thank you for checking this out!

I like how the documentation (really, the most important part) looks like, but having a 'single page' has HUGE advantages as you can just quickly do a control+F from a browser and find what you need, rather than trying to find the section and then do a search. So, if we were to split this, we would need a proper search which is little bit problematic to implement on static pages. Thoughts?

Agree. One way to solve this can be a single page with anchors, i.e sidebar still the same, but a single page on the right.

That's exactly what I was thinking but did not want to say explicitly to create bias. So +1!

You need to do a rebase, because it's not even mergeable at this point (This branch has conflicts that must be resolved) as something screwed the history.

I'm not planning to merge this exact branch, it's too much vibe-coding and changes for me to comfortably merge it. If idea accepted, I would like to provide multiple smaller pin-point PRs.

Honestly, one branch for me would be fine, but that's just my personal opinion, project leads need to make that call.