creativecommons · TimidRobot · Apr 21, 2025 · Apr 21, 2025
@@ -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

@@ -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
@@ -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
@@ -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)

@@ -265,25 +265,25 @@ Here's the link to the [documentation site](https://cc-vocabulary.netlify.app).
 <td><a href="https://github.com/cc-archive/vocabulary-legacy/issues/736">https://github.com/cc-archive/vocabulary-legacy/issues/736</a></td>
 </tr>
 <tr>
-<td rowspan=5><a href="https://github.com/creativecommons/creativecommons.github.io-source">@creativecommons/creativecommons.github.io-source</a></td>
+<td rowspan=5><a href="https://github.com/creativecommons/ccos-website-source">@creativecommons/ccos-website-source</a></td>
 <td>Introductory First Blog Post</td>
-<td><a href="https://github.com/creativecommons/creativecommons.github.io-source/pull/530">https://github.com/creativecommons/creativecommons.github.io-source/pull/530</a><br><a href="/blog/entries/cc-vocabulary-docs-intro/">/blog/entries/cc-vocabulary-docs-intro/</a></td>
+<td><a href="https://github.com/creativecommons/ccos-website-source/pull/530">https://github.com/creativecommons/ccos-website-source/pull/530</a><br><a href="/blog/entries/cc-vocabulary-docs-intro/">/blog/entries/cc-vocabulary-docs-intro/</a></td>
 </tr>
 <tr>
 <td>Vocabulary Site Update v1</td>
-<td><a href="https://github.com/creativecommons/creativecommons.github.io-source/pull/549">https://github.com/creativecommons/creativecommons.github.io-source/pull/549</a><br><a href="/blog/entries/cc-vocabulary-docs-updates-1/">/blog/entries/cc-vocabulary-docs-updates-1/</a></td>
+<td><a href="https://github.com/creativecommons/ccos-website-source/pull/549">https://github.com/creativecommons/ccos-website-source/pull/549</a><br><a href="/blog/entries/cc-vocabulary-docs-updates-1/">/blog/entries/cc-vocabulary-docs-updates-1/</a></td>
 </tr>
 <tr>
 <td>Vocabulary Mid Internship Update v2</td>
-<td><a href="https://github.com/creativecommons/creativecommons.github.io-source/pull/555">https://github.com/creativecommons/creativecommons.github.io-source/pull/555</a><br><a href="/blog/entries/cc-vocabulary-docs-updates-2/">/blog/entries/cc-vocabulary-docs-updates-2/</a></td>
+<td><a href="https://github.com/creativecommons/ccos-website-source/pull/555">https://github.com/creativecommons/ccos-website-source/pull/555</a><br><a href="/blog/entries/cc-vocabulary-docs-updates-2/">/blog/entries/cc-vocabulary-docs-updates-2/</a></td>
 </tr>
 <tr>
 <td>Vocabulary Site Update v3</td>
-<td><a href="https://github.com/creativecommons/creativecommons.github.io-source/pull/561">https://github.com/creativecommons/creativecommons.github.io-source/pull/561</a><br><a href="/blog/entries/cc-vocabulary-docs-updates-3/">/blog/entries/cc-vocabulary-docs-updates-3/</a></td>
+<td><a href="https://github.com/creativecommons/ccos-website-source/pull/561">https://github.com/creativecommons/ccos-website-source/pull/561</a><br><a href="/blog/entries/cc-vocabulary-docs-updates-3/">/blog/entries/cc-vocabulary-docs-updates-3/</a></td>
 </tr>
 <tr>
 <td>Vocabulary Site Final Update</td>
-<td><a href="https://github.com/creativecommons/creativecommons.github.io-source/pull/564">https://github.com/creativecommons/creativecommons.github.io-source/pull/564</a><br><a href="/">/blog/entries/cc-vocabulary-docs-updates-closing/</a></td>
+<td><a href="https://github.com/creativecommons/ccos-website-source/pull/564">https://github.com/creativecommons/ccos-website-source/pull/564</a><br><a href="/">/blog/entries/cc-vocabulary-docs-updates-closing/</a></td>
 </tr>
 <tr>
 <td><a href="https://github.com/cc-archive/cccatalog-api">@cc-archive/cccatalog-api</a></td>

@@ -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
 

@@ -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 -
 

@@ -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
 

@@ -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