Merge pull request creativecommons#814 from creativecommons/define-cc-acronym

TimidRobot · web-flow · commit 1241ab68bda3 · 2024-10-03T11:32:47.000-07:00
Define Creative Commons (CC) acronym at top of page or on first use
diff --git 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 <i class="icon rss-square body-normal"></i>](/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 <i class="icon rss-square body-normal"></i>](/blog/feed.xml).
diff --git 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 <a href=" https://wiki.creativecommons.org/wiki/Slack/Code_of_Conduct">can be found here</a>.
+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 <a href=" https://wiki.creativecommons.org/wiki/Slack/Code_of_Conduct">can be found here</a>.
 ---
 body:
 
diff --git 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
@@ -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 <a href="/community/community-team/">Community Team</a>.
+description: This page serves as a guide for project-based roles on Creative Commons' <a href="/community/community-team/">Community Team</a>.
 ---
 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
@@ -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
-<a href="/blog">CC Open Source Blog</a> or via <a
-href="https://twitter.com/cc_opensource">Twitter</a>.
+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 <a href="/blog">CC
+Open Source Blog</a>.
 ---
 body:
 
diff --git 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 <a href="/blog">our technical blog</a>.
+description: We invite members of the Creative Commons (CC) community to write guest posts on <a href="/blog">our technical blog</a>.
 ---
 body:
 
diff --git a/content/contents.lr b/content/contents.lr
@@ -7,7 +7,7 @@ block_content:
 #### hero ####
 title:
 
-We have been building <span class="has-text-forest-green">free software</span> at <span class="has-text-gold">Creative Commons</span> for over a decade.
+We have been building <span class="has-text-forest-green">free software</span> at <span class="has-text-gold">Creative Commons (CC)</span> 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
@@ -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
@@ -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
@@ -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
@@ -227,7 +227,7 @@ recognized by GitHub. The special ones don't have emojis either._
 - <span class="gh-label friendliness">help wanted</span>
   - **Description:** Open to participation from the community
 - <span class="gh-label friendliness">🔒 staff only</span>
-  - **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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -7,7 +7,7 @@
     <div class="header">
       <div class="container">
         <h1>{{ this.title }}</h1>
-        <p class="description column is-9 is-paddingless">This is a list of all CC Community Team members, and their roles and privileges. For more information about CC Community Team, please see <a href="/community/community-team/">the Community Team Page</a>.</p>
+        <p class="description column is-9 is-paddingless">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 <a href="/community/community-team/">the Community Team Page</a>.</p>
       </div>
     </div>
     <div class="container padding-horizontal-big padding-vertical-xl">
diff --git a/themes/vocabulary_theme/templates/project-ideas.html b/themes/vocabulary_theme/templates/project-ideas.html
@@ -7,7 +7,7 @@
     <div class="header">
       <div class="container">
         <h1>Open Source Work Programs: Project Ideas</h1>
-        <p class="description">This is the project idea list for the <span class="has-color-forest-green">current round of open source collaborations at Creative Commons.</span></p>
+        <p class="description">This is the project idea list for the <span class="has-color-forest-green">current round of open source collaborations at Creative Commons (CC).</span></p>
         {% set ideas = site.query('/programs/project-ideas-collection').include_undiscoverable(true) %}
         <div class="filter-labels" id="project-list">
           <button type="button" class="button tag btn-dark filter-btn" data-filter="all">
diff --git a/themes/vocabulary_theme/templates/project_list.html b/themes/vocabulary_theme/templates/project_list.html
@@ -7,7 +7,7 @@
     <div class="header">
       <div class="container">
         <h1>Project List</h1>
-        <p class="description">This is a list of all active open source software projects that Creative Commons maintains.</p>
+        <p class="description">This is a list of all active open source software projects that Creative Commons (CC) maintains.</p>
       </div>
     </div>
     <div class="body container">
