[docs/website] Update website with roadmap 2026 changes

[MehulBatra]

Purpose

Linked issue: close #2652

Brief change log

Tests

API and Format

Documentation

[wuchong]

Hi @MehulBatra, instead of copying all the roadmap items from GitHub to the website, I prefer adding a direct link to the GitHub roadmap issue (In the future, we can keep every years roadmap link in the roadmap website page). Since the issue status updates in real-time, this approach avoids the extra workload of maintaining synchronization across both platforms. What do you think?

[MehulBatra]

Hi @wuchong , linking to the GitHub roadmap makes sense, low-maintenance and always up-to-date. 👍
One suggestion, though: as the community grows, a raw GitHub issue can feel dense for website visitors (especially folks evaluating Fluss who aren't deep in the repo). That's why I did both (I tried to keep the website part very light)

[wuchong]

Thank you, @MehulBatra. That makes sense. How about moving the "Fluss Roadmap 2026" link to the beginning of the page, specifically after the first paragraph and before the first section? I think this placement would enable users to access both the latest roadmap status and detailed information directly from the landing page. What are your thoughts?

[MehulBatra]

Thank you, @MehulBatra. That makes sense. How about moving the "Fluss Roadmap 2026" link to the beginning of the page, specifically after the first paragraph and before the first section? I think this placement would enable users to access both the latest roadmap status and detailed information directly from the landing page. What are your thoughts?

100% I will do that, also, I will try to slim down the pointers I have put to make roadmap more compact on the webpage