diff --git a/content/blog/entries/contents.lr b/content/blog/entries/contents.lr index 7af89da91..c820bd531 100644 --- a/content/blog/entries/contents.lr +++ b/content/blog/entries/contents.lr @@ -3,4 +3,4 @@ _model: blog title: CC Open Source Blog --- description: -Welcome to CC's new technical blog! The CC technical team writes about what we're working on, updates about CC's software projects, engineering related programs and events that CC is participating in, and more. We also feature posts from community members working on CC-related projects. You can subscribe to our [RSS feed ](/blog/feed.xml). +Welcome to Creative Commons (CC) open source and technical blog! The CC Technical team writes about what we're working on, updates about CC's software projects, engineering related programs and events that CC is participating in, and more. We also feature posts from community members working on CC-related projects. You can subscribe to our [RSS feed ](/blog/feed.xml). diff --git a/content/community/code-of-conduct/contents.lr b/content/community/code-of-conduct/contents.lr index ad45095ae..1a9a5b05d 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: diff --git a/content/community/code-of-conduct/enforcement/contents.lr b/content/community/code-of-conduct/enforcement/contents.lr index 159b103a3..3871b041a 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] 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 caa84f44b..7265e5d66 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: diff --git a/content/community/write-a-blog-post/contents.lr b/content/community/write-a-blog-post/contents.lr index 36fd6221e..d5827c94f 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: diff --git a/content/contents.lr b/content/contents.lr index 494dbc99a..7c6338b88 100644 --- a/content/contents.lr +++ b/content/contents.lr @@ -7,7 +7,7 @@ block_content: #### hero #### title: -We have been building free software at Creative Commons for over a decade. +We have been building free software at Creative Commons (CC) for over a decade. ---- links: diff --git a/content/contributing-code/github-repo-guidelines/contents.lr b/content/contributing-code/github-repo-guidelines/contents.lr index e56176ca8..ad53b6a52 100644 --- a/content/contributing-code/github-repo-guidelines/contents.lr +++ b/content/contributing-code/github-repo-guidelines/contents.lr @@ -108,8 +108,8 @@ 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 @@ -118,7 +118,7 @@ the contribution guidelines for that project. ## 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. 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 b52612c9a..53d6e355e 100644 --- a/content/contributing-code/repo-labels/contents.lr +++ b/content/contributing-code/repo-labels/contents.lr @@ -227,7 +227,7 @@ 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 diff --git a/content/contributing-code/translation-guide/contents.lr b/content/contributing-code/translation-guide/contents.lr index 0d834a9e8..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. 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/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/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/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/themes/vocabulary_theme/templates/community_team_list.html b/themes/vocabulary_theme/templates/community_team_list.html index 90743504b..b1d263c7a 100644 --- a/themes/vocabulary_theme/templates/community_team_list.html +++ b/themes/vocabulary_theme/templates/community_team_list.html @@ -7,7 +7,7 @@

{{ this.title }}

-

This is a list of all CC Community Team members, and their roles and privileges. For more information about CC Community Team, please see the Community Team Page.

+

This is a list of all Creative Commons (CC) Community Team members, and their roles and privileges. For more information about CC Community Team, please see the Community Team Page.

diff --git a/themes/vocabulary_theme/templates/project-ideas.html b/themes/vocabulary_theme/templates/project-ideas.html index fe5cd90bc..6eb0be72c 100644 --- a/themes/vocabulary_theme/templates/project-ideas.html +++ b/themes/vocabulary_theme/templates/project-ideas.html @@ -7,7 +7,7 @@

Open Source Work Programs: Project Ideas

-

This is the project idea list for the current round of open source collaborations at Creative Commons.

+

This is the project idea list for the current round of open source collaborations at Creative Commons (CC).

{% set ideas = site.query('/programs/project-ideas-collection').include_undiscoverable(true) %}