diff --git a/README.md b/README.md
index 0662b2b..15e6cca 100644
--- a/README.md
+++ b/README.md
@@ -27,8 +27,9 @@
 
 ## How to contribute
 
-Have a look at [CONTRIBUTING](./CONTRIBUTING.md) for guidelines on how to
-contribute code to this repository.
+Have a look at [CONTRIBUTING](./CONTRIBUTING.md) and our [documentation on
+project organization and processes](https://docs.opentitan.org/doc/project/)
+for guidelines on how to contribute code to this repository.
 
 ## Licensing
 
diff --git a/doc/project/_index.md b/doc/project/_index.md
index f8bc32f..66db626 100644
--- a/doc/project/_index.md
+++ b/doc/project/_index.md
@@ -3,7 +3,7 @@
 ---
 
 OpenTitan is a collaborative hardware and software development program with contributors from many organizations.
-This area gives some more information about how the project itself is organized.
+This area gives some more information about how the project itself is organized and how to contribute.
 More information will be added over time.
 
 ## Quality standards for open hardware IP
@@ -14,6 +14,10 @@
 To make it to that stage, a [Hardware Signoff Checklist]({{< relref "checklist.md" >}}) is used to confirm completion.
 [Here](https://github.com/lowRISC/opentitan/blob/master/util/uvmdvgen/checklist.md.tpl) is a template that can be used as a checklist item.
 
+## Contributing
+
+See our documentation on [Contributing to OpenTitan]({{< relref "contributing.md" >}}) for general guidance on how we work, making bug reports, dealing with security issues, and contributing code.
+
 ## Governance
 
 OpenTitan is stewarded by lowRISC CIC, a not-for-profit company that uses collaborative engineering to develop and maintain open source silicon designs and tools for the long term.
diff --git a/doc/project/contributing.md b/doc/project/contributing.md
new file mode 100644
index 0000000..f3d952b
--- /dev/null
+++ b/doc/project/contributing.md
@@ -0,0 +1,62 @@
+---
+title: Contributing to OpenTitan
+---
+
+Thank you for your interest in contributing to OpenTitan.
+This document provides some guidelines to making those contributions.
+Important points before getting started:
+* We consider honest feedback crucial to quality.
+  We work hard to thoroughly review changes and provide actionable feedback.
+  We do this to ensure a high quality open source design.
+* Always assume good intent.
+  Our feedback may be demanding and may even feel disheartening.
+  Again, this is to support a high quality silicon design, and we definitely appreciate all OpenTitan contributions.
+* Please be friendly and patient in your communications.
+* All OpenTitan interactions are covered by [lowRISC's code of conduct](https://www.lowrisc.org/code-of-conduct/).
+* When communicating, remember OpenTitan is a security-focused project.
+  Because of this, certain issues may need to be discussed in a small group first.
+  See the [Security Issues Process]({{<ref "#security-issues" >}}) described below for more details.
+* OpenTitan involves both hardware and software.
+  We follow a hybrid approach involving both silicon and software design practices.
+* OpenTitan is a work in progress.
+  We are always looking for ways to improve and welcome feedback on any project matter, technical or not.
+
+**Important**: Please read the next three, short sections on reporting bugs, reporting security issues, and contributing code in preparation for making your first contribution to OpenTitan.
+If you would like more details, see the Detailed Contribution Guide (coming soon).
+
+## Bug reports
+
+**To report a security issue, please follow the [Security Issues Process]({{<ref "#security-issues" >}})**.
+
+Ideally, all designs are bug free.
+Realistically, each piece of collateral in our repository is in a different state of maturity with some still under active testing and development.
+See the [Hardware Development Stages]({{< relref "development_stages" >}}) for an example of how hardware progress is tracked.
+
+We are happy to receive bug reports and eager to fix them.
+Please make reports by opening a new issue in our [GitHub issue tracker](https://github.com/lowRISC/opentitan/issues).
+
+## Security issues
+
+Security is of major importance to the OpenTitan project.
+When dealing with security matters, and in keeping with standard industry practice, there are reasons why it makes sense to be cautious and have a non-public discussion within a small group of experts before full disclosure.
+For example,
+* to ensure responsible disclosure of vulnerabilities,
+* or to discuss the security impact of new features or proposed changes to an existing feature.
+
+If you believe you have found a security issue or intend to work on potentially security sensitive matters, please first reach out to our experienced security team at security@opentitan.org before starting a public discussion.
+That will enable us to engage successfully without creating undue risk to the project or its consumers.
+
+## Contributing code
+
+The information below aims at helping you get involved in the OpenTitan project by guiding you through our process of preparing your contribution and getting it integrated.
+
+For straight-forward and non-invasive contributions, a high level of coordination is unlikely to be necessary.
+In these cases, please open a pull request.
+
+For larger proposed changes we ask contributors to:
+* Discuss the matter with the team, either through the [opentitan-dev@opentitan.org](https://groups.google.com/a/opentitan.org/forum/#!forum/opentitan-dev) mailing list or through discussions in issues on GitHub.
+  Agree on a course of action and document this in a GitHub issue.
+* Implement the contribution, i.e., the solution previously agreed on, and reference the discussion when submitting the contribution.
+* Have the implementation reviewed by the team, address any feedback, and finally have it integrated into the project.
+
+Note that contributions must be accompanied by sign-off text which indicates acceptance of the project's Contributor License Agreement - see [CONTRIBUTING.md](https://github.com/lowRISC/opentitan/blob/master/CONTRIBUTING.md) for details.