|
10 | 10 | - [FAQ](#faq)
|
11 | 11 | - [How can I contribute?](#how-can-i-contribute)
|
12 | 12 | - [Communication](#communication)
|
13 |
| -- [Contribute examples](#contribute-examples) |
| 13 | +- [Contribute examples or community projects](#contribute-examples-or-community-projects) |
14 | 14 | - [Contribute code](#contribute-code)
|
15 | 15 | - [Contribute documentation](#contribute-documentation)
|
16 | 16 | - [Disclosing vulnerabilities](#disclosing-vulnerabilities)
|
@@ -125,34 +125,16 @@ the projects that you are interested in.
|
125 | 125 |
|
126 | 126 | Also, [follow us on Twitter](https://twitter.com/orycorp).
|
127 | 127 |
|
128 |
| -## Contribute examples |
| 128 | +## Contribute examples or community projects |
129 | 129 |
|
130 |
| -One of the most impactful ways to contribute is by adding examples. You can find |
131 |
| -an overview of examples using Ory services on the |
132 |
| -[documentation examples page](https://www.ory.sh/docs/examples). Source code for |
133 |
| -examples can be found in most cases in the |
134 |
| -[ory/examples](https://github.com/ory/examples) repository. |
| 130 | +One of the most impactful ways to contribute is by adding code examples or other |
| 131 | +Ory-related code. You can find an overview of community code in the |
| 132 | +[awesome-ory](https://github.com/ory/awesome-ory) repository. |
135 | 133 |
|
136 | 134 | _If you would like to contribute a new example, we would love to hear from you!_
|
137 | 135 |
|
138 |
| -Please [open an issue](https://github.com/ory/examples/issues/new/choose) to |
139 |
| -describe your example before you start working on it. We would love to provide |
140 |
| -guidance to make for a pleasant contribution experience. Go through this |
141 |
| -checklist to contribute an example: |
142 |
| - |
143 |
| -1. Create a GitHub issue proposing a new example and make sure it's different |
144 |
| - from an existing one. |
145 |
| -1. Fork the repo and create a feature branch off of `master` so that changes do |
146 |
| - not get mixed up. |
147 |
| -1. Add a descriptive prefix to commits. This ensures a uniform commit history |
148 |
| - and helps structure the changelog. Please refer to this |
149 |
| - [Convential Commits configuration](https://github.com/ory/hydra-maester/blob/master/.github/workflows/conventional_commits.yml) |
150 |
| - for the list of accepted prefixes. You can read more about the Conventional |
151 |
| - Commit specification |
152 |
| - [at their site](https://www.conventionalcommits.org/en/v1.0.0/). |
153 |
| -1. Create a `README.md` that explains how to use the example. (Use |
154 |
| - [the README template](https://github.com/ory/examples/blob/master/_common/README.md)). |
155 |
| -1. Open a pull request and maintainers will review and merge your example. |
| 136 | +Please [open a pull request at awesome-ory](https://github.com/ory/awesome-ory/) |
| 137 | +to add your example or Ory-related project to the awesome-ory README. |
156 | 138 |
|
157 | 139 | ## Contribute code
|
158 | 140 |
|
|
0 commit comments