Rebuild website
diff --git a/content/contributing/contribute-code.html b/content/contributing/contribute-code.html
index 76b9695..2473034 100644
--- a/content/contributing/contribute-code.html
+++ b/content/contributing/contribute-code.html
@@ -220,6 +220,7 @@
<div class="page-toc">
<ul id="markdown-toc">
+ <li><a href="#looking-for-what-to-contribute" id="markdown-toc-looking-for-what-to-contribute">Looking for what to contribute</a></li>
<li><a href="#code-contribution-process" id="markdown-toc-code-contribution-process">Code Contribution Process</a> <ul>
<li><a href="#create-jira-ticket-and-reach-consensus" id="markdown-toc-create-jira-ticket-and-reach-consensus">1. Create Jira Ticket and Reach Consensus</a></li>
<li><a href="#implement-your-change" id="markdown-toc-implement-your-change">2. Implement your change</a></li>
@@ -231,6 +232,14 @@
</div>
+<h2 id="looking-for-what-to-contribute">Looking for what to contribute</h2>
+
+<p>If you have a good idea for the contribution, you can proceed to <a href="#code-contribution-process">the code contribution process</a>.
+If you are looking for what you could contribute, you can browse open Jira issues in <a href="https://issues.apache.org/jira/projects/FLINK/issues">Flink’s bug tracker</a>,
+which are not assigned, and then follow <a href="#code-contribution-process">the code contribution process</a>. If you are very new
+to the Flink project and want to learn about it and its contribution process, you can check
+<a href="https://issues.apache.org/jira/issues/?filter=12349196">the starter issues</a>, which are annotated with a <em>starter</em> label.</p>
+
<h2 id="code-contribution-process">Code Contribution Process</h2>
<style>
