diff --git a/README.md b/README.md
index d528e14d8..d30553082 100644
--- a/README.md
+++ b/README.md
@@ -1,12 +1,13 @@
-# creativecommons.github.io-source
+# ccos-website-source
Source for `creativecommons.github.io`
## Overview
-> **:warning: DO *NOT* MAKE CHANGES TO THE
-> [creativecommons/creativecommons.github.io][ccghiorepo] REPO DIRECTLY**.
+> **:warning: DON'T MAKE CHANGES TO THE
+> [creativecommons/creativecommons.github.io][ccghiorepo] REPOSIOTRY,
+> DIRECTLY**.
[ccghiorepo]: https://github.com/creativecommons/creativecommons.github.io
@@ -41,10 +42,10 @@ See [`CONTRIBUTING.md`][org-contrib].
[org-contrib]: https://github.com/creativecommons/.github/blob/main/CONTRIBUTING.md
- See [Contributors to
- creativecommons/creativecommons.github.io-source][contributors] for a
+ creativecommons/ccos-website-source][contributors] for a
list of authors and their contributions to this project :blush:
-[contributors]: https://github.com/creativecommons/creativecommons.github.io-source/graphs/contributors "Contributors to creativecommons/creativecommons.github.io-source"
+[contributors]: https://github.com/creativecommons/ccos-website-source/graphs/contributors "Contributors to creativecommons/ccos-website-source"
## Installation
diff --git a/assets/CODE_OF_CONDUCT.md b/assets/CODE_OF_CONDUCT.md
index 30dc65364..36db7ff2c 100644
--- a/assets/CODE_OF_CONDUCT.md
+++ b/assets/CODE_OF_CONDUCT.md
@@ -10,4 +10,4 @@ For a history of updates, see the [page history here][updates].
[code_of_conduct]: https://opensource.creativecommons.org/community/code-of-conduct/
[reporting_guide]: https://opensource.creativecommons.org/community/code-of-conduct/enforcement/
-[updates]: https://github.com/creativecommons/creativecommons.github.io-source/commits/main/content/community/code-of-conduct/contents.lr
+[updates]: https://github.com/creativecommons/ccos-website-source/commits/main/content/community/code-of-conduct/contents.lr
diff --git a/assets/README.md b/assets/README.md
index c1e887dfa..4ff052c5d 100644
--- a/assets/README.md
+++ b/assets/README.md
@@ -4,7 +4,7 @@
These are the static files for [Creative Commons Open Source][ccos]. The files
are automatically built via CI from the source files in the
-[creativecommons.github.io-source][src] repository.
+[ccos-website-source][src] repository.
[ccos]: https://opensource.creativecommons.org/
-[src]: https://github.com/creativecommons/creativecommons.github.io-source
+[src]: https://github.com/creativecommons/ccos-website-source
diff --git a/content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr b/content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr
index 27cdfc287..06cb7c773 100644
--- a/content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr
+++ b/content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr
@@ -51,7 +51,7 @@ With a smaller engineering team, we will need to support fewer projects. Please
We will continue to actively develop the following projects:
- [CC Search Browser Extension](https://github.com/creativecommons/ccsearch-browser-extension) (maintainer: Mayank Nader)
-- [CC Open Source website](https://github.com/creativecommons/creativecommons.github.io-source) (maintainers: Zack Krida & Timid Robot Zehta)
+- [CC Open Source website](https://github.com/creativecommons/ccos-website-source) (maintainers: Zack Krida & Timid Robot Zehta)
- [CC WordPress base](https://github.com/creativecommons/creativecommons-base) & child themes (new maintainer: Zack Krida)
- [CC Legal Database](https://github.com/creativecommons/legaldb) (maintainer: Timid Robot Zehta)
- [CC Chooser](https://github.com/creativecommons/chooser) (maintainer: Zack Krida)
diff --git a/content/blog/entries/cc-vocabulary-docs-updates-closing/contents.lr b/content/blog/entries/cc-vocabulary-docs-updates-closing/contents.lr
index e57f74542..670b53a6b 100644
--- a/content/blog/entries/cc-vocabulary-docs-updates-closing/contents.lr
+++ b/content/blog/entries/cc-vocabulary-docs-updates-closing/contents.lr
@@ -265,25 +265,25 @@ Here's the link to the [documentation site](https://cc-vocabulary.netlify.app).
| https://github.com/cc-archive/vocabulary-legacy/issues/736 |
-| @creativecommons/creativecommons.github.io-source |
+@creativecommons/ccos-website-source |
Introductory First Blog Post |
-https://github.com/creativecommons/creativecommons.github.io-source/pull/530
/blog/entries/cc-vocabulary-docs-intro/ |
+https://github.com/creativecommons/ccos-website-source/pull/530
/blog/entries/cc-vocabulary-docs-intro/ |
| Vocabulary Site Update v1 |
-https://github.com/creativecommons/creativecommons.github.io-source/pull/549
/blog/entries/cc-vocabulary-docs-updates-1/ |
+https://github.com/creativecommons/ccos-website-source/pull/549
/blog/entries/cc-vocabulary-docs-updates-1/ |
| Vocabulary Mid Internship Update v2 |
-https://github.com/creativecommons/creativecommons.github.io-source/pull/555
/blog/entries/cc-vocabulary-docs-updates-2/ |
+https://github.com/creativecommons/ccos-website-source/pull/555
/blog/entries/cc-vocabulary-docs-updates-2/ |
| Vocabulary Site Update v3 |
-https://github.com/creativecommons/creativecommons.github.io-source/pull/561
/blog/entries/cc-vocabulary-docs-updates-3/ |
+https://github.com/creativecommons/ccos-website-source/pull/561
/blog/entries/cc-vocabulary-docs-updates-3/ |
| Vocabulary Site Final Update |
-https://github.com/creativecommons/creativecommons.github.io-source/pull/564
/blog/entries/cc-vocabulary-docs-updates-closing/ |
+https://github.com/creativecommons/ccos-website-source/pull/564
/blog/entries/cc-vocabulary-docs-updates-closing/ |
| @cc-archive/cccatalog-api |
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
index 0fbd6f473..ef103e790 100644
--- a/content/blog/entries/outreachy-midpoint-progess-with-creative-commons/contents.lr
+++ b/content/blog/entries/outreachy-midpoint-progess-with-creative-commons/contents.lr
@@ -26,28 +26,28 @@ The goal of my project is to implement the Vocabulary design system across sever
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/creativecommons.github.io-source/pull/118): Refactored the recent blog post section on the homepage.
-- [PR 856](https://github.com/creativecommons/creativecommons.github.io-source/pull/856): Refactored the homepage markup to align with Vocabulary components.
-- [PR 862](https://github.com/creativecommons/creativecommons.github.io-source/pull/862): Updated `page-with-toc.html`, which serves as a template for many pages.
-- [PR 863](https://github.com/creativecommons/creativecommons.github.io-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/creativecommons.github.io-source/pull/865): Refactored the blog’s author page to match Vocabulary’s “person” context.
-- [PR 866](https://github.com/creativecommons/creativecommons.github.io-source/pull/866): Updated the blog structure to follow Vocabulary markup.
-- [PR 867](https://github.com/creativecommons/creativecommons.github.io-source/pull/867): Refactored the Project List page, leaving the table markup intact but removing old styles.
-- [PR 868](https://github.com/creativecommons/creativecommons.github.io-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/creativecommons.github.io-source/pull/870): Aligned the Authors page with Vocabulary’s team styling.
-- [PR 871](https://github.com/creativecommons/creativecommons.github.io-source/pull/871): Refactored the Project Ideas page, incorporating Vocabulary’s project markup and removing legacy styles.
-- [PR 873](https://github.com/creativecommons/creativecommons.github.io-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/creativecommons.github.io-source/pull/880): Refactored `page-with-title.html` (used by CC Tech Archives) to align with Vocabulary.
-- [PR 886](https://github.com/creativecommons/creativecommons.github.io-source/pull/886): Updated the header component markup and removed old class names.
+- [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/creativecommons.github.io-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/creativecommons.github.io-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/creativecommons.github.io-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/creativecommons.github.io-source/pull/990): Styled the CC Search archive table using Datatables.
+- [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
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/community/code-of-conduct/contents.lr b/content/community/code-of-conduct/contents.lr
index 1a9a5b05d..a390a61f8 100644
--- a/content/community/code-of-conduct/contents.lr
+++ b/content/community/code-of-conduct/contents.lr
@@ -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 3871b041a..8b3066d80 100644
--- a/content/community/code-of-conduct/enforcement/contents.lr
+++ b/content/community/code-of-conduct/enforcement/contents.lr
@@ -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/write-a-blog-post/contents.lr b/content/community/write-a-blog-post/contents.lr
index d71a4b37f..633a2b189 100644
--- a/content/community/write-a-blog-post/contents.lr
+++ b/content/community/write-a-blog-post/contents.lr
@@ -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
@@ -64,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/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
index 919d03d2f..53a6cf93d 100644
--- 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
@@ -41,7 +41,7 @@ resources:
- [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/creativecommons.github.io-source)
+- [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)
diff --git a/databags/community_team_members.json b/databags/community_team_members.json
index d6bb4ee24..0b01e90bd 100644
--- a/databags/community_team_members.json
+++ b/databags/community_team_members.json
@@ -199,7 +199,7 @@
}
],
"name": "CC Open Source",
- "repos": "creativecommons.github.io-source"
+ "repos": "ccos-website-source"
},
{
"members": [
diff --git a/databags/repos.json b/databags/repos.json
index 7dfbb3a6a..c4fb92b8b 100644
--- a/databags/repos.json
+++ b/databags/repos.json
@@ -352,11 +352,11 @@
"language": "HTML",
"license": {
"name": "MIT License",
- "url": "https://github.com/creativecommons/creativecommons.github.io-source/blob/main/LICENSE"
+ "url": "https://github.com/creativecommons/ccos-website-source/blob/main/LICENSE"
},
- "name": "creativecommons.github.io-source",
+ "name": "ccos-website-source",
"slack": "",
- "url": "https://github.com/creativecommons/creativecommons.github.io-source",
+ "url": "https://github.com/creativecommons/ccos-website-source",
"website": "https://opensource.creativecommons.org/"
},
{