THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
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.
...
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.
Detailed designs:
f) Home page + drop down
g) Architecture
h) Applications
i) Operations
