Added Google Season of Docs ideas

Author: kgodey

content/internships/project-ideas-collection/add-audio/contents.lr

@@ -0,0 +1,33 @@
+_model: project-idea
+---
+_hidden: yes
+---
+title: Improve CC Catalog API repo documentation for potential contributors
+---
+problem:
+We'd like to improve our documentation for potential contributors in the `cccatalog-api` repository. This repository includes a few different projects and we'd like to improve documentation for all of them.
+---
+expected_outcome:
+* Detailed code and architecture documentation available in the GitHub repository.
+---
+internship_tasks:  
+* Work with CC’s backend engineer to come up with a plan for the documentation.
+* Write documentation and create pull requests to get it merged.
+* If the documentation requires deployment, work with the CC team to deploy the documentation publicly.
+---
+application_tips:
+* Demonstrate your familiarity with the codebase and existing documentation.
+* Explain how you'd like to refactor or expand the documentation in detail.
+---
+resources:
+* [CC Catalog API documentation](https://api.creativecommons.engineering/v1/)
+* [CC Catalog API code](https://github.com/creativecommons/cccatalog-api)
+* [Divio's documentation best practices](https://documentation.divio.com/)
+---
+skills_recommended: Python, Writing
+---
+mentors: Alden Page
+---
+difficulty: Medium
+---
+filter_value: difficulty-medium skill-python skill-writing

content/internships/project-ideas-collection/api-contributor-docs/contents.lr

@@ -0,0 +1,41 @@
+_model: project-idea
+---
+_hidden: yes
+---
+title: CC Catalog API usage guide
+---
+problem:
+The [CC Catalog API documentation](https://api.creativecommons.engineering/v1/) is currently entirely auto-generated. While it's good, basic, API documentation, we'd like to make it more user friendly and provide how-tos, examples, and a bit more narrative.
+---
+expected_outcome:
+* Published API documentation should include auto-generated documentation as well as narrative elements.
+* API documentation should use Vocabulary, CC's design system if feasible.
+---
+internship_tasks:  
+* Work with CC’s backend engineer to come up with a plan for the documentation.
+* Build upon the auto-generated documentation and find a way to include narrative elements.
+* Integrate with Vocabulary if feasible.
+* Write documentation and create pull requests to get it merged.
+* Work with the CC team to deploy the documentation publicly.
+---
+application_tips:
+* Demonstrate your familiarity with the codebase and existing documentation.
+* Explain how you'd like to refactor or expand the documentation in detail.
+---
+resources:
+* [CC Catalog API documentation](https://api.creativecommons.engineering/v1/)
+* [CC Catalog API code](https://github.com/creativecommons/cccatalog-api)
+* [GoodRx API guide](https://www.goodrx.com/developer) (example API guide)
+* [Divio's documentation best practices](https://documentation.divio.com/)
+* [vocabulary GitHub repo](https://github.com/creativecommons/vocabulary)
+* [vocabulary documentation](https://cc-vocabulary.netlify.app/)
+* [Introducing Vocabulary blog post on CC blog](https://creativecommons.org/2019/12/13/cc-vocabulary-web-design-system/)
+* [Posts about Vocabulary on the CC open source blog](https://opensource.creativecommons.org/blog/categories/cc-vocabulary/)
+---
+skills_recommended: Python, Writing
+---
+mentors: Alden Page, Kriti Godey
+---
+difficulty: Medium
+---
+filter_value: difficulty-medium skill-python skill-writing

content/internships/project-ideas-collection/api-usage-guide/contents.lr

@@ -0,0 +1,33 @@
+_model: project-idea
+---
+_hidden: yes
+---
+title: Improve CC Search documentation for potential contributors
+---
+problem:
+We'd like to improve our documentation for potential contributors in the `cccatalog-frontend` repository.
+---
+expected_outcome:
+* Detailed code and architecture documentation available in the GitHub repository.
+---
+internship_tasks:  
+* Work with CC’s frontend engineer to come up with a plan for the documentation.
+* Write documentation and create pull requests to get it merged.
+* If the documentation requires deployment, work with the CC team to deploy the documentation publicly.
+---
+application_tips:
+* Demonstrate your familiarity with the codebase and existing documentation.
+* Explain how you'd like to refactor or expand the documentation in detail.
+---
+resources:
+* [CC Search code](https://github.com/creativecommons/cccatalog-frontend)
+* [CC Search](https://search.creativecommons.org/)
+* [Divio's documentation best practices](https://documentation.divio.com/)
+---
+skills_recommended: JavaScript, Writing
+---
+mentors: Breno Ferreira
+---
+difficulty: Medium
+---
+filter_value: difficulty-medium skill-javascript skill-writing