THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Page properties | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Document the state by adding a label to the FLIP page with one of "discussion", "accepted", "released", "rejected".
|
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Previous discussion thread: https://lists.apache.org/thread/c3pt00cf77lrtgt242p26lgp9l2z5yc8
Motivation
This FLIP proposes modernizing the Apache Flink website to improve its user experience and design. The Apache Flink website (https://flink.apache.org/) serves as the primary source of information for prospects and users interested in learning about Flink. With the growing interest in Flink, we want to modernize the website so that new and existing users can easily find information to understand what Flink is, the primary use cases where Flink is useful, and clearly understand its value proposition. We also want to improve the impression that prospective users have upon first encountering Apache Flink with the goal to make Flink attractive to new users.
...
Pages in scope:
We recommend modifications to the design and content (minor text changes, presentation, diagrams) of the following pages.
https://flink.apache.org/,
https://flink.apache.org/what-is-flink/flink-architecture/
https://flink.apache.org/what-is-flink/flink-applications/
https://flink.apache.org/what-is-flink/flink-operations/
https://flink.apache.org/use-cases/
https://flink.apache.org/powered-by/
We recommend modifications only to the design of the following pages
https://flink.apache.org/downloads/
https://flink.apache.org/getting-help/
https://flink.apache.org/community/
https://flink.apache.org/roadmap/
https://flink.apache.org/how-to-contribute (+ subpages)
https://flink.apache.org/security/
Out of scope:
Flink documentation. https://nightlies.apache.org/flink/flink-docs-stable/ We are NOT proposing any changes to Flink documentation as there is general consensus in the community that the Flink documentation is very well-organized and easily searchable based on the previous discussion thread: https://lists.apache.org/thread/c3pt00cf77lrtgt242p26lgp9l2z5yc8.
Here are a few initial designs with dark mode and moving navigation to the top, color options, and a GIF showcasing how Flink works instead of the Flink Squirrel logo:
a)
b) 
c) 
...
Detailed designs (dark and light modes)
| Home page | Architecture | Applications | Operations |
|---|---|---|---|
|
|
|  |
|
|
|
|
We are considering implementing both dark and light mode with a toggle. Order of implementation may result in one mode being available early followed by the other mode and toggle.
Additional pages:
| Roadmap | Powered By | Use cases | Getting help | Flink blog | Security | Community | Contribute | Review pull requests | Downloads |
|---|---|---|---|---|---|---|---|---|---|
 |  |  |  |
|
|  |  |
|
|
Other components:
| Dropdown |
|---|
|
Compatibility, Deprecation, and Migration Plan
...
1) Maintain status quo. No changes to the existing website. This is a rejected alternative as we received feedback from customers, specifically new users that the content could be better organized and could have improved visual appeal for a better user experience. Users shared that they did not understand the core value proposition of Flink. Some users stated that the design is unwelcoming and dated, especially when compared to other Apache projects.
2) For implementation, we considered using pre-built Hugo themes or paid solutions to build websites. This is a rejected alternative as pre-built Hugo themes explored were not suitable for the main website and required similar levels of effort to modify. We also rejected paid solutions as an option.
Previous designs:
a) b) c)
d) 
e)