Document the state by adding a label to the FLIP page with one of "discussion", "accepted", "released", "rejected".

Discussion thread	https://lists.apache.org/thread/z9j0rqt61ftgbkr37gzwbjg0n4fl1hsf
Vote thread	here (<- link to https://lists.apache.org/list.html?dev@flink.apache.org)
JIRA	here (<- link to https://issues.apache.org/jira/browse/FLINK-XXXX)
Release	Does not have to be tied to a version release.

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.

Public Interfaces

We do not expect to have any new interfaces for this redesign.

Proposed Changes

We propose a change to the design, user experience, and content (where applicable). The design changes are to modernize the look and feel of the website. This will include a consistent color theme, dark mode, and updated graphics where applicable. Inspired by other Apache project websites, we propose a simplified top navigation bar with logically grouped links. This will provide users quick and easy access to commonly used information. Content changes will include minimal changes to the What is Flink, architecture, applications, operations, and use case pages including adding clearer visuals/graphics and simpler language to market capabilities to new users.

Our proposal is to modify the existing Hugo theme for the relevant webpages as we think it’s the simplest option that affords us the flexibility to modify the pages that need changes.

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:

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

There will be no impact to existing users.

Test Plan

While we do not expect to change any existing links, we will ensure that every link from the existing Flink website works on the redesigned version so that existing users are able to navigate without issues.

Rejected Alternatives

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)

Page tree

FLIP-333: Redesign Apache Flink website