Update project ideas list

Author: TimidRobot

content/programs/project-ideas-collection/add-plain-text-format-to-cc-legal-tools/contents.lr

@@ -0,0 +1,46 @@
+_model: project-idea
+---
+_hidden: yes
+---
+title: Automating Quantifying the Commons
+---
+problem:
+The Quantifying the Commons project has seen excellent additions led by student
+developers. However, the scope of previous projects did not include automation
+or combined reporting.
+---
+expected_outcome:
+Add automation of data gathering and report generation so that our reports
+quantifying the commons are never more than 3 months out of date.
+---
+contributor_tasks:
+The contributor will need to architect a data flow, formalize data formats,
+automate data gathering, and automate reporting. Challenges include quota
+limits that may require multi-day/multi-step data gathering, deciding on plain
+text vs binary data formats, and secret management. Knowledge of numpy and
+matplotlib python libraries will be very helpful.
+---
+application_tips:
+- Engage with the CC Legal Tools repositories (issues, pull requests)
+- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
+- [Applicant Guide](/programs/applicant-guide/)
+---
+resources:
+- [creativecommons/quantifying](https://github.com/creativecommons/quantifying):
+  Quantifying the Commons
+- [[Feature\] Automate Data Gathering and Analysis/Rendering · Issue
+  #22](https://github.com/creativecommons/quantifying/issues/22)
+---
+skills_recommended:
+- Git
+- GitHub Actions
+- Python
+---
+lead:
+- Timid Robot
+---
+difficulty: Medium
+---
+size: Large (~350 hours)
+---
+filter_value: difficulty-medium skill-git skill-github-actions skill-python

content/programs/project-ideas-collection/automating-quantifying-the-commons/contents.lr

@@ -0,0 +1,50 @@
+_model: project-idea
+---
+_hidden: yes
+---
+title: Modernize CC Resource Archive
+---
+problem:
+The Resources Archive has an outdated visual setup, and needs functionality
+fixes and improvements.
+---
+expected_outcome:
+Upgrade the look & feel to match current CC aesthetics, using the internal
+Design System (Vocabulary). Codebase is running current and standards compliant
+technology implementations. Entire site builds as static files on GH pages.
+Generate clear documentation of codebase and functionality.
+---
+contributor_tasks:
+Contributor will refactor codebase to fix resource submission, use current
+semantic, accessible, and standards compliant HTML, CSS, and JavaScript to
+match the current visual aesthetic of Creative Commons sites. Improve the
+overall UX for finding, submitting, and  accessing resources. Ensure the site
+functions as a static and stable Jekyll site hosted on GH Pages as static
+files. Final implementation will have clear documentation drafted within the
+codebase for future maintainability.
+---
+application_tips:
+- Engage with the CC Legal Tools repositories (issues, pull requests)
+- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
+- [Applicant Guide](/programs/applicant-guide/)
+---
+resources:
+- [creativecommons/cc-resource-archive](https://github.com/creativecommons/cc-resource-archive): CC Resource Archive
+- [Jekyll](https://jekyllrb.com/)
+- [GH Pages](https://pages.github.com/)
+---
+skills_recommended:
+- Git
+- JavaScript
+- Jekyll
+- HTML (Semantic & Accessible)
+- CSS (Structured & Accessible)
+---
+lead:
+- Sara
+---
+difficulty: Medium
+---
+size: Large (~350 hours)
+---
+filter_value: difficulty-medium skill-git skill-javascript skill-jekyll skill-html skill-css

content/programs/project-ideas-collection/add-rdf-xml-format-to-cc-legal-tools/contents.lr renamed to content/programs/project-ideas-collection/cc-legal-tools-machine-layer/contents.lr

@@ -0,0 +1,58 @@
+_model: project-idea
+---
+_hidden: yes
+---
+title: Upgrade and Refactor CC Chooser
+---
+problem:
+The Chooser has a stable initial UX, but due to bitrot its codebase is
+approaching non-support.
+---
+expected_outcome:
+Upgrade the codebase to current Vue.js versions and ancillary technologies
+(Vite, Pinia), created more clarity and longevity in the codebase. Generate
+clear documentation of codebase and functionality.
+---
+contributor_tasks:
+The contributor will need to upgrade the codebase from Vue.js v2.x to Vue.js
+v3.x, from Vue CLI to Vite, and from Vuex to Pinia. Incorporate new UX changes
+using semantic,  standards compliant, and accessible JavaScript, HTML, and CSS.
+Reduce the number of dependencies, and establish a stable automated process to
+build out an embeddable Web Component compatible implementation. Knowledge of
+the upgrade path from Vue 2.x implementations to Vue 3.x will be helpful, as
+will knowledge of Web Components. Final implementation will have clear
+documentation drafted within the codebase for future maintainability.
+---
+application_tips:
+- Engage with the CC Legal Tools repositories (issues, pull requests)
+- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
+- [Applicant Guide](/programs/applicant-guide/)
+---
+resources:
+- [creativecommons/chooser](https://github.com/creativecommons/chooser): Chooser
+- [Vue.js](https://vuejs.org/)
+- [Vue v3 Migration Guide](https://v3-migration.vuejs.org/)
+- [Vue CLI](https://cli.vuejs.org/)
+- [Vuex](https://vuex.vuejs.org/)
+- [Vite.js](https://vitejs.dev/)
+- [Pinia](https://pinia.vuejs.org/)
+- [Web Components](https://developer.mozilla.org/en-US/docs/Web/Web_Components)
+---
+skills_recommended:
+- Git
+- JavaScript
+- Vite
+- Vue.js (v2 & v3)
+- Pinia
+- HTML (Semantic & Accessible)
+- CSS (Structured & Accessible)
+- Web Components
+---
+lead:
+- Sara
+---
+difficulty: High
+---
+size: Large (~350 hours)
+---
+filter_value: difficulty-high skill-git skill-javascript skill-vue skill-html skill-css