This is an automated email from the ASF dual-hosted git repository.
wuchong pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/fluss.git
The following commit(s) were added to refs/heads/main by this push:
new 6b726d376 [website] Add contribution overview landing page
6b726d376 is described below
commit 6b726d3761761bf5cec64a8b5caad35d8872f109
Author: Jark Wu <[email protected]>
AuthorDate: Mon May 11 00:24:08 2026 +0800
[website] Add contribution overview landing page
Adds an overview landing page under community/how-to-contribute
that introduces contributors to the available guides (bug reports,
code, docs, blog posts, reviews) and provides getting-started tips
based on experience level.
---
website/community/become-a-committer.md | 4 +-
website/community/dev/_category_.json | 2 +-
website/community/how-to-contribute/overview.md | 71 +++++++++++++++++++++++++
3 files changed, 74 insertions(+), 3 deletions(-)
diff --git a/website/community/become-a-committer.md
b/website/community/become-a-committer.md
index 439447827..fd6259fb2 100644
--- a/website/community/become-a-committer.md
+++ b/website/community/become-a-committer.md
@@ -1,6 +1,6 @@
---
-title: How to become a Committer
-sidebar_position: 5
+title: How to Become a Committer
+sidebar_position: 4
---
# How to become a committer
diff --git a/website/community/dev/_category_.json
b/website/community/dev/_category_.json
index e1d8b6535..94661d369 100644
--- a/website/community/dev/_category_.json
+++ b/website/community/dev/_category_.json
@@ -1,4 +1,4 @@
{
"label": "Development Guide",
- "position": 4
+ "position": 5
}
diff --git a/website/community/how-to-contribute/overview.md
b/website/community/how-to-contribute/overview.md
new file mode 100644
index 000000000..5ee4d00ca
--- /dev/null
+++ b/website/community/how-to-contribute/overview.md
@@ -0,0 +1,71 @@
+---
+title: Overview
+sidebar_position: 0
+---
+
+# How to Contribute
+
+Apache Fluss is an open, community-driven project, and every improvement —
from fixing a typo to designing a major new feature — comes from contributors
like you. Contributions shape the project's direction, harden its quality, and
help other users succeed. Whether you are filing your first bug report or
landing a large feature, there is a place for you in the community.
+
+This section collects the guides you need to make that journey smooth. Start
with the contribution path that fits what you want to do, then follow the
detailed guide for the specifics.
+
+## Choose Your Contribution Path
+
+### Report a Bug or Request a Feature
+
+If you have found a defect, have a question the docs could not answer, or have
an idea for a new capability, the best first step is to open an issue. This
gives the community visibility into the problem and a place to discuss the
solution before any code is written.
+
+- Read the [Bug Reports and Feature Requests](bug-reports-feature-requests.md)
guide to learn what information to include and which template to use.
+
+Good for: users of any experience level who want to help improve Fluss without
writing code.
+
+### Contribute Code
+
+Code contributions — bug fixes, new features, performance improvements,
refactors — are the heart of the project. Fluss follows a *discuss first,
implement after* workflow so that reviewers and contributors stay aligned on
the approach before effort is spent on a pull request.
+
+- Follow the [Contribute Code](contribute-code.md) guide for the end-to-end
process: discuss, implement, review, and merge.
+- New to the codebase? Look at the [good first
issues](https://github.com/apache/fluss/contribute) to find a well-scoped task.
+
+Good for: developers who want to dive into the Fluss codebase, from small
fixes to large features.
+
+### Contribute Documentation
+
+Clear documentation makes Fluss usable. Fixing a broken link, clarifying a
concept, or adding a full guide for a new feature are all valuable
contributions, and they are often the fastest way to start contributing.
+
+- Follow the [Contribute Documentation](contribute-docs.md) guide for how the
docs site is structured, how to preview changes locally, and how versioned docs
work across release branches.
+
+Good for: contributors who want to improve the user experience, including
those who prefer writing over coding.
+
+### Contribute Blog Posts
+
+Blog posts are how the community shares use cases, deep dives, tutorials, and
release announcements. Blog content lives in a separate repository,
[apache/fluss-blog](https://github.com/apache/fluss-blog), and is published
independently from the main documentation.
+
+- Follow the [Contribute Blog Posts](contribute-blog-posts.md) guide to
propose a topic, write the post, and get it published.
+
+Good for: practitioners who want to share experience, demos, or technical deep
dives with the wider community.
+
+### Review Pull Requests
+
+Reviewing is one of the most valuable contributions you can make. Good reviews
keep the code base healthy, share knowledge across the community, and give
contributors a great experience.
+
+- Read the [Review Pull Requests](review-pull-requests.md) guide for the
review checklist and what to look for.
+
+Good for: experienced contributors and committers who want to help others land
their changes.
+
+## Getting Started Based on Your Experience
+
+**New to Fluss?** Start small. File a bug report when you hit one, fix a typo
you notice in the docs, or pick up a [good first
issue](https://github.com/apache/fluss/contribute) labeled for newcomers.
+
+**Comfortable with the project?** Look through the [open
issues](https://github.com/apache/fluss/issues) for unassigned work that
matches your interests, or propose an improvement you have wanted to see.
+
+**Experienced contributor?** Help review pull requests, mentor newcomers on
issues, or drive a larger feature through a [Fluss Improvement Proposal
(FIP)](https://cwiki.apache.org/confluence/display/FLUSS/Fluss+Improvement+Proposals).
+
+## Connect with the Community
+
+Contributions are easier when you are connected with other contributors. Join
the conversation on:
+
+- [GitHub Discussions](https://github.com/apache/fluss/discussions) — design
questions, usage help, and general discussion.
+-
[Slack](https://join.slack.com/t/apache-fluss/shared_invite/zt-33wlna581-QAooAiCmnYboJS8D_JUcYw)
— real-time chat with contributors and users.
+- [Mailing Lists](../welcome.mdx) — `[email protected]` for development,
`[email protected]` for user questions.
+
+Thank you for helping make Apache Fluss better.
