You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/contributing-code/cc-search/contents.lr
+10-10
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ We also want to enable you - our community members - to build features that woul
12
12
13
13
If you do want to build a new feature, and we would love it if you did, all we ask is that you follow the process outlined in this document to ensure a smooth experience for everyone involved.
**Figure out if you need to follow this process.**
@@ -34,7 +34,7 @@ Examples that should follow this process:
34
34
- Adding a new filter to the search results page
35
35
-**Reasoning**: It is user facing and requires some product input and may require infrastructural work to collect the data that the search results will filter on.
@@ -43,7 +43,7 @@ Look through [our issues](https://github.com/creativecommons/cccatalog-frontend/
43
43
44
44
On this GitHub issue, add a comment describing the feature you want to build and why you think it would be a good addition to CC Search. Add as much detail as you can.
**Wait for CC staff to resolve dependencies (if applicable).**
87
87
88
88
If your feature depends on work that only CC staff can do, please wait for us to do that work. If you can start working on other parts of the feature in parallel, you may go ahead.
@@ -105,14 +105,14 @@ Once your pull request is ready, someone on CC staff will review your code and p
105
105
106
106
You may have to do Steps 4-7 for multiple codebases in some cases, e.g. if your work includes both the CC Catalog API and CC Search, the API work will have to be done before the CC Search work that depends on it.
Once your code is merged, it will be deployed to the staging server and tested manually (in addition to the comprehensive automated tests that you've already written). We may need to run some changes by our product counsel. This may produce an additional round of feedback for you to address.
0 commit comments