diff --git a/content/blog/entries/my-outreachy-internship-with-creative-commons/contents.lr b/content/blog/entries/my-outreachy-internship-with-creative-commons/contents.lr
new file mode 100644
index 000000000..f89fdbc78
--- /dev/null
+++ b/content/blog/entries/my-outreachy-internship-with-creative-commons/contents.lr
@@ -0,0 +1,56 @@
+title: My Outreachy Internship With Creative Commons
+---
+categories:
+outreachy
+outreachy-2024
+open-source
+community
+---
+author: Queen
+---
+series: outreachy-dec-2024-consolidating-and-implementing-vocabulary
+---
+pub_date: 2024-12-10
+---
+body:
+
+## Introduction
+Hi, everyone! My name is Queen, and I’m a fresh pharmacy graduate with a passion for tech. My journey into coding started four years ago when I wrote my first HTML code and thought, "Yes, I’m FAANG-ready!" Spoiler: I wasn’t — but that didn’t stop me from dreaming big. Balancing pharmacy school and learning to code often felt like I was biting off more than I could chew, but I’m proud that I never gave up on my dream of becoming a front-end developer.
+
+## My Core Values
+When I think about my core values, three words come to mind: **Growth**, **Curiosity**, and **Knowledge**.
+
+- **Growth**: I strive to improve in every aspect of life—mentally, physically, intellectually, and even spiritually. Every setback is just a stepping stone for me.
+- **Curiosity**: This one’s a work in progress, but I’m learning to ask questions and embrace not knowing. I love understanding *why* things work the way they do.
+- **Knowledge**: I read a lot because I genuinely enjoy learning new things. For me, knowledge is the key to confidence and growth.
+
+## My Journey to Outreachy
+Outreachy is a three-month paid open-source internship program for underrepresented people in tech. I first heard about it last year—just two days before the application deadline. I didn’t make it past the initial application stage that time.
+
+When the December 2024 cohort initial application opened, it was the perfect timing for me. By then, I had finished my pharmacy degree and was ready to gain professional experience in front-end development and most especially, in open source. This time, I was determined to get it right.
+
+I applied on the same day the application opened, I had already kept answers for the essay questions in my notes app. While waiting for the results, I brushed up on my skills and read articles from past interns to prepare for the contribution period.
+
+When I received the email saying my initial application had been approved, I felt a rush of excitement. To move forward and be able to make a final application, I needed to make at least one contribution to a project. I narrowed my choices to two based on the skills required, but Creative Commons stood out to me. Their mission and the project description piqued my interest more.
+
+## The Contribution Period
+The contribution period was competitive—and intimidating. Seeing the amazing work other applicants were doing made me doubt myself. But I loved the project and found the community so welcoming that I couldn’t give up.
+
+The mentors were incredibly supportive, giving feedback that helped me improve with each contribution. When it was time to draft my final application and proposal, I worked with my mentor, sharing my plans and got her input which helped me in creating my project timeline.
+
+Even before I knew if I’d be selected, I felt fulfilled. Contributing to Creative Commons was a rewarding experience, and I knew I wanted to continue contributing to the community, intern or not.
+
+## My Internship Project
+### **Consolidating and Implementing the Vocabulary Design System**
+During my internship, I’ll be working on consolidating and implementing the Vocabulary design system across Creative Commons' ancillary websites.
+
+Vocabulary is a design system that ensures a consistent user interface (UI) and user experience (UX) across all Creative Commons websites. However, its implementation has been inconsistent, with variations in features and versions across different sites. My role is to identify these inconsistencies and work on a unified implementation that also focuses on accessibilty. I'd also be implementing features that might be a good addition to the design system.
+
+I’m excited about this project because it aligns with my passion for front-end development and allows me to contribute meaningfully to a global community. I also get to improve my skills and gain new ones.
+
+## Conclusion
+This internship is more than just a milestone for me—it’s a testament to perseverance and growth. I’m thrilled to embark on this journey with Creative Commons, and I can’t wait to see where it leads.
+
+If you’re considering applying for Outreachy, my advice is simple: believe in yourself, stay curious, and never stop learning. Your journey might just surprise you.
+
+Thank you for reading!
diff --git a/content/blog/entries/outreachy-midpoint-progess-with-creative-commons/contents.lr b/content/blog/entries/outreachy-midpoint-progess-with-creative-commons/contents.lr
new file mode 100644
index 000000000..ef103e790
--- /dev/null
+++ b/content/blog/entries/outreachy-midpoint-progess-with-creative-commons/contents.lr
@@ -0,0 +1,73 @@
+title: Outreachy Midpoint Progress With Creative Commons
+---
+categories:
+outreachy
+outreachy-2024
+open-source
+community
+---
+author: Queen
+---
+series: outreachy-dec-2024-consolidating-and-implementing-vocabulary
+---
+pub_date: 2025-01-19
+---
+body:
+# Outreachy Midpoint Blog Post
+
+Hi there! My name is Queen, and I’m an Outreachy intern at Creative Commons. My project involves consolidating and implementing the Vocabulary design system across Creative Commons ancillary websites. In this post, I’ll share my progress and key takeaways from the first half of my internship.
+
+## Project Overview
+
+The goal of my project is to implement the Vocabulary design system across several Creative Commons ancillary websites like the [CC Open Source](https://opensource.creativecommons.org/), [CC Legal Database](https://legaldb.creativecommons.org/en/), [CC Search Portal](https://search.creativecommons.org/), and [CC Resource Archive](https://resources.creativecommons.org/).
+## Progress So Far
+
+### Phase One: Refactoring Markup to Align with Vocabulary
+
+In the first phase, I focused on refactoring the markup to align with Vocabulary’s components and context. Here are the pull requests (PRs) merged during this phase:
+
+- [PR 118](https://github.com/creativecommons/ccos-website-source/pull/118): Refactored the recent blog post section on the homepage.
+- [PR 856](https://github.com/creativecommons/ccos-website-source/pull/856): Refactored the homepage markup to align with Vocabulary components.
+- [PR 862](https://github.com/creativecommons/ccos-website-source/pull/862): Updated `page-with-toc.html`, which serves as a template for many pages.
+- [PR 863](https://github.com/creativecommons/ccos-website-source/pull/863): Initially, I planned to refactor the markup to Vocabulary’s context, but after feedback from my mentor, I instead removed legacy class names while retaining the table structure.
+- [PR 865](https://github.com/creativecommons/ccos-website-source/pull/865): Refactored the blog’s author page to match Vocabulary’s “person” context.
+- [PR 866](https://github.com/creativecommons/ccos-website-source/pull/866): Updated the blog structure to follow Vocabulary markup.
+- [PR 867](https://github.com/creativecommons/ccos-website-source/pull/867): Refactored the Project List page, leaving the table markup intact but removing old styles.
+- [PR 868](https://github.com/creativecommons/ccos-website-source/pull/868): Refactored the Issue Finder tool, replacing Vue.js with plain JavaScript. Although removing Webpack will happen later, this PR set the stage for future improvements.
+- [PR 870](https://github.com/creativecommons/ccos-website-source/pull/870): Aligned the Authors page with Vocabulary’s team styling.
+- [PR 871](https://github.com/creativecommons/ccos-website-source/pull/871): Refactored the Project Ideas page, incorporating Vocabulary’s project markup and removing legacy styles.
+- [PR 873](https://github.com/creativecommons/ccos-website-source/pull/873): Dynamically updated the body tag’s class in `layout.html` and added a body-class field to the `blog.ini` model file for consistent styling.
+- [PR 880](https://github.com/creativecommons/ccos-website-source/pull/880): Refactored `page-with-title.html` (used by CC Tech Archives) to align with Vocabulary.
+- [PR 886](https://github.com/creativecommons/ccos-website-source/pull/886): Updated the header component markup and removed old class names.
+
+### Phase 2: Adding Local Styles
+
+After refactoring the markup, I moved on to styling sections that Vocabulary doesn’t cover. Here are some of the merged PRs so far;
+
+- [PR 888](https://github.com/creativecommons/ccos-website-source/pull/888): Added local styles based on Creative Commons’ main website for the homepage and other sections, such as “Get Involved” and “Featured Projects.”
+- [PR 891](https://github.com/creativecommons/ccos-website-source/pull/891): Created a new `issue-finder.css` file to restyle the Issue Finder page while removing legacy styles but maintaining legacy design.
+- [PR 898](https://github.com/creativecommons/ccos-website-source/pull/898): Integrated Datatables and jQuery by adding them to a vendor folder. Styled the table and code blocks using existing website styles.
+- [PR 990](https://github.com/creativecommons/ccos-website-source/pull/990): Styled the CC Search archive table using Datatables.
+
+## Current Status
+
+I’m a little behind schedule—I had planned to start work on the Legal Database website by now. However, I’m wrapping up the CC Open Source website this week and will move on to the next phase soon.
+
+## Lessons Learned
+
+This internship has been an incredible learning journey. Here are some key takeaways:
+
+### Technical Skills:
+- I’ve become comfortable working with [Lektor](https://getlektor.com/), a static site generator that was entirely new to me.
+- Implementing the Vocabulary design system has improved my problem-solving skills, especially when dealing with legacy code and adapting the system to fit unique website needs.
+- To localize the table component, I had to read the [DataTables documentation](https://datatables.net/), which helped my ability to learn on the go.
+
+### Collaboration:
+Working with mentors has taught me the value of clear communication, especially when addressing blockers or seeking feedback.
+
+### Project Management:
+Breaking tasks into smaller chunks, prioritizing effectively, and maintaining consistent progress have been critical in managing this project.
+
+This experience has significantly boosted my confidence as a front-end developer, particularly in creating user-friendly and accessible interfaces.
+
+That’s it for now! Thank you for reading about my progress. I’m excited to see how the second half of this journey unfolds!
diff --git a/content/blog/entries/reflecting-on-my-outreachy-journey-with-creative-commons/contents.lr b/content/blog/entries/reflecting-on-my-outreachy-journey-with-creative-commons/contents.lr
new file mode 100644
index 000000000..64fcd4600
--- /dev/null
+++ b/content/blog/entries/reflecting-on-my-outreachy-journey-with-creative-commons/contents.lr
@@ -0,0 +1,91 @@
+title: Reflecting On My Outreachy Journey With Creative Commons
+---
+categories:
+outreachy
+outreachy-2024
+open-source
+community
+---
+author: Queen
+---
+series: outreachy-dec-2024-consolidating-and-implementing-vocabulary
+---
+pub_date: 2025-02-27
+---
+body:
+
+It feels like just yesterday I was writing my first blog post, trying to wrap my head around all the things I’d be doing during this internship. And now, here I am, writing my final post—time really does fly when you’re deep in code, refactoring, and figuring things out.
+
+When I started, I was both excited and nervous. I knew I’d be working on implementing and consolidating the Vocabulary design system across different Creative Commons ancillary websites, but I didn’t fully grasp just how much I’d learn along the way. The idea of making a meaningful contribution to such an impactful organization was thrilling, yet there was that little voice in my head wondering: *Can I really do this?*
+
+Spoiler alert: Yes, I could—and I did!
+
+## From Day One to Now: The Journey
+
+My first few weeks were all about getting familiar with the codebase, understanding how Vocabulary worked, and figuring out how the different websites used it. I remember spending quite a bit of time just reading through the Vocabulary documentation, going through all of the websites to identify discrepancies, and trying to piece things together.
+
+Looking back, it’s funny how something that once felt so complex now feels like second nature.
+
+## Refactoring the Issue Finder: Removing Vue for a Simpler Setup
+
+One of my major tasks was refactoring the issue finder tool on the Creative Commons Open Source website. This tool was built using Vue.js, but the goal was to remove Vue and refactor the JavaScript to align with the vocabulary approach - using HTML and CSS as much as possible with minimal and plain JavaScript.
+
+At first, this felt like a huge task, especially since I hadn’t used Vue before. The Vue-based setup handled filtering, UI interactions, and data fetching. Without a framework, I had to ensure that the core functionality remained intact while simplifying the code.
+
+I started by carefully analyzing how Vue was being used in the project. Then, I broke down the refactor into smaller steps:
+
+- Removing Vue dependencies and setting up a plan to replace its functionality with vanilla JavaScript.
+- Refactoring the JavaScript—rewriting event listeners, handling state manually, and simplifying functions where possible.
+- Ensuring everything still worked-since Vue had handled reactivity, I had to make sure UI changes (like filtering issues) were updated correctly without unnecessary complexity.
+- Testing and fine-tuning—checking for edge cases and making sure the refactored version behaved just like the Vue version (but with cleaner, more maintainable code).
+
+## Working with DataTables: A Whole New Learning Curve
+
+One of the most interesting things I learned during my internship was working with datatables Before this project, I had never even heard of DataTables. I spent time reading through the documentation, testing out different configurations, and experimenting with how it handled datasets.
+
+Initially, I added DataTables to the project using a **content delivery network (CDN)**, which was the quickest way to integrate it. However, after a suggestion from my mentor, we decided it would be better to download the source code and add it as a vendor folder in the project.
+
+After setting it up, I worked on overriding some default styles to make sure datatables aligned with Vocabulary’s design system. I had to carefully adjust CSS properties, inspect the DOM structure, and test different solutions to make sure everything looked cohesive.
+
+This entire process taught me an important lesson:
+
+> **Documentation is your best friend.** When dealing with a new tool, reading the official documentation can save so much time.
+
+## From Midterm to Now: Wrapping Up and Final Contributions
+
+After the midterm blog, my focus shifted towards finishing up the restyling process and addressing minor bugs across the Creative Commons Open Source website. These were smaller but important refinements—ensuring consistency, fixing UI inconsistencies, and making sure everything aligned with the Vocabulary design system.
+
+### Improving the Search Portal
+
+One of the websites I worked on was the **Search Portal**. This involved:
+
+- Defining the CC abbreviation in the header section to improve clarity and accessibility.
+- Restyling the search input to align visually with the provided context in Vocabulary, making it feel more integrated with the overall design.
+- Making downstream changes to ensure everything was up to date with Vocabulary’s latest standards.
+
+The goal was to keep the existing functionality and improve on the design, making sure the search input visually aligned with the design system.
+
+### CC Legal Database(LegalDB): Planning for Future Work
+
+Although LegalDB was initially part of the project scope, time constraints didn’t allow for implementation. Instead, I'm focusing on laying the groundwork for future contributions by:
+
+- Identifying necessary changes and documenting them thoroughly.
+- Creating all the relevant issues and linking them to the larger tracking issue on Vocabulary, ensuring that future contributors have a clear roadmap to follow.
+
+This is so that even though I couldn’t complete the work myself, the transition for the next person picking it up would be smooth and well-documented.
+
+## What’s Next?
+
+This internship has solidified my love for front-end development, especially when it comes to building interfaces that are both beautiful and functional. My next goal? To dive deeper into **animations, interactivity, and making the web more immersive** (looking at you, **GSAP and Three.js**!).
+
+I also want to keep contributing to **open source** and continue growing as a developer. This isn’t the end—it’s just the beginning of the next chapter.
+
+## A Heartfelt Goodbye (For Now!)
+
+To my mentors, and everyone who supported me during this internship— thank you! Your guidance, patience, and encouragement made this experience truly special.
+
+To future Outreachy interns: If you ever feel overwhelmed, know that it’s part of the journey. Keep asking questions, keep pushing through challenges, and most importantly—**enjoy the process**. You’ll come out on the other side with skills, confidence, and a whole new appreciation for open source.
+
+And with that, it’s time to say goodbye to this chapter.
+
+Until then, **happy coding!** 🚀
diff --git a/content/blog/entries/the-specifics-revamping-CCOS/contents.lr b/content/blog/entries/the-specifics-revamping-CCOS/contents.lr
index 6a88f156d..a4819dd76 100644
--- a/content/blog/entries/the-specifics-revamping-CCOS/contents.lr
+++ b/content/blog/entries/the-specifics-revamping-CCOS/contents.lr
@@ -171,7 +171,7 @@ This is code for the Hero section of the home page.
### Improvements in the Lektor project -
-I tried to write the perfect code that is cleaner and readable. I would try to demonstrate my effort using the home page code where I used [Lektor Flowblocks](https://www.getlektor.com/docs/models/flow/). The new homepage design have four sections where each section communicated something and I realized they were all independent and building the whole page through one single template would become a bit messy and hard to handle. So I did some research and found a way where I could build sub-templates and use them all to develop a single page and Lektor’s flowblocks allowed me to do so. Here is one of the flowblock and if you want to check out the whole working you can go to — [CCOS Repository](https://github.com/creativecommons/creativecommons.github.io-source).
+I tried to write the perfect code that is cleaner and readable. I would try to demonstrate my effort using the home page code where I used [Lektor Flowblocks](https://www.getlektor.com/docs/models/flow/). The new homepage design have four sections where each section communicated something and I realized they were all independent and building the whole page through one single template would become a bit messy and hard to handle. So I did some research and found a way where I could build sub-templates and use them all to develop a single page and Lektor’s flowblocks allowed me to do so. Here is one of the flowblock and if you want to check out the whole working you can go to — [CCOS Repository](https://github.com/creativecommons/ccos-website-source).
#### Recent Blog Post block -
diff --git a/content/blog/series/gsoc-2024-ansible-local-dev/contents.lr b/content/blog/series/gsoc-2024-ansible-local-dev/contents.lr
new file mode 100644
index 000000000..a730f9889
--- /dev/null
+++ b/content/blog/series/gsoc-2024-ansible-local-dev/contents.lr
@@ -0,0 +1 @@
+name: GSoC 2024: Ansible Local Dev
diff --git a/content/blog/series/gsoc-2024-cc-resource-archive/contents.lr b/content/blog/series/gsoc-2024-cc-resource-archive/contents.lr
new file mode 100644
index 000000000..592830737
--- /dev/null
+++ b/content/blog/series/gsoc-2024-cc-resource-archive/contents.lr
@@ -0,0 +1 @@
+name: GSoC 2024: CC Resource Archive
diff --git a/content/blog/series/outreachy-dec-2024-consolidating-and-implementing-vocabulary/contents.lr b/content/blog/series/outreachy-dec-2024-consolidating-and-implementing-vocabulary/contents.lr
new file mode 100644
index 000000000..4c89004f8
--- /dev/null
+++ b/content/blog/series/outreachy-dec-2024-consolidating-and-implementing-vocabulary/contents.lr
@@ -0,0 +1 @@
+name: Outreachy Dec 2024: Consolidating and Implementing Vocabulary
diff --git a/content/community/code-of-conduct/contents.lr b/content/community/code-of-conduct/contents.lr
index ad45095ae..a390a61f8 100644
--- a/content/community/code-of-conduct/contents.lr
+++ b/content/community/code-of-conduct/contents.lr
@@ -4,7 +4,7 @@ _template: page-with-toc.html
---
title: CC Open Source Code of Conduct
---
-description: The following Code of Conduct applies to all digital spaces managed by the Creative Commons technology team, including GitHub, mailing lists, and any other spaces which the development community uses for communication. Our Slack code of conduct is separate and
can be found here.
+description: The following Code of Conduct applies to all digital spaces managed by the Creative Commons (CC) Technology team, including GitHub, mailing lists, and any other spaces which the development community uses for communication. Our Slack code of conduct is separate and
can be found here.
---
body:
@@ -82,9 +82,9 @@ Enforcement](/community/code-of-conduct/enforcement/).
- 2022-05-11
- For a detailed list of changes, see [History for
content/community/code-of-conduct/contents.lr -
- creativecommons/creativecommons.github.io-source][commits].
+ creativecommons/ccos-website-source][commits].
-[commits]: https://github.com/creativecommons/creativecommons.github.io-source/commits/main/content/community/code-of-conduct/contents.lr
+[commits]: https://github.com/creativecommons/ccos-website-source/commits/main/content/community/code-of-conduct/contents.lr
## Attribution
diff --git a/content/community/code-of-conduct/enforcement/contents.lr b/content/community/code-of-conduct/enforcement/contents.lr
index 159b103a3..8b3066d80 100644
--- a/content/community/code-of-conduct/enforcement/contents.lr
+++ b/content/community/code-of-conduct/enforcement/contents.lr
@@ -9,7 +9,7 @@ body:
## Codes of Conduct
This document provides incident reporting guidelines and an enforcement manual
-for the following codes of conduct used by Creative Commons:
+for the following codes of conduct used by Creative Commons (CC):
- [Terms of Use - Creative Commons][terms-of-use]
- [CC Open Source Code of Conduct][foss-conduct]
@@ -205,9 +205,9 @@ comply with the current policy.
### Last Revised
- 2021-05-11
-- For a detailed list of changes, see [History for content/community/code-of-conduct/enforcement/contents.lr - creativecommons/creativecommons.github.io-source][commits].
+- For a detailed list of changes, see [History for content/community/code-of-conduct/enforcement/contents.lr - creativecommons/ccos-website-source][commits].
-[commits]: https://github.com/creativecommons/creativecommons.github.io-source/commits/main/content/community/code-of-conduct/enforcement/contents.lr
+[commits]: https://github.com/creativecommons/ccos-website-source/commits/main/content/community/code-of-conduct/enforcement/contents.lr
## Attribution
diff --git a/content/community/community-team/project-roles/contents.lr b/content/community/community-team/project-roles/contents.lr
index 0055ea624..cac720626 100644
--- a/content/community/community-team/project-roles/contents.lr
+++ b/content/community/community-team/project-roles/contents.lr
@@ -4,7 +4,7 @@ _template: page-with-toc.html
---
title: Community Team: Project Roles
---
-description: This page serves as a guide for project-based roles on CC's
Community Team.
+description: This page serves as a guide for project-based roles on Creative Commons'
Community Team.
---
body:
@@ -20,7 +20,8 @@ Team][communityteam] page.
**Who should apply:**
-If you’ve contributed to a CC project, you should apply for this role.
+If you’ve contributed to a Creative Commons (CC) project, you should apply for
+this role.
**What does this role give you?**
diff --git a/content/community/contents.lr b/content/community/contents.lr
index ac5ce2cd6..cca202227 100644
--- a/content/community/contents.lr
+++ b/content/community/contents.lr
@@ -4,11 +4,10 @@ _template: page-with-toc.html
---
title: Join the CC Developer Community
---
-description: Join our Slack or mailing list communities to meet other
-developers interested in Creative Commons, get feedback on your projects, and
-talk with CC's full-time engineering staff. You can also keep up with us on the
-
CC Open Source Blog or via
Twitter.
+description: Join our Slack to meet other developers interested in Creative
+Commons (CC), get feedback on your projects, and talk with CC's full-time
+Technology team members. You can also keep up with us on the
CC
+Open Source Blog.
---
body:
@@ -54,9 +53,9 @@ The channels most relevant to CC's developer community are:
| `#cc-dev-platform-toolkit` | [mp][mp] project (CC Platform Toolkit) |
| `#cc-dev-searchportal` | [search][search] project |
| `#cc-dev-vocabulary` | [cc-vocabulary][cc-vocabulary] project |
-| `#cc-dev-wordpress` | [wp-plugin-creativecommons][wp-plugin-creativecommons] project (creativecommons WordPress plugin) |
| `#cc-dev-workprograms` | **GSoC, GSoD, Outreachy, and other [work programs][workprograms] or internships** |
| `#cc-developers` | **general technical issues, new tech blog posts, etc.** |
+| `#cc-translation` | Coordinating translation efforts |
| `#cc-usability` | general usability issues, seeking feedback on new releases of CC products from the community, etc. |
[legaldb]: https://github.com/creativecommons/legaldb
@@ -66,7 +65,6 @@ The channels most relevant to CC's developer community are:
[mp]: https://github.com/creativecommons/mp
[cc-vocabulary]: https://github.com/creativecommons/cc-vocabulary
[search]: https://github.com/creativecommons/search
-[wp-plugin-creativecommons]: https://github.com/creativecommons/wp-plugin-creativecommons
[workprograms]: /programs/
diff --git a/content/community/write-a-blog-post/contents.lr b/content/community/write-a-blog-post/contents.lr
index e33aefe14..633a2b189 100644
--- a/content/community/write-a-blog-post/contents.lr
+++ b/content/community/write-a-blog-post/contents.lr
@@ -4,7 +4,7 @@ _template: page-with-toc.html
---
title: Write a Blog Post
---
-description: We invite members of the Creative Commons community to write guest posts on
our technical blog.
+description: We invite members of the Creative Commons (CC) community to write guest posts on
our technical blog.
---
body:
@@ -29,18 +29,18 @@ If you're writing about a project you're working on, here are a few ways you cou
- Announce your project and ask for contributions (example: [CC Vocabulary announcement](https://creativecommons.github.io/blog/entries/cc-vocabulary-new-design-system/))
- Write an overview of how your project works without as much narrative (example: [this post about the CC Catalog](https://creativecommons.github.io/blog/entries/cc-catalog-leverage-open-data-1/))
-
If you have more tips, submit an edit to this page.
+
If you have more tips, submit an edit to this page.
## How to post
Once you have written your post, you can either send it to us (Markdown is easiest for us, but we're happy to work with other formats) or directly create a pull request for your post as detailed below.
-[Pull requests](/contributing-code/pr-guidelines/) should be submitted to the **[creativecommons.github.io-source](https://github.com/creativecommons/creativecommons.github.io-source) repository**. The CC Open Source site is built using the static site generator [Lektor](https://www.getlektor.com/) and your blog post must follow the specific format documented below to appear correctly on the site. For example, please see [this commit adding a post](https://github.com/creativecommons/creativecommons.github.io-source/commit/eac3fbc23b7cadb58fe49d3af3286e4c8bf20d2f).
+[Pull requests](/contributing-code/pr-guidelines/) should be submitted to the **[ccos-website-source](https://github.com/creativecommons/ccos-website-source) repository**. The CC Open Source site is built using the static site generator [Lektor](https://www.getlektor.com/) and your blog post must follow the specific format documented below to appear correctly on the site. For example, please see [this commit adding a post](https://github.com/creativecommons/ccos-website-source/commit/eac3fbc23b7cadb58fe49d3af3286e4c8bf20d2f).
-1. Each blog entry lives in its own subdirectory of the [content/blog/entries](https://github.com/creativecommons/creativecommons.github.io-source/tree/main/content/blog/entries) folder. Create a new subdirectory with a [slugified](https://blog.tersmitten.nl/slugify/) version of your blog post title.
+1. Each blog entry lives in its own subdirectory of the [content/blog/entries](https://github.com/creativecommons/ccos-website-source/tree/main/content/blog/entries) folder. Create a new subdirectory with a [slugified](https://blog.tersmitten.nl/slugify/) version of your blog post title.
1. Create a file named `contents.lr` in the subdirectory you just created. This is the file that will contain your blog post content.
1. If your post uses images or other files, put them in the same subdirectory as the `contents.lr` file.
-1. Fill in `contents.lr` in the following format ([see example post](https://raw.githubusercontent.com/creativecommons/creativecommons.github.io-source/main/content/blog/entries/open-development-with-saltstack/contents.lr)):
+1. Fill in `contents.lr` in the following format ([see example post](https://raw.githubusercontent.com/creativecommons/ccos-website-source/main/content/blog/entries/open-development-with-saltstack/contents.lr)):
title: Replace this text with the title of your blog post
@@ -54,6 +54,8 @@ Once you have written your post, you can either send it to us (Markdown is easie
---
pub_date: Replace this text with the publication date in YYYY-MM-DD format.
---
+ excerpt: Replace this text with a summary of your blog post. This is an optional field. If left blank, the first 100 characters of your blog post will be used.
+ ---
body:
Replace this text with your post's content (minus the title). This field accepts Markdown for formatting.
If you're including images, you can use the Markdown image syntax i.e. .
@@ -62,17 +64,17 @@ Once you have written your post, you can either send it to us (Markdown is easie
*Read more about [Markdown formatting here](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet).*
-1. Create category pages for any new categories that you've assigned to your post. Each category has its own subdirectory in the [content/blog/categories](https://github.com/creativecommons/creativecommons.github.io-source/tree/main/content/blog/categories) directory.
+1. Create category pages for any new categories that you've assigned to your post. Each category has its own subdirectory in the [content/blog/categories](https://github.com/creativecommons/ccos-website-source/tree/main/content/blog/categories) directory.
* Create a folder that uses the **the exact category name** as the blog post with its own `contents.lr` file within.
- * The new `contents.lr` file within should follow the same format as the other categories. Here's an [example category content file](https://raw.githubusercontent.com/creativecommons/creativecommons.github.io-source/main/content/blog/categories/gsoc-2019/contents.lr).
-1. Similarly, if this is your first post, you'll need to create a file with author information. Each author has a subdirectory in the [content/blog/authors](https://github.com/creativecommons/creativecommons.github.io-source/tree/main/content/blog/authors) directory.
+ * The new `contents.lr` file within should follow the same format as the other categories. Here's an [example category content file](https://raw.githubusercontent.com/creativecommons/ccos-website-source/main/content/blog/categories/gsoc-2019/contents.lr).
+1. Similarly, if this is your first post, you'll need to create a file with author information. Each author has a subdirectory in the [content/blog/authors](https://github.com/creativecommons/ccos-website-source/tree/main/content/blog/authors) directory.
* Your author folder must have **the exact username** as the author field of the blog post and have a `contents.lr` file within.
* The `username` field in the `contents.lr` file should also use the same exact username.
- * The author's `contents.lr` file within should follow the same format as the other authors. Here's an [example author content file](https://raw.githubusercontent.com/creativecommons/creativecommons.github.io-source/main/content/blog/authors/TimidRobot/contents.lr).
-1. If your blog is part of a connected series, you'll need to make a file with series information. Each series has a subdirectory in the [content/blog/series](https://github.com/creativecommons/creativecommons.github.io-source/tree/main/content/blog/series) directory.
+ * The author's `contents.lr` file within should follow the same format as the other authors. Here's an [example author content file](https://raw.githubusercontent.com/creativecommons/ccos-website-source/main/content/blog/authors/TimidRobot/contents.lr).
+1. If your blog is part of a connected series, you'll need to make a file with series information. Each series has a subdirectory in the [content/blog/series](https://github.com/creativecommons/ccos-website-source/tree/main/content/blog/series) directory.
* Create a folder that uses the **the exact series name** as the blog post with its own `contents.lr` file within.
- * The new `contents.lr` file within should follow the same format as the other series. Here's an [example series content file](https://raw.githubusercontent.com/creativecommons/creativecommons.github.io-source/main/content/blog/series/gsoc-2019-vocabulary/contents.lr).
-1. Build the `creativecommons.github.io-source` project locally (instructions are in the `README` in the repository) and ensure your blog post shows up correctly locally. If you have not created the appropriate category or author files, you will see a build error in this step.
+ * The new `contents.lr` file within should follow the same format as the other series. Here's an [example series content file](https://raw.githubusercontent.com/creativecommons/ccos-website-source/main/content/blog/series/gsoc-2019-vocabulary/contents.lr).
+1. Build the `ccos-website-source` project locally (instructions are in the `README` in the repository) and ensure your blog post shows up correctly locally. If you have not created the appropriate category or author files, you will see a build error in this step.
1. Push your code and make a pull request.
1. Wait for a member of CC's fulltime staff to merge the post into the `main` branch.
diff --git a/content/contents.lr b/content/contents.lr
index 0f0dc2088..c4b8f8cfc 100644
--- a/content/contents.lr
+++ b/content/contents.lr
@@ -7,17 +7,24 @@ block_content:
#### hero ####
title:
-We have been building
free software at
Creative Commons for over a decade.
-----
-description:
-
-We work on code and products that support digital creativity and sharing, from usability of our legal tools to enabling discovery of CC-licensed content.
+We have been building
free software at
Creative Commons (CC) for over a decade.
----
links:
+
We work on code and products that support digital creativity and sharing, from usability of our legal tools to enabling discovery of CC-licensed content.
+
+
+
This site is for developers looking to contribute, but anyone can use CC tools to share their works.
#### get-involved ####
diff --git a/content/contributing-code/contents.lr b/content/contributing-code/contents.lr
index 83683dbcd..0f180de45 100644
--- a/content/contributing-code/contents.lr
+++ b/content/contributing-code/contents.lr
@@ -32,6 +32,13 @@ are some of the ones that are most relevant to finding a good issue to work on:
- You do not need our permission to work on one of these issues.
- You may work on an issue labeled
good
first issue even if it's not your first issue.
+ - Please don't ask for issue assignment or claim issues. Do the work and
+ submit a pull request (PR).
+ - Even if multiple people submit PRs for the same issue, multiple ideas and
+ implementations strengthen the final product.
+ - For work program applicants, each can all list their own PRs on their
+ application. It is the quality of work that is important, not whether it
+ is merged.
- **Issues not available for community contribution:**
- The following tags mark issues that are _not_ open for community
contribution:
@@ -81,12 +88,10 @@ on.
Once you've found an issue you'd like to work on, please follow these steps to
make your contribution:
-1. Comment on it and say you're working on that issue. This is to avoid
- conflicts with others also working on the issue. If you've followed the
- guidelines above, you don't need to ask permission to start work on an
- issue.
-2. Write your code and submit your pull request. Be sure to read and follow our
- **[pull request guidelines](/contributing-code/pr-guidelines/)!**
+1. If you have followed the guidelines above, you don't need to ask permission
+ to start work on an issue.
+2. Write your code and submit your pull request (PR). Be sure to read and
+ follow our **[pull request guidelines](/contributing-code/pr-guidelines/)!**
3. Wait for code review and address any issues raised as soon as you can.
**A note on collaboration:** We encourage people to collaborate as much as
@@ -123,3 +128,5 @@ When in doubt, ask a question on [one of our community forums](/community/).
Recurring donations to Creative Commons Open Source can be made via [Sponsor
@creativecommons on GitHub
Sponsors](https://github.com/sponsors/creativecommons).
+
+Thank you to our [Supporters](/supporters/)!
diff --git a/content/contributing-code/documentation-guidelines/contents.lr b/content/contributing-code/documentation-guidelines/contents.lr
new file mode 100644
index 000000000..f5efc80a6
--- /dev/null
+++ b/content/contributing-code/documentation-guidelines/contents.lr
@@ -0,0 +1,43 @@
+_model: page
+---
+_template: page-with-toc.html
+---
+title: Documentation Guidelines
+---
+description: This Documentation Guidelines (style guide) ensures all the files in all repositories and any other documentation are properly documented.
+---
+body:
+
+# Documentation guidelines
+
+The purpose of this guideline is to provide a step-by-step framework for writing and maintaining high-quality documentation for Creative Commons (CC) projects. This guide covers essential sections such as project style guide Preference, Style modification, terminologies, markdown usage. Following these guidelines ensures consistency, clarity, and ease of use for all contributors and users.
+
+## Style guide reference
+
+For general writing style and guidelines, refer to the following upstream style guides:
+
+- [Google Developer Style Guide (Preferred)](https://developers.google.com/style/)
+- [Microsoft Writing Style Guide](https://learn.microsoft.com/en-us/style-guide/welcome/)
+
+## Style preferences modifications
+
+While adhering to the upstream style guides, observe the following modifications:
+- All acronyms must be defined on first use
+- Use active voice wherever possible to improve clarity and engagement.
+- Keep sentences concise and to the point, avoiding jargon unless necessary.
+
+
+## Terminology
+
+Establishing a clear "Terminology" section for Creative Commons (CC)-specific usage is crucial. Below are some proprietary terms and their usage:
+
+- **Creative Commons (CC)**: A non-profit organization enabling sharing and reuse of creative works.
+- **Licenses**: Legal tools that allow creators to specify how their works can be used.
+- **Attribution**: Giving credit to the creator of a work, required by most CC licenses.
+
+
+## Markdown usage
+This section provides guidelines for using Markdown in documentation:
+- For comprehensive documentation on GitHub-flavored Markdown, refer to the [GitHub Markdown Guide](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax).
+- For additional information on the specific Markdown implementation used in Lektor, visit the [Lektor Markdown Documentation](https://www.getlektor.com/docs/content/#markdown).
+- Note: Use code block markup for instructions on installation, deployment, and development, especially to write code commands.
diff --git a/content/contributing-code/foundational-tech/contents.lr b/content/contributing-code/foundational-tech/contents.lr
new file mode 100644
index 000000000..eb6d2e20d
--- /dev/null
+++ b/content/contributing-code/foundational-tech/contents.lr
@@ -0,0 +1,221 @@
+_model: page
+---
+_template: page-with-toc.html
+---
+title: Foundational technologies
+---
+description: Most or many of Creative Commons' projects require a working
+knowledge of these foundational technologies.
+---
+body:
+
+
+## Step zero
+
+Welcome to Creative Commons (CC) software development! We are glad you are
+here! ❤️
+
+Before engaging with our projects, please ensure you have a working knowledge
+of the following technologies:
+1. Slack
+2. Command line interface (CLI)
+3. Code editor
+4. GitHub and git
+5. Docker
+
+
+## Slack
+
+Slack is currently our primary channel for chat and lower latency communication.
+
+For more information, see [Join the CC Developer Community](/community/).
+
+
+## Command line interface (CLI)
+
+Often shortened to just "command line" or referred to as the "console" or
+"terminal", the command line interface (CLI) is where quite a bit of software
+development work happens.
+
+
+### Getting started with the CLI
+
+- [Terminal Tutor – learn the Command Line interactively][terminal-tutor]
+
+[terminal-tutor]: https://www.terminaltutor.com/
+
+
+## Code editor
+
+A code editor or integrated development environment (IDE) provides strong
+support for software development. Which one you use is up to personal
+preference. The two editors used by the Technology team are currently Visual
+Studio Code (recommended) and Vim.
+
+
+### Visual Studio Code
+
+- [Visual Studio Code - Code Editing. Redefined][vscode]
+- Highlighted features:
+ - [Emmet in Visual Studio Code][emmet]
+- Recommended plugins:
+ - [Docker - Visual Studio Marketplace][vscode-docker] *makes it easy to
+ build, manage, and deploy containerized applications from Visual Studio
+ Code. It also provides one-click debugging of Node.js, Python, and .NET
+ inside a container.*
+ - [Prettier - Code formatter - Visual Studio Marketplace][prettier]: *is an
+ opinionated code formatter.*
+ - Prettier is especially helpful for Web develoment (HTML, JavaScript,
+ etc.)
+ - [Rewrap - Visual Studio Marketplace][rewrap]
+ - Some of our repositories hard wrap code and text at 80 characters
+
+[vscode]: https://code.visualstudio.com/
+[emmet]: https://code.visualstudio.com/docs/editor/emmet
+[vscode-docker]: https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-docker
+[prettier]: https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode
+[rewrap]: https://marketplace.visualstudio.com/items?itemName=stkb.rewrap
+
+
+### Vim
+
+- [welcome home : vim online](https://www.vim.org/)
+- Recommended plugins (install Vundle first):
+ - [godlygeek/tabular][tabular]: *Vim script for text filtering and alignment*
+ - (required by vim-markdown)
+ - [preservim/vim-markdown][vim-md]: *Markdown Vim Mode*
+ - [VundleVim/Vundle.vim][vundle]: *Vundle, the plug-in manager for Vim*
+
+[tabular]: https://github.com/godlygeek/tabular
+[vim-md]: https://github.com/preservim/vim-markdown
+[vundle]: https://github.com/VundleVim/Vundle.vim
+
+
+## GitHub and git
+
+All of our projects require a working knowledge of GitHub. It is our primary
+repository for code and we utilize many of the sites features for managing
+code and higher latency communication.
+
+[Git - Wikipedia](https://en.wikipedia.org/wiki/Git):
+> Git (/ɡɪt/) is a distributed version control system that tracks
+> versions of files. It is often used to control source code by programmers who
+> are developing software collaboratively.
+
+
+### Installing GitHub
+
+As a web service, GitHub doesn't require any installation. However, once you
+become more familiar with it, you may benefit from installing the GitHub
+command line utility:
+- [GitHub CLI | Take GitHub to the command line](https://cli.github.com/)
+
+
+### Installing git
+
+- **Linux:** Git is optimally installed using your distribution's package
+ manager. See [Git- Download for Linux and Unix][linux-git] for a wide range
+ of popular distros.
+- **macOS:** Mac users can install Git using these instructions: [Git -
+ Installing Git - Installing on macOS][macos-git]
+- **Windows:**
+ - You must use Windows 10 or 11 with Windows Subsystem for Linux (WSL2). For
+ installation instructions: see [Install WSL | Microsoft Learn][wsl2].
+ - Git should be installed within WSL2, using the appropriate Linux
+ installation method. For WSL2 Ubuntu, the command is:
+ ```shell
+ sudo apt-get install git
+ ```
+
+[linux-git]: https://git-scm.com/download/linux
+[macos-git]: https://git-scm.com/book/en/v2/Getting-Started-Installing-Git#_installing_on_macos
+[wsl2]: https://docs.microsoft.com/en-us/windows/wsl/install
+
+
+### Getting started with GitHub and Git
+
+Thankfully GitHub's documentation is relatively robust. Please see:
+- [Get started with GitHub documentation - GitHub Docs][github-start]
+ - [GitHub flow - GitHub Docs][github-flow]
+- [GitHub Training Manual][github-training]
+- [Fork a repository - GitHub Docs][github-fork]
+ - [Creating a pull request from a fork - GitHub Docs][github-forkpr]
+
+[github-start]: https://docs.github.com/en/get-started
+[github-flow]: https://docs.github.com/en/get-started/using-github/github-flow
+[github-training]: https://githubtraining.github.io/training-manual/#/
+[github-fork]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo
+[github-forkpr]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork
+
+
+### CC specifics for GitHub
+
+For some specifics on how we use GitHub, please see the following information
+on this site:
+- [Pull Request Guidelines — Creative Commons Open Source][ccos-prs]
+- [GitHub Repo Guidelines — Creative Commons Open Source][ccos-repos]
+- [Repository Labels — Creative Commons Open Source][ccos-labels]
+
+[ccos-prs]: /contributing-code/pr-guidelines/
+[ccos-repos]: /contributing-code/github-repo-guidelines/
+[ccos-labels]: /contributing-code/repo-labels/
+
+
+## Docker
+
+[Docker (software) - Wikipedia][wikipedia-docker]:
+> Docker is a set of platform as a service (PaaS) products that use OS-level
+> virtualization to deliver software in packages called containers. [...]
+>
+> Docker is a tool that is used to automate the deployment of applications in
+> lightweight containers so that applications can work efficiently in different
+> environments in isolation.
+
+[wikipedia-docker]: https://en.wikipedia.org/wiki/Docker_(software)
+
+
+### Installing Docker
+
+- **Linux:** Both Docker Desktop and Docker Engine are separately supported on
+ Linux. Both include the required Compose command plugin, but Docker Engine is
+ typically much easier to install:
+ - _Recommended:_ See [Install Docker Engine | Docker
+ Docs][linux-docker-engine] for links to installation instructions for
+ Docker Engine and Compose for various Linux distributions.
+ - See [Install Docker Desktop on Linux | Docker Docs][linux-docker-desktop]
+ for links to instructions for the graphical desktop app that includes the
+ commandline interface and Compose
+- **macOS:** Docker Desktop can be installed using these instructions: [Install
+ Docker Desktop on Mac | Docker Docs][macos-docker].
+- **Windows:** Docker Desktop should be installed on Windows itself and
+ integrated with Windows Subsystem for Linux (WSL2) as explained in [Docker
+ Desktop WSL 2 backend on Windows | Docker Docs][windows-docker]. Unlike Git,
+ you should not install Docker within your WSL2 environment. For installation
+ instructions: see [Install WSL | Microsoft Learn][wsl2].
+
+[linux-docker-engine]: https://docs.docker.com/engine/install
+[linux-docker-desktop]: https://docs.docker.com/desktop/install/linux-install
+[macos-docker]: https://docs.docker.com/desktop/install/mac-install
+[windows-docker]: https://docs.docker.com/desktop/windows/wsl
+[wsl2]: https://docs.microsoft.com/en-us/windows/wsl/install
+
+
+### Getting started with Docker
+
+- [A Docker Tutorial for Beginners][docker-tutorial]
+
+[docker-tutorial]: https://docker-curriculum.com/
+
+
+### Docker compose
+
+Our projects use [Docker Compose | Docker Docs][docker-compose].
+
+[docker-compose]: https://docs.docker.com/compose/
+
+
+## Next steps
+
+We have added a lot of documentation (ex. language guides) and tooling (issue
+finder) to this site that cover frequently asked questions and confusions.
+Please explore this site and reach out on Slack for additional assistance.
diff --git a/content/contributing-code/github-repo-guidelines/contents.lr b/content/contributing-code/github-repo-guidelines/contents.lr
index 78b5c3f1a..ad53b6a52 100644
--- a/content/contributing-code/github-repo-guidelines/contents.lr
+++ b/content/contributing-code/github-repo-guidelines/contents.lr
@@ -13,7 +13,40 @@ associated with the repository.
body:
-## Required Items
+## Organizational defaults
+
+The following organizational defaults are automatically applied to all
+repositories (per [Creating a default community health file - GitHub
+Docs][health-files]). Most repositories _shouldn't_ have their own copies of
+these files:
+- [`.github/PULL_REQUEST_TEMPLATE.md`][pr-template]: Pull request template
+ - All pull request templates _must_ include the full text of the [DCO][dco].
+- [`.github/ISSUE_TEMPLATE/bug_report.md`][issue-template-bug]: Bug report
+ issue template
+- [`.github/ISSUE_TEMPLATE/feature_request.md`][issue-template-feature]:
+ Feature request issue template
+- [`CODE_OF_CONDUCT.md`][conduct]: Code of Conduct
+ - [Adding a code of conduct to your project - GitHub Help][help-conduct]
+- [`CONTRIBUTING.md`][contributing]: contributor guidelines
+ - [Setting guidelines for repository contributors - GitHub
+ Help][setting-guidelines]
+- [`FUNDING.yml`][funding]: Displays a sponsor button
+- [`SUPPORT.md`][support]: Documentation on how to get help
+
+[health-files]: https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file
+[pr-template]: https://github.com/creativecommons/.github/blob/main/.github/PULL_REQUEST_TEMPLATE.md
+[dco]: https://developercertificate.org/
+[issue-template-bug]: https://github.com/creativecommons/.github/blob/main/.github/ISSUE_TEMPLATE/bug_report.md
+[issue-template-feature]: https://github.com/creativecommons/.github/blob/main/.github/ISSUE_TEMPLATE/feature_request.md
+[conduct]: https://github.com/creativecommons/.github/blob/main/CODE_OF_CONDUCT.md
+[help-conduct]: https://help.github.com/en/articles/adding-a-code-of-conduct-to-your-project
+[contributing]: https://github.com/creativecommons/.github/blob/main/CONTRIBUTING.md
+[setting-guidelines]: https://help.github.com/en/articles/setting-guidelines-for-repository-contributors
+[funding]: https://github.com/creativecommons/.github/blob/main/FUNDING.yml
+[support]: https://github.com/creativecommons/.github/blob/main/SUPPORT.md
+
+
+## Required items
All GitHub repositories should have the following items to be considered fully
ready for external contributors.
@@ -24,79 +57,74 @@ ready for external contributors.
- `/.github/CODEOWNERS`: Defined code owners
- [About code owners - GitHub Help][about-owners]
- `/.cc-metadata.yml`: The standard [CC metadata YAML file](#cc-metadata-file).
-- `/CODE_OF_CONDUCT.md`: Code of Conduct
- - Feel free to use our standard [`CODE_OF_CONDUCT.md`][conduct] file from
- [creativecommons/.github][dot-github]
- - [Adding a code of conduct to your project - GitHub Help][help-condcut]
- `/LICENSE`: license file.
-- `/CONTRIBUTING.md`: contributor guidelines
- - Can be project-specific or our standard [`CONTRIBUTING.md`][contributing]
- file from [creativecommons/.github][dot-github]
- - [Setting guidelines for repository contributors - GitHub
- Help][setting-guidelines]
-- `/README.md`: read me information file
- - Must documents how to install and build the project locally and documents a
+- `/README.md`: repository information file
+ - begin with an H1 heading identical to repository name followed by a
+ repository description
+ - Must document how to install and build the project locally and documents a
high level overview of the project and code structure. It should also link
to any other available documentation.
-- **All pull request templates must include the full text of the [DCO][dco].**
+ - Must document the Code of Conduct. For example, see the [Code of
+ Conduct][section-coc] `README.md` section in
+ `creativecommons/index-dev-env`.
+ - Must document Contributing. For example, see the
+ [Contributing][section-contrib] `README.md` section in
+ `creativecommons/index-dev-env`.
[about-owners]: https://help.github.com/en/articles/about-code-owners
-[conduct]: https://github.com/creativecommons/vocabulary/blob/main/CODE_OF_CONDUCT.md
-[dot-github]: https://github.com/creativecommons/.github
-[help-condcut]: https://help.github.com/en/articles/adding-a-code-of-conduct-to-your-project
-[contributing]: https://github.com/creativecommons/vocabulary/blob/main/CONTRIBUTING.md
-[setting-guidelines]: https://help.github.com/en/articles/setting-guidelines-for-repository-contributors
-[dco]: https://developercertificate.org/
-
+[section-coc]: https://github.com/creativecommons/index-dev-env/blob/main/README.md#code-of-conduct
+[section-contrib]: https://github.com/creativecommons/index-dev-env/blob/main/README.md#contributing
-### Additional Items
-- CI and code style linters that run automatically whenever new code is pushed
- (if applicable to the project).
-- At least a couple of automated tests (if applicable to the project).
+## Additional items
+As applicable or appropriate, each repository should include:
+- GitHub Actions for formatting, linting, styling, etc.
+- GitHub Actions for unit tests
-## Optional items
-- [Issue templates][issue-templates]. GitHub pulls the default templates from
- our [`.github` repository][dot-github] automatically, but if you want/need to
- customize them, create them in your repository.
-- A [pull request template][pr-template]. GitHub pulls the default template
- from our [`.github` repository][dot-github] automatically, but if you
- want/need to customize it, create it in your repository.
-- [Support resources][support-resources]. GitHub pulls the default `SUPPORT.md`
- file from our [`.github` repository][dot-github] automatically, but if you
- want/need to customize it, create it in your repository.
+## Repository configuration
-[issue-templates]: https://help.github.com/en/articles/creating-issue-templates-for-your-repository
-[dot-github]: https://github.com/creativecommons/.github
-[pr-template]: https://help.github.com/en/articles/creating-a-pull-request-template-for-your-repository
-[support-resources]: https://help.github.com/en/articles/adding-support-resources-to-your-project
+- Main page: About ⚙️ (Edit repository details)
+ - Description should match `README.md`
+ - Add appropriate Topics
+ - Disable/Uncheck any of the "Include in home page" that are not relevant to
+ the repository (ex. if no packages are provided, uncheck Packages).
+- Settings: General
+ - Features
+ - Disable/Uncheck Wikis unless you are going to use that feature
+ - Disable/Uncheck Discussions unless you are going to use that feature
+ - Disable/Uncheck Projects unless you are going to use that feature
+ - Pull Requests
+ - Enable/check Automatically delete head branches
+- Settings: Collaborators and teams
+ - Ensure, at a minimum that the team in `/.github/CODEOWNERS` has write
+ permissions
-## Standard Labels
+## Standard labels
All repositories must contain a set of standard labels, [documented
here](/contributing-code/repo-labels/), which comprise of common labels in
addition to repository-specific skill labels. You don't have to set these up
manually. The labels are [automatically
-managed](https://github.com/creativecommons/ccos-scripts) on all CC
-repositories, and so, must not be renamed.
+managed](https://github.com/creativecommons/ccos-scripts) on all Creative
+Commons (CC) repositories, and so, must not be renamed.
Repositories may contain additional custom labels as well which will remain
unaffected by the sync. It is recommended that custom labels be explained in
the contribution guidelines for that project.
-## Branch Protections
+## Branch protections
-Branch protections are automatically set up by CC staff via
+Branch protections are automatically set up by CC team members via
[creativecommons/ccos-scripts](https://github.com/creativecommons/ccos-scripts).
By default, pushing directly to the *default branch* (ex. `main`) is disabled
and all pull requests require review by at least one person before merge.
-## CC Metadata file
+## CC metadata file
Each repo should have a `.cc-metadata.yml` file in the root directory with the
following structure:
@@ -106,8 +134,8 @@ following structure:
engineering_project: true
# Name of the repository/project in English
english_name: CC Catalog API
-# All technologies used
-technologies: Python, Django, Django REST Framework, Elasticsearch
+# All technologies used, sorted
+technologies: Django, Django REST Framework, Elasticsearch, Python
# Whether this repository should be featured on the CC Open Source site's "Projects" page
featured: false
# Slack channel name (optional key)
diff --git a/content/contributing-code/issue-finder/contents.lr b/content/contributing-code/issue-finder/contents.lr
index 3082200f2..2f722179c 100644
--- a/content/contributing-code/issue-finder/contents.lr
+++ b/content/contributing-code/issue-finder/contents.lr
@@ -4,10 +4,10 @@ _template: issue_finder.html
---
title: Issue Finder
---
-description: Welcome to the CC developer community! We're absolutely delighted
-to have you here. If you want to contribute but are unsure where to start, you
-can use this issue finder to find an issue that matches your skills and
-experience level.
+description: Welcome to the Creative Commons (CC) developer community! We're
+absolutely delighted to have you here. If you want to contribute but are unsure
+where to start, you can use this issue finder to find an issue that matches
+your skills and experience level.
---
body:
diff --git a/content/contributing-code/pr-guidelines/contents.lr b/content/contributing-code/pr-guidelines/contents.lr
index a458bec52..a89a61aba 100644
--- a/content/contributing-code/pr-guidelines/contents.lr
+++ b/content/contributing-code/pr-guidelines/contents.lr
@@ -4,7 +4,12 @@ _template: page-with-toc.html
---
title: Pull Request Guidelines
---
-description: We ask that contributors to CC projects submit a pull request with your changes. If you're not familiar with pull requests, please read [this GitHub documentation](https://help.github.com/en/articles/about-pull-requests). Here are our expectations for pull requests; following them will expedite the process of merging your code in.
+description: We ask that contributors to Creative Commons (CC) projects submit
+a pull request with your changes. If you're not familiar with pull requests,
+please read [this GitHub documentation][github-pr]. Here are our expectations
+for pull requests; following them will expedite the process of merging your
+code in.
+[github-pr]: https://help.github.com/en/articles/about-pull-requests
---
body:
diff --git a/content/contributing-code/repo-labels/contents.lr b/content/contributing-code/repo-labels/contents.lr
index de0494d1c..53d6e355e 100644
--- a/content/contributing-code/repo-labels/contents.lr
+++ b/content/contributing-code/repo-labels/contents.lr
@@ -4,13 +4,16 @@ _template: page-with-toc.html
---
title: Repository Labels
---
-description: To facilitate the community in finding ways to contribute that match their experiences and skillsets, we have developed a comprehensive system for labelling issues and PRs. This is an introduction to this standard labelling scheme.
+description: To facilitate the community in finding ways to contribute that
+match their experiences and skillsets, we have developed a comprehensive system
+for labelling issues and PRs. This is an introduction to this standard
+labelling scheme.
---
body:
-Labels consist of three fields, viz. name, description and color. Label names
-should have a consistent format to aid both filtering within the github UI as
-well as scanning visually through the list. The following format is the most
+Labels consist of three fields, viz. name, description and color. Label names
+should have a consistent format to aid both filtering within the github UI as
+well as scanning visually through the list. The following format is the most
suited to this task (where `⎵` denotes a single space):
```
@@ -31,6 +34,7 @@ An issue has many different attributes:
- Talk
- Friendliness
+
### *Priority
@@ -59,8 +63,8 @@ An issue has many different attributes:
-The priority of an issue is based on its impact, derived from a combination of
-urgency and importance. This determines the importance of the issue when sprint
+The priority of an issue is based on its impact, derived from a combination of
+urgency and importance. This determines the importance of the issue when sprint
planning or deciding which issues to tackle next.
-
@@ -80,6 +84,7 @@ planning or deciding which issues to tackle next.
- **Description:** Low priority and doesn't need to be rushed
+
### *Status
@@ -112,32 +117,24 @@ The status of the issue determines whether it is ready for work or not. Issues
may not be ready to be worked on for a number of reasons and the maintainers
must keep updating the labels as the situation evolves.
-An issue, at the time of closing can have either the
+An issue, at the time of closing can have either the
🏁 status: ready for dev
-or the
+or the
⛔️ status: discarded
label based on whether it was closed with or without resolution, respectively.
--
- 🏁 status: ready for dev
+-
+ 🚦 status: awaiting triage
- - **Description:** Ready for work
+ - **Description:** Has not been triaged & therefore, not ready for work
-
🚧 status: blocked
- **Description:** Blocked & therefore, not ready for work
--
- 🧹 status: ticket work required
-
- - **Description:** Needs more details before it can be worked on
--
- 🏷 status: label work required
-
- - **Description:** Needs proper labelling before it can be worked on
-
⛔️ status: discarded
@@ -146,10 +143,19 @@ label based on whether it was closed with or without resolution, respectively.
🙅 status: discontinued
- **Description:** Not suitable for work as repo is in maintenance
--
- 🚦 status: awaiting triage
+-
+ 🏷 status: label work required
- - **Description:** Has not been triaged & therefore, not ready for work
+ - **Description:** Needs proper labelling before it can be worked on
+-
+ 🏁 status: ready for dev
+
+ - **Description:** Ready for work
+-
+ 🧹 status: ticket work required
+
+ - **Description:** Needs more details before it can be worked on
+
### *Goal
@@ -158,10 +164,11 @@ represents the impact of the issue on the scope of the software.
- ⭐ goal: addition
- **Description:** Addition of new feature
-- ✨ goal: improvement
- - **Description:** Improvement to an existing feature
- 🛠 goal: fix
- **Description:** Bug fix
+- ✨ goal: improvement
+ - **Description:** Improvement to an existing feature
+
### *Aspect
@@ -169,43 +176,48 @@ The aspect of an issue is the side of the project that the issue deals with. A
single codebase can have multiple aspects to it and knowing which ones will be
touched helps contributors find relevant issues.
-- 📄 aspect: text
- - **Description:** Concerns the textual material in the repository
- 💻 aspect: code
- **Description:** Concerns the software code in the repository
-- 🕹 aspect: interface
- - **Description:** Concerns end-users' experience with the software
+- 📖 aspect: docs
+ - **Description:** Concerns the documentation in the repository
- 🤖 aspect: dx
- **Description:** Concerns developers' experience with the codebase
+- 🕹 aspect: interface
+ - **Description:** Concerns end-users' experience with the software
+- 📄 aspect: text
+ - **Description:** Concerns the textual material in the repository
+
### Skill
-The technical skills a person is required to possess to work on the issue.
+The technical skills a person is required to possess to work on the issue.
Skills are a special type of label that vary by repository. Issues may not have
a skill tag if no special skills are required.
- 💪 skill: <skill name>
- **Description:** Requires proficiency in '<skill name>'
+
### Talk
Issues with interaction labels do not entail any work to be done on the
-repository. They are for Q&A, RFCs and any other form of discussions. While both
-of these may appear to be too similar, triage permissions are granted to
+repository. They are for Q&A, RFCs and any other form of discussions. While
+both of these may appear to be too similar, triage permissions are granted to
collaborators who might not have the answers to questions but by labelling them
as such, they might draw a faster response from an experienced contributor who
-does. _In the future this category might be rendered redundant by GitHub
+does. _In the future this category might be rendered redundant by GitHub
Discussions and will be removed._
-- ❓ talk: question
- - **Description:** Can be resolved with an answer
- 💬 talk: discussion
- **Description:** Open for discussions and feedback
+- ❓ talk: question
+ - **Description:** Can be resolved with an answer
+
### Friendliness
-The level of friendliness a particular issue is the valency of the issue
-towards contributions from the community. Some issues provide a great
+The level of friendliness a particular issue is the valency of the issue
+towards contributions from the community. Some issues provide a great
introduction while others require a little more familiarity with the codebase.
_These issues do not have the category prefix as two of them are special labels
recognized by GitHub. The special ones don't have emojis either._
@@ -215,7 +227,8 @@ recognized by GitHub. The special ones don't have emojis either._
- help wanted
- **Description:** Open to participation from the community
- 🔒 staff only
- - **Description:** Restricted to CC staff members
+ - **Description:** Restricted to Creative Commons (CC) team members
+
### Miscellaneous
@@ -223,22 +236,19 @@ recognized by GitHub. The special ones don't have emojis either._
🤯 ノಠ益ಠノ彡┻━┻
- **Description:** Aaargh!
--
- Hacktoberfest
-
- - **Description:** Good issues for Hacktoberfest participants
-
invalid
- **Description:** Inappropriate or invalid (ex. Hacktoberfest spam)
+
## Usage rules
In the above categories, some are marked with an `*` sign. Those are mandatory
categories and every issue is required to have at least one label from those
categories.
-Only issues labelled with
+Only issues labelled with
🚦 status: awaiting triage
@@ -246,4 +256,4 @@ are allowed to not have all mandatory labels (seeing as they have not been
triaged yet).
Categories not marked with an `*` are optional and it is upto the discretion of
-the maintainers to have apply labels from those categories to issues.
\ No newline at end of file
+the maintainers to have apply labels from those categories to issues.
diff --git a/content/contributing-code/translation-guide/contents.lr b/content/contributing-code/translation-guide/contents.lr
index 99e6c70ab..058185671 100644
--- a/content/contributing-code/translation-guide/contents.lr
+++ b/content/contributing-code/translation-guide/contents.lr
@@ -4,14 +4,17 @@ _template: page-with-toc.html
---
title: Translation Guide
---
-description: Our translation files are hosted and managed on [Transifex](https://www.transifex.com). It's very easy to sign up for an account and start translation CC services into another language.
+description: Our translation files are hosted and managed on
+[Transifex](https://www.transifex.com). It is very easy to sign up for an
+account and start translation Creative Commons (CC) services into another
+language.
---
body:
-CC applications such as CC Search and the CC License Chooser are used by
-millions of users worldwide. Translating these services into the languages our
-users speak and read is integral to making these services accessible to our
-diverse user base.
+CC applications such as CC Search and the CC Chooser are used by millions of
+users worldwide. Translating these services into the languages our users speak
+and read is integral to making these services accessible to our diverse user
+base.
We use Transifex to manage our translation files. It provides an intuitive UI
and many useful tools. Let's see how you can join us there and get started.
@@ -19,16 +22,17 @@ and many useful tools. Let's see how you can join us there and get started.
TL;DR: We have a [video version](https://www.youtube.com/watch?v=Rta2AlPww8M)
of this tutorial if you prefer that as the medium of instruction.
+
## For translators
-* **Sign up on Transifex**
- * Visit the Transifex [sign up page](https://www.transifex.com/signup/) and
+- **Sign up on Transifex**
+ - Visit the Transifex [sign up page](https://www.transifex.com/signup/) and
fill out the form to create an account.
- * You can create a new account using your email address, a username and a
+ - You can create a new account using your email address, a username and a
password.
- * Alternatively you can link an existing account from GitHub, Google or
+ - Alternatively you can link an existing account from GitHub, Google or
LinkedIn to avoid having to remember another password.
- * During the sign up process, you will be asked for the languages you speak.
+ - During the sign up process, you will be asked for the languages you speak.
Remember to fill it as comprehensively as possible.
@@ -38,12 +42,12 @@ of this tutorial if you prefer that as the medium of instruction.
src="./transifex_signup.png">
-* **Verify your email**
+- **Verify your email**
You will receive an email from Transifex on the email address you signed up.
Clicking the link in the email will verify that you used an authentic email to
sign up and enable all the features on your account.
-* **Visit the CC Organisation page**
+- **Visit the CC Organisation page**
The [organisation page](https://www.transifex.com/creativecommons/public/)
contains links to all CC projects currently in translation.
@@ -54,7 +58,7 @@ of this tutorial if you prefer that as the medium of instruction.
src="./transifex_org_page.png">
-* **Choose a project**
+- **Choose a project**
Choose any project from the list that you would like to translate. Click on
the project name to go to the project page.
@@ -65,18 +69,21 @@ of this tutorial if you prefer that as the medium of instruction.
src="./transifex_summit.png">
-* **Join the team**
- * You can see a list of languages that each project has been translated into.
+- **Join the team**
+ - You can see a list of languages that each project has been translated into.
Not all languages are visible. Click on the 'Display all languages' button
to see them all.
- * If your language isn't present in the list, you can request for it by
+ - If your language isn't present in the list, you can request for it by
clicking the 'Request language' button. You will have to go to the previous
step and find a different project till your language request is approved.
- * If your language is present, click on the 'Join team' button to join the
+ - If your language is present, click on the 'Join team' button to join the
team that's translating this project.
- * In the modal choose your language and click the 'Join' button. You'll
- receive a notification that a request has been submitted. Wait for an
- administrator to add you to the team.
+ - In the modal choose your language and click the 'Join' button. You'll
+ receive a notification that a request has been submitted.
+ - Notify the `cc-translation` channel on Slack
+ - See [Join the CC Developer Community — Creative Commons Open
+ Source](/community/) for instructions on joining Slack
+ - Wait for an administrator to add you to the team.
-* **Getting around**
- * You'll receive an email when your request has been accepted.
- * When you log back in to Transifex, you'll see some changes in the UI.
- * You'll have Creative Commons mentioned in the organisation dropdown.
- * You'll see CC projects in the left sidebar.
- * Click on the project of your choice from the sidebar.
+- **Getting around**
+ - You'll receive an email when your request has been accepted.
+ - When you log back in to Transifex, you'll see some changes in the UI.
+ - You'll have Creative Commons mentioned in the organisation dropdown.
+ - You'll see CC projects in the left sidebar.
+ - Click on the project of your choice from the sidebar.
-* **Translate the strings**
- * Find your language from the list of languages. Hovering over the name will
+- **Translate the strings**
+ - Find your language from the list of languages. Hovering over the name will
reveal a 'View resource' button.
- * Click on the 'View resource' button. That should take you to the page of
+ - Click on the 'View resource' button. That should take you to the page of
that particular language. It contains the resources that you need to
translate.
- * Clicking on the resource opens a modal describing the words and strings that
+ - Clicking on the resource opens a modal describing the words and strings that
remain to be translated. Here onwards you have three paths for translating
the site.
- Transifex editor UI, by clicking the 'Translate' button
@@ -119,18 +126,20 @@ of this tutorial if you prefer that as the medium of instruction.
src="./transifex_resource_modal.png">
-* * **Method 1: Translating using the Transifex editor UI**
- * To do this, click on the 'Translate' button from the resource modal. You
- will be taken to a list of all the strings from the website.
- * Switch the language to your target language using the menu bar on the
- upper side of the screen.
- * Click on any string, enter the translation in the lower box and click
- the 'Save Translation' button to commit the change.
- * Some text has HTML tags in it. In those cases you can click on the tags in
- the source text to copy them over in the translated text. You can also
- drag to move them around as needed.
- * Keep [these instructions](https://wiki.creativecommons.org/wiki/Translating_CC_Deeds#General_Notes_About_Translating)
- in mind.
+- **Method 1: Translating using the Transifex editor UI**
+ - To do this, click on the 'Translate' button from the resource modal. You
+ will be taken to a list of all the strings from the website.
+ - Switch the language to your target language using the menu bar on the upper
+ side of the screen.
+ - Click on any string, enter the translation in the lower box and click the
+ 'Save Translation' button to commit the change.
+ - Some text has HTML tags in it. In those cases you can click on the tags in
+ the source text to copy them over in the translated text. You can also drag
+ to move them around as needed.
+ - Keep these instructions in mind: [General Notes About Translating -
+ Translating CC Deeds - CC Public Wiki][wiki-translate-notes]
+
+[wiki-translate-notes]: https://wiki.creativecommons.org/wiki/Translating_CC_Deeds#General_Notes_About_Translating
-* * **Method 2: Translating using the Transifex live UI**
- * To do this, click on the 'Live' button from the resource modal. You will
- be taken to the website rendered in the Transifex page and you can edit
- the text directly.
- * Switch the language to your target language using the sidebar on the right
- side of the screen.
- * All the text is green boxes can be translated. Click on the pencil icon
- that appears when you move your mouse over the green boxes.
- * Enter your translated string in the lower box and press the 'Save' button
- to confirm the translation.
+- **Method 2: Translating using the Transifex live UI**
+ - To do this, click on the 'Live' button from the resource modal. You will be
+ taken to the website rendered in the Transifex page and you can edit the
+ text directly.
+ - Switch the language to your target language using the sidebar on the right
+ side of the screen.
+ - All the text is green boxes can be translated. Click on the pencil icon
+ that appears when you move your mouse over the green boxes.
+ - Enter your translated string in the lower box and press the 'Save' button
+ to confirm the translation.
-* * **Method 3: Translating strings locally**
- * To do this, you can download the JSON file that maps English strings to
- their counterparts in your language by clicking the 'Download file to
- translate' button.
- * For the untranslated strings, both key and value will be the same.
- ```json
- { "Hello, World!": "Hello, World!" }
- ```
- * Change the JSON values to the translated text.
- ```json
- { "Hello World": "नमस्ते, दुनिया!" }
- ```
- * Upload the translated JSON file using the 'Upload file' button.
+- **Method 3: Translating strings locally**
+ - To do this, you can download the JSON file that maps English strings to
+ their counterparts in your language by clicking the 'Download file to
+ translate' button.
+ - For the untranslated strings, both key and value will be the same.
+ ```json
+ { "Hello, World!": "Hello, World!" }
+ ```
+ - Change the JSON values to the translated text.
+ ```json
+ { "Hello World": "नमस्ते, दुनिया!" }
+ ```
+ - Upload the translated JSON file using the 'Upload file' button.
Your translations will go live as soon as they are approved by the admins.
+
## For admins
-* **Approve team join requests**
- * Click on the person's name to see their profile. That could help in
+- **Approve team join requests**
+ - Click on the person's name to see their profile. That could help in
determining the credibility of the candidate.
- * Click the 'Accept' button if you want to add the collaborator to the team.
+ - Click the 'Accept' button if you want to add the collaborator to the team.
You'll receive a notification confirming the acceptance of the translator.
@@ -188,12 +198,12 @@ Your translations will go live as soon as they are approved by the admins.
src="./transifex_join_request.png">
-* **Review translations**
- * Navigate to the resource as described for translators in the 'Translate the
+- **Review translations**
+ - Navigate to the resource as described for translators in the 'Translate the
strings' section.
- * In the resource modal that appears, click on the 'View strings online'
+ - In the resource modal that appears, click on the 'View strings online'
button. You will be taken to the strings page.
- * Click on the 'Unreviewed' tab. Approve or decline the translation as
+ - Click on the 'Unreviewed' tab. Approve or decline the translation as
applicable.
@@ -201,4 +211,11 @@ Your translations will go live as soon as they are approved by the admins.
style="max-height: 503px; border: 1px solid #ccc;"
alt="Screenshot of the Transifex 'Unreviewed translations' page"
src="./transifex_review_translation.png">
-
\ No newline at end of file
+
+
+
+## Additional resources
+
+- [Translate - CC Public Wiki][wiki-translate]
+
+[wiki-translate]: https://wiki.creativecommons.org/wiki/Translate
diff --git a/content/contributing-code/usability/contents.lr b/content/contributing-code/usability/contents.lr
index fb84ea841..47503299c 100644
--- a/content/contributing-code/usability/contents.lr
+++ b/content/contributing-code/usability/contents.lr
@@ -6,7 +6,7 @@ title: Usability
---
body:
-At CC, our goal is to make our products as easy and delightful to use as possible. To that end, we are constantly talking to our users. Sometimes our sessions involve understanding current experiences and identifying pain points, other times we’re determining upcoming feature prioritization. If we plan to roll out a new product, or design a new interface or feature for an existing product, we do research! We appreciate our users volunteering their time to help us with this research by participating in test sessions.
+At Creative Commons (CC), our goal is to make our products as easy and delightful to use as possible. To that end, we are constantly talking to our users. Sometimes our sessions involve understanding current experiences and identifying pain points, other times we’re determining upcoming feature prioritization. If we plan to roll out a new product, or design a new interface or feature for an existing product, we do research! We appreciate our users volunteering their time to help us with this research by participating in test sessions.
## Participate in a Session
When we’re rolling out a specific feature, we do **usability tests** to test the proposed experience.
diff --git a/content/multiple-authors.jpg b/content/multiple-authors.jpg
new file mode 100644
index 000000000..775b5e6f3
Binary files /dev/null and b/content/multiple-authors.jpg differ
diff --git a/content/programs/applicant-guide/contents.lr b/content/programs/applicant-guide/contents.lr
index 807366c9d..41d2d1b64 100644
--- a/content/programs/applicant-guide/contents.lr
+++ b/content/programs/applicant-guide/contents.lr
@@ -5,10 +5,11 @@ _template: page-with-toc.html
title: Open Source Work Programs: Applicant Guide
---
description:
-CC participates in open source work programs such as Google Summer of Code
-(GSoC) and Outreachy. Both CC staff and community members are welcome to lead
-projects. Details about specific programs and rounds are listed in the
-[Overview page](/programs); this page serves as a general guide to applicants.
+Creative Commons (CC) participates in open source work programs such as Google
+Summer of Code (GSoC) and Outreachy. Both CC team members and community members
+are welcome to lead projects. Details about specific programs and rounds are
+listed in the [Overview page](/programs); this page serves as a general guide
+to applicants.
---
body:
diff --git a/content/programs/contents.lr b/content/programs/contents.lr
index 695a9c4ce..cf0b71858 100644
--- a/content/programs/contents.lr
+++ b/content/programs/contents.lr
@@ -22,27 +22,21 @@ CC isn't currently participating in Google Season of Docs (GSoD).
### Google Summer of Code
-CC is participating in Google Summer of Code (GSoC) 2023.
+CC is [Skipping Google Summer of Code (GSoC) 2025][skipping2025]. We hope to
+apply again to participate in 2026.
- [Program website](https://summerofcode.withgoogle.com/)
-- [CC's GSoC 2023 page][gsoc2023cc]
-[gsoc2023cc]: https://summerofcode.withgoogle.com/programs/2023/organizations/creative-commons
+[skipping2025]: /blog/entries/2025-01-15-skipping-gsoc-2025/
### Outreachy
-CC is participating in the [Outreachy December 2022 to March 2023
-Internships][dec2022].
-
-CC isn't participating in the May 2023 internships.
-
-CC will participate in the December 2023 internships.
+CC is participating in the December 2024 cohort. We are planning on also participating in the December 2025 cohort.
- [Program website](https://www.outreachy.org/)
- [CC's Outreachy page][outreachycc]
-[dec2022]: https://www.outreachy.org/apply/project-selection/#creative-commons
[outreachycc]: https://www.outreachy.org/communities/cfp/creative-commons/
@@ -68,16 +62,21 @@ CC will participate in the December 2023 internships.
| Name | Pronouns | Slack Username | Time Zone |
| ---- | -------- | -------------- | --------- |
-| [Sara][authorsara] | she/her | `@sara` | Central (CDT UTC-06:00 / CST UTC-05:00) |
-| [Timid Robot][authortimidrobot] | they/them | `@Timid Robot` | Pacific (PDT UTC-08:00 / PST UTC-07:00) |
+| [Sara][authorsara] | she/her | `@sara` | Central (CDT UTC-05:00 / CST UTC-06:00) |
+| [Shafiya][authorshafiya] | she/her | `@Shafiya Heena` | Eastern (EDT UTC-04:00 / EST UTC-05:00) |
+| [Timid Robot][authortimidrobot] | they/them | `@Timid Robot` | Pacific (PDT UTC-07:00 / PST UTC-08:00) |
[authorsara]: /blog/authors/sara/
+[authorshafiya]: /blog/authors/shafiya/
[authortimidrobot]: /blog/authors/TimidRobot/
+
## Other Opportunities
-Apart from the mentioned Creative Commons collaborations, there are numerous additional ways to enhance your knowledge and make meaningful contributions to open source communities:
+Apart from the mentioned Creative Commons collaborations, there are numerous
+additional ways to enhance your knowledge and make meaningful contributions to
+open source communities:
- [tapaswenipathak/Open-Source-Programs][otherprogs]: A list of open source
programs.
-[otherprogs]: https://github.com/tapaswenipathak/Open-Source-Programs
\ No newline at end of file
+[otherprogs]: https://github.com/tapaswenipathak/Open-Source-Programs
diff --git a/content/programs/contrib-guide/contents.lr b/content/programs/contrib-guide/contents.lr
index 6a9f7e244..02f9af04c 100644
--- a/content/programs/contrib-guide/contents.lr
+++ b/content/programs/contrib-guide/contents.lr
@@ -5,10 +5,11 @@ _template: page-with-toc.html
title: Open Source Work Programs: Contributor Guide
---
description:
-CC participates in open source work programs such as GSoC and Outreachy. Both
-CC staff and community members are welcome to lead projects. Details about
-specific programs and rounds are listed in the [Overview page](/programs); this
-page serves as a general guide for accepted contributors.
+Creative Commons (CC) participates in open source work programs such as Google
+Summer of Code (GSoC) and Outreachy. Both CC team members and community members
+are welcome to lead projects. Details about specific programs and rounds are
+listed in the [Overview page](/programs); this page serves as a general guide
+for accepted contributors.
---
body:
diff --git a/content/programs/history/contents.lr b/content/programs/history/contents.lr
index a2a285b88..ebbee9672 100644
--- a/content/programs/history/contents.lr
+++ b/content/programs/history/contents.lr
@@ -22,39 +22,20 @@ first time in 2020.
## Google Summer of Code
-CC has participated in Google Summer of Code (GSoC) nine times since 2006:
+CC has participated in Google Summer of Code (GSoC) ten times since 2006:
- *[All GSoC Open Source Blog posts](/blog/categories/gsoc/)*
+- [Google Summer of Code 2024](https://summerofcode.withgoogle.com/archive/2024/organizations/creative-commons)
+ - [Open Source Blog Posts](/blog/categories/gsoc-2024/)
+- [Google Summer of Code
+ 2023](https://summerofcode.withgoogle.com/archive/2023/organizations/creative-commons)
+ - [Open Source Blog posts](/blog/categories/gsoc-2023/)
- [Google Summer of Code
2020](https://summerofcode.withgoogle.com/archive/2020/organizations/5450793232105472/)
- [Open Source Blog posts](/blog/categories/gsoc-2020/)
- - [Welcome Our Interns from Google Summer of Code and
- Outreachy!](https://creativecommons.org/2020/05/11/welcome-interns-google-summer-of-code-and-outreachy/)
- - [The Improved CC
- Search](https://creativecommons.org/2020/12/15/the-improved-cc-search/)
- - [Important Updates to the Creative Commons
- Catalog](https://creativecommons.org/2020/11/02/updates-to-the-creative-commons-catalog/)
- - [New Improvements in the CC Search Browser
- Extension](https://creativecommons.org/2020/12/07/new-improvements-in-the-cc-search-browser-extension/)
- - [The Linked Commons 2.0: What’s
- New?](https://creativecommons.org/2020/11/04/the-linked-commons-2-0-whats-new/)
- [Google Summer of Code
2019](https://summerofcode.withgoogle.com/archive/2019/organizations/5500455663173632/)
- [Open Source Blog posts](/blog/categories/gsoc-2019/)
- - [CC + Google Summer of Code
- 2019](https://creativecommons.org/2019/03/04/cc-google-summer-of-code-2019/)
- - [Meet CC’s 2019 Google Summer of Code
- students](https://creativecommons.org/2019/05/30/meet-ccs-2019-google-summer-of-code-students/)
- - [Introducing the Updated Creative Commons WordPress
- Plugin](https://creativecommons.org/2019/11/22/updated-cc-wordpress-plugin/)
- - [Introducing CC Vocabulary, Our New Web Design
- System](https://creativecommons.org/2019/12/13/cc-vocabulary-web-design-system/)
- - [Introducing the CC Search Browser
- Extension](https://creativecommons.org/2020/01/06/cc-search-browser-extension/)
- - [Introducing the Linked
- Commons](https://creativecommons.org/2020/01/23/introducing-the-linked-commons/)
- - [Here’s a Sneak Peek at the Updated Creative Commons
- Chooser](https://creativecommons.org/2020/01/27/the-new-cc-license-chooser/)
- [Google Summer of Code
2013](https://www.google-melange.com/archive/gsoc/2013/orgs/cc)
- [Google Summer of Code
@@ -73,23 +54,18 @@ CC has participated in Google Summer of Code (GSoC) nine times since 2006:
## Outreachy
-CC participated in Outreachy three times since 2019:
+CC participated in Outreachy four times since 2019:
- *[All Outreachy Open Source Blog posts](/blog/categories/outreachy/)*
-- [Outreachy December 2021 - March
+- [Outreachy **December 2022** - March
+ 2023](https://www.outreachy.org/outreachy-december-2022-internship-round/)
+ - [Open Source Blog posts](/blog/categories/outreachy-2022/)
+- [Outreachy **December 2021** - March
2022](https://www.outreachy.org/outreachy-december-2021-internship-round/)
- [Open Source Blog posts](/blog/categories/outreachy-2021/)
-- [Outreachy May 2020 - August
+- [Outreachy **May 2020** - August
2020](https://www.outreachy.org/outreachy-may-2020-internship-round/)
- [Open Source Blog posts](/blog/categories/outreachy-2020/)
- - [Welcome Our Interns from Google Summer of Code and
- Outreachy!](https://creativecommons.org/2020/05/11/welcome-interns-google-summer-of-code-and-outreachy/)
- - [Say Hello to Our New CC Open Source
- Website!](https://creativecommons.org/2020/11/02/cc-open-source-website/)
- - [Explore the New CC Legal Database
- Site!](https://creativecommons.org/2020/12/03/explore-the-new-cc-legal-database-site/)
-- [Outreachy December 2019 - March
+- [Outreachy **December 2019** - March
2020](https://www.outreachy.org/december-2019-to-march-2020-internship-round/)
- [Open Source Blog posts](/blog/categories/outreachy-2019-20/)
- - [Meet Our 2020 Interns From
- Outreachy](https://creativecommons.org/2019/12/10/2020-outreachy-interns/)
diff --git a/content/programs/lead-guide/contents.lr b/content/programs/lead-guide/contents.lr
index 6554f7362..8677111f3 100644
--- a/content/programs/lead-guide/contents.lr
+++ b/content/programs/lead-guide/contents.lr
@@ -5,10 +5,11 @@ _template: page-with-toc.html
title: Open Source Work Programs: Project Lead Guide
---
description:
-CC participates in open source work programs such as GSoC and Outreachy. Both
-CC staff and community members are welcome to lead projects. Details about
-specific programs and rounds are listed in the [Overview page](/programs); this
-page serves as a general project lead guide.
+Creative Commons (CC) participates in open source work programs such as Google
+Summer of Code (GSoC) and Outreachy. Both CC team members and community members
+are welcome to lead projects. Details about specific programs and rounds are
+listed in the [Overview page](/programs); this page serves as a general project
+lead guide.
---
body:
diff --git a/content/programs/project-ideas-collection/automating-quantifying-the-commons/contents.lr b/content/programs/project-ideas-collection/automating-quantifying-the-commons/contents.lr
deleted file mode 100644
index 0ab012c28..000000000
--- a/content/programs/project-ideas-collection/automating-quantifying-the-commons/contents.lr
+++ /dev/null
@@ -1,46 +0,0 @@
-_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 repository (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
diff --git a/content/programs/project-ideas-collection/cc-legal-tools-machine-layer/contents.lr b/content/programs/project-ideas-collection/cc-legal-tools-machine-layer/contents.lr
deleted file mode 100644
index 42bf0346d..000000000
--- a/content/programs/project-ideas-collection/cc-legal-tools-machine-layer/contents.lr
+++ /dev/null
@@ -1,74 +0,0 @@
-_model: project-idea
----
-_hidden: yes
----
-title: CC Legal Tools: Machine Readable Layer
----
-problem:
-The CC Legal tools consist of three parts, the legal code, the deed (simple
-language description), and the machine readable. The machine readable layer has
-received the least recent development. It is out of date and there are
-unresolved issues.
----
-expected_outcome:
-Extend the CC Legal Tools App to generate deterministic RDF XML files for all
-of the legal tools.
-
-Stretch goal: Extend the CC Legal Tools App to generate deterministic plain
-text versions of the 4.0 licenses and the CC0 public domain dedication.
----
-contributor_tasks:
-The contributor will need to extend the CC Legal Tools App to generate RDF XML
-files. The generated RDF XML files must be deterministic and well organized and
-based on current RDF specifications. Application updates must include test
-coverage.
-
-Stretch goal: Extend the CC Legal Tools App to generate plain text versions.
-The generated plain text versions must be deterministic and match the
-formatting of the manual versions (except where improvements are desired).
-Application updates must include test coverage. Additional stretch goals
-include adding markdown format generation and interfacing/collaborating with
-SPDX.
----
-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-legal-tools-app](https://github.com/creativecommons/cc-legal-tools-app/):
- License and public domain dedication management application for Creative
- Commons
-- [creativecommons/cc-legal-tools-data](https://github.com/creativecommons/cc-legal-tools-data):
- License and public domain dedication data for Creative Commons
-- **ccREL (RDF/XML)**
-- [Describing Copyright in RDF - Creative Commons Rights Expression
- Language](https://creativecommons.org/ns/)
-- [CC REL - Creative Commons](https://wiki.creativecommons.org/wiki/CC_REL) (CC
- Public Wiki)
-- [creativecommons/ccrel](https://github.com/creativecommons/ccrel)
-- [ccREL: The Creative Commons Rights Expression
- Language](https://opensource.creativecommons.org/ccrel/)
-- [creativecommons/ccrel-guide](https://github.com/creativecommons/ccrel-guide)
-- [CC REL by Example](https://opensource.creativecommons.org/ccrel-guide/)
-- **Plain text format**
-- [Plaintext versions of Creative Commons 4.0 licenses - Creative
- Commons](https://creativecommons.org/2014/01/07/plaintext-versions-of-creative-commons-4-0-licenses/)
-- [Plaintext versions of Creative Commons licenses and CC0 - Creative
- Commons](https://creativecommons.org/2011/04/15/plaintext-versions-of-creative-commons-licenses-and-cc0/)
----
-skills_recommended:
-- Django
-- Git
-- Python
-- RDF
-- XML
----
-lead:
-- Timid Robot
----
-difficulty: High
----
-size: Large (~350 hours)
----
-filter_value: difficulty-high skill-django skill-git skill-python skill-rdf skill-xml
diff --git a/content/programs/project-ideas-collection/conslidate-implement-vocabulary-design-system-across-websites/contents.lr b/content/programs/project-ideas-collection/conslidate-implement-vocabulary-design-system-across-websites/contents.lr
new file mode 100644
index 000000000..53a6cf93d
--- /dev/null
+++ b/content/programs/project-ideas-collection/conslidate-implement-vocabulary-design-system-across-websites/contents.lr
@@ -0,0 +1,70 @@
+_model: project-idea
+---
+_hidden: yes
+---
+title: Consolidate and implement Vocabulary design system across ancillary
+websites
+---
+problem:
+The new design system, Vocabulary, has been implemented to varying degrees
+across several Creative Commons web entities, versioning and features do not
+have full parity and each implementation merits a further investigation,
+course correction, expansion, and cleanup.
+---
+expected_outcome:
+Ancillary CC websites implement the current versions and features of the latest
+Vocabulary codebase in a consistent and stable manner. Necessary new features
+are identified, built, and implemented upstream into Vocabulary itself where
+relevant, localized features are implemented into the codebase of each project
+where necessary.
+---
+contributor_tasks:
+Identify and catalog features present on current sites, but missing within
+Vocabulary. Document migration paths between conflicting or missing UX patterns.
+Rewrite and/or refactor the codebase of each ancillary site, maintaining its
+original function, while implementing the Vocabulary design system; migrating
+implementations from NPM dependency chains to more simplistic static code, where
+needed; building out new features as necessary locally or within the Vocabulary
+codebase itself. Using simple, standards-compliant, and accessible HTML, CSS,
+and minimal JavaScript.
+---
+application_tips:
+- Engage with the ancillary sites and Vocabulary repositories (issues, pull requests)
+- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
+- [Applicant Guide](/programs/applicant-guide/)
+---
+resources:
+- [Vocabulary Docs](https://vocabulary-docs.netlify.app/)
+- [Vocabulary Repository](https://github.com/creativecommons/vocabulary)
+- [search.creativecommons.org](http://search.creativecommons.org)
+- [Search Portal Repository](https://github.com/creativecommons/search)
+- [resources.creativecommons.org](http://resources.creativecommons.org)
+- [Resources Archive Repository](https://github.com/creativecommons/cc-resource-archive)
+- [opensource.creativecommons.org](http://opensource.creativecommons.org)
+- [Open Source Repository](https://github.com/creativecommons/ccos-website-source)
+- [legaldb.creativecommons.org](http://legaldb.creativecommons.org)
+- [LegalDB Repository](https://github.com/creativecommons/legaldb)
+- [MDN Web Docs: Semantics](https://developer.mozilla.org/en-US/docs/Glossary/Semantics)
+- [MDN Web Docs: HTML](https://developer.mozilla.org/en-US/docs/Web/HTML)
+- [MDN Web Docs: JavaScript](https://developer.mozilla.org/en-US/docs/Web/JavaScript)
+- [Django Docs](https://docs.djangoproject.com/en/5.1/)
+- [Lektor Docs](https://www.getlektor.com/docs/)
+
+---
+skills_recommended:
+- CSS
+- Django
+- Git
+- HTML
+- JavaScript
+- Lektor
+
+---
+lead:
+- Sara
+---
+difficulty: Medium
+---
+size: Large (~350 hours)
+---
+filter_value: difficulty-medium skill-django skill-git skill-javascript skill-html skill-css skill-lektor
diff --git a/content/programs/project-ideas-collection/modernize-cc-resource-archive/contents.lr b/content/programs/project-ideas-collection/modernize-cc-resource-archive/contents.lr
deleted file mode 100644
index 6c54c45ba..000000000
--- a/content/programs/project-ideas-collection/modernize-cc-resource-archive/contents.lr
+++ /dev/null
@@ -1,50 +0,0 @@
-_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 repository (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
diff --git a/content/programs/project-ideas-collection/upgrade-and-refactor-cc-chooser/contents.lr b/content/programs/project-ideas-collection/upgrade-and-refactor-cc-chooser/contents.lr
deleted file mode 100644
index c37c27002..000000000
--- a/content/programs/project-ideas-collection/upgrade-and-refactor-cc-chooser/contents.lr
+++ /dev/null
@@ -1,58 +0,0 @@
-_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 repository (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
diff --git a/databags/community_team_members.json b/databags/community_team_members.json
index 665937e05..0b01e90bd 100644
--- a/databags/community_team_members.json
+++ b/databags/community_team_members.json
@@ -124,32 +124,6 @@
"name": "Vocabulary",
"repos": "vocabulary"
},
- {
- "members": [
- {
- "github": "hugosolar",
- "name": "Hugo Solar",
- "role": "Project Maintainer"
- },
- {
- "github": "kgodey",
- "name": "Kriti Godey",
- "role": "Project Maintainer"
- },
- {
- "github": "ahmadbilaldev",
- "name": "Ahmad Bilal",
- "role": "Project Core Committer"
- },
- {
- "github": "Cronus1007",
- "name": "Ritish Thareja",
- "role": "Project Core Committer"
- }
- ],
- "name": "WordPress Plugin",
- "repos": "wp-plugin-creativecommons"
- },
{
"members": [
{
@@ -225,7 +199,7 @@
}
],
"name": "CC Open Source",
- "repos": "creativecommons.github.io-source"
+ "repos": "ccos-website-source"
},
{
"members": [
@@ -239,6 +213,11 @@
"name": "Kriti Godey",
"role": "Project Maintainer"
},
+ {
+ "github": "zackkrida",
+ "name": "Zack Krida",
+ "role": "Project Maintainer"
+ },
{
"github": "JackieBinya",
"name": "Jacqueline Binya",
@@ -291,22 +270,6 @@
"name": "License Buttons",
"repos": "licensebuttons"
},
- {
- "members": [
- {
- "github": "bhumijgupta",
- "name": "Bhumij Gupta",
- "role": "Project Maintainer"
- },
- {
- "github": "kgodey",
- "name": "Kriti Godey",
- "role": "Project Maintainer"
- }
- ],
- "name": "Link Checker",
- "repos": "cc-link-checker"
- },
{
"members": [
{
diff --git a/databags/repos.json b/databags/repos.json
index 10a1e8955..cc9d21bad 100644
--- a/databags/repos.json
+++ b/databags/repos.json
@@ -75,30 +75,6 @@
"url": "https://github.com/creativecommons/cc-assets",
"website": ""
},
- {
- "created": "2021-11-26T11:23:54+00:00",
- "description": "Vue.js components for consistent navigation and branding across Creative Commons web properties",
- "engineering_project": true,
- "english_name": "CC Global Components",
- "featured": false,
- "id": 432153424,
- "language": "Vue",
- "license": {
- "name": "MIT License",
- "url": "https://github.com/creativecommons/cc-global-components/blob/main/LICENSE"
- },
- "name": "cc-global-components",
- "slack": "",
- "technologies": [
- "HTML",
- "CSS",
- "JS",
- "Bulma",
- "Vue"
- ],
- "url": "https://github.com/creativecommons/cc-global-components",
- "website": null
- },
{
"created": "2020-06-03T18:51:38+00:00",
"description": "Legal tool (licenses, public domain dedication, etc.) management application for Creative Commons",
@@ -118,7 +94,7 @@
"Python"
],
"url": "https://github.com/creativecommons/cc-legal-tools-app",
- "website": ""
+ "website": "https://creativecommons.org/licenses/"
},
{
"created": "2020-09-08T19:18:51+00:00",
@@ -163,26 +139,6 @@
"url": "https://github.com/creativecommons/cc-license-chooser",
"website": ""
},
- {
- "created": "2019-06-12T18:15:54+00:00",
- "description": "Automated link checker for legalcode and license URLs",
- "engineering_project": true,
- "english_name": "Creative Commons Link Checker",
- "featured": false,
- "id": 191622826,
- "language": "Python",
- "license": {
- "name": "MIT License",
- "url": "https://github.com/creativecommons/cc-link-checker/blob/main/LICENSE"
- },
- "name": "cc-link-checker",
- "slack": "cc-dev-linkchecker",
- "technologies": [
- "Python"
- ],
- "url": "https://github.com/creativecommons/cc-link-checker",
- "website": ""
- },
{
"created": "2014-01-08T18:49:45+00:00",
"description": "Collection of resources on Creative Commons (CC) tools and other open topics",
@@ -199,38 +155,6 @@
"url": "https://github.com/creativecommons/cc-resource-archive",
"website": "https://resources.creativecommons.org/"
},
- {
- "created": "2015-07-15T18:24:37+00:00",
- "description": "WordPress theme used on creativecommons.org",
- "engineering_project": true,
- "featured": false,
- "id": 39153629,
- "language": "Hack",
- "license": {
- "name": "GNU General Public License v2.0",
- "url": "https://github.com/creativecommons/cc-wp-theme/blob/main/LICENSE"
- },
- "name": "cc-wp-theme",
- "slack": "",
- "url": "https://github.com/creativecommons/cc-wp-theme",
- "website": ""
- },
- {
- "created": "2013-12-02T21:01:41+00:00",
- "description": "Legacy API to integrate the Creative Commons licensing engine into third party applications",
- "engineering_project": true,
- "featured": false,
- "id": 14874742,
- "language": "Python",
- "license": {
- "name": "MIT License",
- "url": "https://github.com/creativecommons/cc.api/blob/main/LICENSE"
- },
- "name": "cc.api",
- "slack": "",
- "url": "https://github.com/creativecommons/cc.api",
- "website": "https://api.creativecommons.org/docs/"
- },
{
"created": "2014-10-06T22:07:52+00:00",
"description": "RubyCAS customizations for CCID (Creative Commons ID)",
@@ -283,6 +207,22 @@
"url": "https://github.com/creativecommons/ccos-scripts",
"website": ""
},
+ {
+ "created": "2019-01-27T02:29:18+00:00",
+ "description": "Source files for CC Open Source website",
+ "engineering_project": true,
+ "featured": false,
+ "id": 167761414,
+ "language": "HTML",
+ "license": {
+ "name": "MIT License",
+ "url": "https://github.com/creativecommons/ccos-website-source/blob/main/LICENSE"
+ },
+ "name": "ccos-website-source",
+ "slack": "",
+ "url": "https://github.com/creativecommons/ccos-website-source",
+ "website": "https://opensource.creativecommons.org/"
+ },
{
"created": "2013-10-24T00:12:36+00:00",
"description": "A guide to using the Creative Commons Rights Expression Language (CC REL)",
@@ -361,6 +301,20 @@
"url": "https://github.com/creativecommons/commoners",
"website": "https://network.creativecommons.org/"
},
+ {
+ "created": "2024-06-14T18:39:49+00:00",
+ "description": "This plugin allows you to add a button to your WordPress site's posts which will display terms and licensing for Creative Commons reposting, as well as the title and content of the post for easy sharing. This is useful for sites that want to easily and clearly share their content with others.",
+ "id": 815277416,
+ "language": "PHP",
+ "license": {
+ "name": "GNU General Public License v3.0",
+ "url": "https://github.com/creativecommons/Creative-Commons-Post-Republisher/blob/main/LICENSE"
+ },
+ "name": "Creative-Commons-Post-Republisher",
+ "slack": "",
+ "url": "https://github.com/creativecommons/Creative-Commons-Post-Republisher",
+ "website": ""
+ },
{
"created": "2019-12-06T19:44:21+00:00",
"description": "Base WordPress theme for Creative Commons websites.",
@@ -405,22 +359,6 @@
"url": "https://github.com/creativecommons/creativecommons-certificate",
"website": ""
},
- {
- "created": "2019-01-27T02:29:18+00:00",
- "description": "Source files for CC Open Source website",
- "engineering_project": true,
- "featured": false,
- "id": 167761414,
- "language": "HTML",
- "license": {
- "name": "MIT License",
- "url": "https://github.com/creativecommons/creativecommons.github.io-source/blob/main/LICENSE"
- },
- "name": "creativecommons.github.io-source",
- "slack": "",
- "url": "https://github.com/creativecommons/creativecommons.github.io-source",
- "website": "https://opensource.creativecommons.org/"
- },
{
"created": "2013-10-31T00:19:22+00:00",
"description": "Legacy legal code translations and general support issues",
@@ -535,7 +473,7 @@
"english_name": "CC Legal Database",
"featured": false,
"id": 133715391,
- "language": "HTML",
+ "language": "Python",
"license": {
"name": "MIT License",
"url": "https://github.com/creativecommons/legaldb/blob/main/LICENSE"
@@ -548,7 +486,7 @@
"PostgreSQL"
],
"url": "https://github.com/creativecommons/legaldb",
- "website": "https://legaldb.creativecommons.org/"
+ "website": "https://LegalDB.CreativeCommons.org/"
},
{
"created": "2013-10-28T02:42:48+00:00",
@@ -639,35 +577,9 @@
"url": "https://github.com/creativecommons/open4us.org",
"website": "http://open4us.org/"
},
- {
- "created": "2021-07-06T17:25:01+00:00",
- "description": "Project to manage technical implementation of creativecommons.org (primary website)",
- "engineering_project": true,
- "english_name": "CreativeCommons.org website development project",
- "featured": false,
- "id": 383548251,
- "language": "Shell",
- "license": {
- "name": "MIT License",
- "url": "https://github.com/creativecommons/project_creativecommons.org/blob/main/LICENSE"
- },
- "name": "project_creativecommons.org",
- "slack": "cc-dev-wordpress",
- "technologies": [
- "PHP",
- "WordPress",
- "JavaScript",
- "React",
- "Django",
- "Docker",
- "Docker Compose"
- ],
- "url": "https://github.com/creativecommons/project_creativecommons.org",
- "website": "https://creativecommons.org/"
- },
{
"created": "2022-09-07T17:02:39+00:00",
- "description": "Quantifying the Commons",
+ "description": "quantify the size and diversity of the commons--the collection of works that are openly licensed or in the public domain",
"engineering_project": true,
"english_name": "Quantifying the Commons",
"featured": true,
@@ -701,22 +613,6 @@
"url": "https://github.com/creativecommons/reversionary-rights",
"website": "https://rights-back-beta.creativecommons.org/"
},
- {
- "created": "2015-07-23T21:30:47+00:00",
- "description": "Rails plugin for the RubyCAS-Client",
- "engineering_project": true,
- "featured": false,
- "id": 39594110,
- "language": "Ruby",
- "license": {
- "name": "MIT License",
- "url": "https://github.com/creativecommons/rubycas-client-rails/blob/master/MIT-LICENSE"
- },
- "name": "rubycas-client-rails",
- "slack": "",
- "url": "https://github.com/creativecommons/rubycas-client-rails",
- "website": ""
- },
{
"created": "2016-07-29T23:14:42+00:00",
"description": "The scholars addenda system.",
@@ -740,7 +636,7 @@
"english_name": "CC Search Portal",
"featured": false,
"id": 13818557,
- "language": "HTML",
+ "language": "CSS",
"license": {
"name": "MIT License",
"url": "https://github.com/creativecommons/search/blob/main/LICENSE"
@@ -877,99 +773,26 @@
"website": "https://thepowerofopen.org/"
},
{
- "created": "2019-11-25T17:29:13+00:00",
- "description": "A cohesive design system & Vue component library to unify the web-facing Creative Commons",
+ "created": "2024-04-24T19:10:38+00:00",
+ "description": "A cohesive system of design for Creative Commons",
"engineering_project": true,
- "english_name": "CC Vocabulary",
+ "english_name": "Vocabulary Design System",
"featured": false,
- "id": 224004769,
- "language": "SCSS",
+ "id": 791465373,
+ "language": "HTML",
"license": {
- "name": "MIT License",
- "url": "https://github.com/creativecommons/vocabulary/blob/main/LICENSE"
+ "name": "Creative Commons Zero v1.0 Universal",
+ "url": "https://github.com/creativecommons/vocabulary/blob/main/COPYING"
},
"name": "vocabulary",
- "slack": "cc-dev-vocabulary",
+ "slack": "",
"technologies": [
- "Sass",
- "JavaScript",
- "Webpack",
- "Storybook",
- "Bulma",
- "Fonts"
+ "HTML",
+ "CSS",
+ "Javascript"
],
"url": "https://github.com/creativecommons/vocabulary",
- "website": "https://cc-vocabulary.netlify.app"
- },
- {
- "created": "2022-01-10T10:29:18+00:00",
- "description": "A collection of Vue components used in the web facing Creative Commons.",
- "engineering_project": true,
- "english_name": "CC Vocabulary components",
- "featured": false,
- "id": 446377158,
- "language": "Vue",
- "license": {
- "name": "MIT License",
- "url": "https://github.com/creativecommons/vocabulary-components/blob/main/LICENSE"
- },
- "name": "vocabulary-components",
- "slack": "cc-dev-vocabulary",
- "technologies": [
- "Sass",
- "JavaScript",
- "Webpack",
- "Vue.js"
- ],
- "url": "https://github.com/creativecommons/vocabulary-components",
- "website": ""
- },
- {
- "created": "2022-01-10T11:07:04+00:00",
- "description": "Typefaces that lend personality to the web facing Creative Commons",
- "engineering_project": true,
- "english_name": "CC Vocabulary fonts",
- "featured": false,
- "id": 446389251,
- "language": "JavaScript",
- "license": {
- "name": "MIT License",
- "url": "https://github.com/creativecommons/vocabulary-fonts/blob/main/LICENSE"
- },
- "name": "vocabulary-fonts",
- "slack": "cc-dev-vocabulary",
- "technologies": [
- "Sass",
- "JavaScript",
- "Webpack",
- "Storybook"
- ],
- "url": "https://github.com/creativecommons/vocabulary-fonts",
- "website": ""
- },
- {
- "created": "2022-01-10T11:06:45+00:00",
- "description": "A cohesive design system to unite the web facing Creative Commons",
- "engineering_project": true,
- "english_name": "CC Vocabulary styles",
- "featured": false,
- "id": 446389149,
- "language": "SCSS",
- "license": {
- "name": "MIT License",
- "url": "https://github.com/creativecommons/vocabulary-styles/blob/main/LICENSE"
- },
- "name": "vocabulary-styles",
- "slack": "cc-dev-vocabulary",
- "technologies": [
- "Sass",
- "JavaScript",
- "Webpack",
- "Storybook",
- "Bulma"
- ],
- "url": "https://github.com/creativecommons/vocabulary-styles",
- "website": ""
+ "website": "https://vocabulary-docs.netlify.app"
},
{
"created": "2023-04-21T19:58:28+00:00",
@@ -1017,29 +840,6 @@
"url": "https://github.com/creativecommons/wp-plugin-cc-global-network",
"website": ""
},
- {
- "created": "2014-07-28T15:18:18+00:00",
- "description": "Official Creative Commons plugin for licensing your content. With Creative Commons licenses, keep your copyright AND share your creativity.",
- "engineering_project": true,
- "english_name": "CC WordPress Plugin",
- "featured": true,
- "id": 22347352,
- "language": "PHP",
- "license": {
- "name": "GNU General Public License v2.0",
- "url": "https://github.com/creativecommons/wp-plugin-creativecommons/blob/main/license.txt"
- },
- "name": "wp-plugin-creativecommons",
- "slack": "cc-dev-wordpress",
- "technologies": [
- "PHP",
- "CSS",
- "JS",
- "WordPress"
- ],
- "url": "https://github.com/creativecommons/wp-plugin-creativecommons",
- "website": "https://wordpress.org/plugins/creative-commons/"
- },
{
"created": "2020-09-17T19:19:54+00:00",
"description": "This WordPress plugin provides custom functionality for the creativecommons.org website.",
diff --git a/models/blog-post.ini b/models/blog-post.ini
index a5e8cefb4..8376c1ced 100644
--- a/models/blog-post.ini
+++ b/models/blog-post.ini
@@ -29,3 +29,8 @@ type = strings
[fields.body]
label = Body
type = markdown
+
+[fields.excerpt]
+label = Excerpt
+type = markdown
+width = 1/2
diff --git a/themes/vocabulary_theme/templates/blocks/featured-projects.html b/themes/vocabulary_theme/templates/blocks/featured-projects.html
index 02f61c172..abc317c93 100644
--- a/themes/vocabulary_theme/templates/blocks/featured-projects.html
+++ b/themes/vocabulary_theme/templates/blocks/featured-projects.html
@@ -15,7 +15,7 @@