Merge pull request #781 from creativecommons/update-links

update links to `vocabulary-legacy`, fix other errors encountered along the way

content/blog/authors/nimishbongale/contents.lr

@@ -9,5 +9,5 @@ about:
 [Nimish Bongale](https://nimishbongale.github.io/) is a Technical Writing
 Intern at Creative Commons. He goes by `@nimishnb` on the CC Community Slack
 workspace. Nimish developed the website and documentation for [CC
-Vocabulary](https://github.com/creativecommons/vocabulary/) as part of [Google
+Vocabulary Legacy](https://github.com/cc-archive/vocabulary-legacy/) as part of [Google
 Season of Docs (GSoD) 2020](/programs/history/).

content/blog/entries/2022-11-11-calver-to-semver/contents.lr

@@ -66,7 +66,7 @@ example, NPM currently strips leading zeros which breaks CDN integration
 ([CalVer and CDN compatibility · Issue #588 ·
 creativecommons/vocabulary][issue588]).
 
-[issue588]: https://github.com/creativecommons/vocabulary/issues/588.
+[issue588]: https://github.com/cc-archive/vocabulary-legacy/issues/588.
 
 
 ## Using SemVer

content/blog/entries/cc-platform-toolkit-revamp-4/contents.lr

@@ -15,7 +15,7 @@ pub_date: 2020-03-04
 body:
 Phew, how is it possible that we're already in March? Between my last check-in and today, there was a lot of work and effort into revamping the [Platform Toolkit](https://creativecommons.org/platform/toolkit/).
 
-There were two rounds of user interviews: the first one was done looking only at the wireframe, focusing exclusively on usability and content. This provided a lot of important feedback to adjust the structure and move forward with the UI.  I tried my best to apply the design standards already mapped out by the [Vocabulary](https://github.com/creativecommons/vocabulary/) project, so that in the future this wouldn't stand out from other CC materials.
+There were two rounds of user interviews: the first one was done looking only at the wireframe, focusing exclusively on usability and content. This provided a lot of important feedback to adjust the structure and move forward with the UI.  I tried my best to apply the design standards already mapped out by the [Vocabulary Legacy](https://github.com/cc-archive/vocabulary-legacy/) project, so that in the future this wouldn't stand out from other CC materials.
 
 The second round of user interviews was done with a UI prototype, and was meant to take away some of my doubts regarding a few choices in this project. For instance, would it be best for the user to have the information in a single page, or would that be too much, and best to split in separate pages? There were pros and cons to both scenarios, but in the end we decided to stick with the single-page format because of a particular behavior: one of the ways users search for content is to ctrl+F and look for keywords. That would be drastically less effective with multiple pages.
 

content/blog/entries/cc-vocabulary-docs-updates-3/contents.lr

@@ -26,7 +26,7 @@ Excited to know more about this week's vocabulary site updates? Read on to find
 
 Merged? Yes. **Merged**. Here's my story!
 
-- After getting a thumbs up from the UX Designer, I put up my [GSoD Website PR](https://github.com/creativecommons/vocabulary/pull/747) for review.
+- After getting a thumbs up from the UX Designer, I put up my [GSoD Website PR](https://github.com/cc-archive/vocabulary-legacy/pull/747) for review.
 - I was confident there would be changes, and I let them roll in. It's important to note here that what seems perfect to you may not be so to others, and only experience teaches you the right from the wrong.
 - There were a few of them, mainly dealing with spacing, textual content and colors. I resolved them as soon as I could.
 -  [zackkrida](/blog/authors/zackkrida/) has been kind enough to point and enumerate all of them for me!
@@ -53,9 +53,9 @@ Merged? Yes. **Merged**. Here's my story!
 
 Being a part of an open source organisation also means that I must try to bring in contributions from existing & first time contributors. Here's a peek into my efforts for the same:
 
-- The [dark mode PR](https://github.com/creativecommons/vocabulary/pull/806) started off as a hacktoberfest contribution, and it is now complete!
+- The [dark mode PR](https://github.com/cc-archive/vocabulary-legacy/pull/806) started off as a hacktoberfest contribution, and it is now complete!
 - Created a `/shared` package to house common files between packages (such as the dark & light theme after referring to the [React](https://reactjs.org/) documentation.
-- The automated npm [README.md customisation](https://github.com/creativecommons/vocabulary/pull/746) is now up and running. (really had a blast solving that issue!)
+- The automated npm [README.md customisation](https://github.com/cc-archive/vocabulary-legacy/pull/746) is now up and running. (really had a blast solving that issue!)
 - If the snapshot testing stands approved, we'll have it running on chromatic!
 - Raised issues to add multiple badges to the root README.md  file; namely `maintained with Lerna` & custom badges for package sizes from [packagephobia](https://packagephobia.com/).
 

content/blog/entries/cc-vocabulary-docs-updates-closing/contents.lr

@@ -210,59 +210,59 @@ Here's the link to the [documentation site](https://cc-vocabulary.netlify.app).
 <tr>
 <td rowspan=14><a href="https://github.com/creativecommons/vocabulary">@creativecommons/vocabulary</a></td>
 <td>Developed the CC Vocabulary Landing Page</td>
-<td><a href="https://github.com/creativecommons/vocabulary/pull/747">https://github.com/creativecommons/vocabulary/pull/747<br><a href="https://cc-vocab-draft.web.app">https://cc-vocab-draft.web.app</a></td>
+<td><a href="https://github.com/cc-archive/vocabulary-legacy/pull/747">https://github.com/cc-archive/vocabulary-legacy/pull/747<br><a href="https://cc-vocab-draft.web.app">https://cc-vocab-draft.web.app</a></td>
 </tr>
 <tr>
 <td>Implemented dark mode for our storybooks</td>
-<td><a href="https://github.com/creativecommons/vocabulary/pull/806">https://github.com/creativecommons/vocabulary/pull/806</a><br><a href="https://cc-vocabulary.netlify.app">https://cc-vocabulary.netlify.app</a></td>
+<td><a href="https://github.com/cc-archive/vocabulary-legacy/pull/806">https://github.com/cc-archive/vocabulary-legacy/pull/806</a><br><a href="https://cc-vocabulary.netlify.app">https://cc-vocabulary.netlify.app</a></td>
 </tr>
 <tr>
 <td>Carried out a monorepo wide documentation revamp</td>
-<td><a href="https://github.com/creativecommons/vocabulary/pull/813">https://github.com/creativecommons/vocabulary/pull/813</a></td>
+<td><a href="https://github.com/cc-archive/vocabulary-legacy/pull/813">https://github.com/cc-archive/vocabulary-legacy/pull/813</a></td>
 </tr>
 <tr>
 <td>Wrote the Monorepo Documentation Story</td>
-<td><a href="https://github.com/creativecommons/vocabulary/pull/785">https://github.com/creativecommons/vocabulary/pull/785</a><br><a href="https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-structure--page#why-is-vocabulary-a-monorepo">https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-structure--page#why-is-vocabulary-a-monorepo</a></td>
+<td><a href="https://github.com/cc-archive/vocabulary-legacy/pull/785">https://github.com/cc-archive/vocabulary-legacy/pull/785</a><br><a href="https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-structure--page#why-is-vocabulary-a-monorepo">https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-structure--page#why-is-vocabulary-a-monorepo</a></td>
 </tr>
 <tr>
 <td>Wrote the Grid Documentation Story</td>
-<td><a href="https://github.com/creativecommons/vocabulary/pull/802">https://github.com/creativecommons/vocabulary/pull/802</a><br><a href="https://cc-vocabulary.netlify.app/?path=/docs/layouts-grid--fullhd#grid-system">https://cc-vocabulary.netlify.app/?path=/docs/layouts-grid--fullhd#grid-system</a></td>
+<td><a href="https://github.com/cc-archive/vocabulary-legacy/pull/802">https://github.com/cc-archive/vocabulary-legacy/pull/802</a><br><a href="https://cc-vocabulary.netlify.app/?path=/docs/layouts-grid--fullhd#grid-system">https://cc-vocabulary.netlify.app/?path=/docs/layouts-grid--fullhd#grid-system</a></td>
 </tr>
 <tr>
 <td>Wrote the "Getting Started" Usage Guide</td>
-<td><a href="https://github.com/creativecommons/vocabulary/pull/774">https://github.com/creativecommons/vocabulary/pull/774</a><br><a href="https://cc-vocabulary.netlify.app/?path=/story/vocabulary-getting-started--page#getting-started">https://cc-vocabulary.netlify.app/?path=/story/vocabulary-getting-started--page#getting-started</a></td>
+<td><a href="https://github.com/cc-archive/vocabulary-legacy/pull/774">https://github.com/cc-archive/vocabulary-legacy/pull/774</a><br><a href="https://cc-vocabulary.netlify.app/?path=/story/vocabulary-getting-started--page#getting-started">https://cc-vocabulary.netlify.app/?path=/story/vocabulary-getting-started--page#getting-started</a></td>
 </tr>
 <tr>
 <td>Added a CHANGELOG.md to adhere to OSS conventions</td>
-<td><a href=https://github.com/creativecommons/vocabulary/pull/671">https://github.com/creativecommons/vocabulary/pull/671</a><br><a href="https://github.com/creativecommons/vocabulary/blob/main/CHANGELOG.md">https://github.com/creativecommons/vocabulary/blob/main/CHANGELOG.md</a></td>
+<td><a href=https://github.com/cc-archive/vocabulary-legacy/pull/671">https://github.com/cc-archive/vocabulary-legacy/pull/671</a><br><a href="https://github.com/cc-archive/vocabulary-legacy/blob/main/CHANGELOG.md">https://github.com/cc-archive/vocabulary-legacy/blob/main/CHANGELOG.md</a></td>
 </tr>
 <tr>
 <td>Unified README.md and updated monorepo build process</td>
-<td><a href="https://github.com/creativecommons/vocabulary/pull/649">https://github.com/creativecommons/vocabulary/pull/649</a><br><a href="https://www.npmjs.com/package/@creativecommons/vocabulary">https://www.npmjs.com/package/@creativecommons/vocabulary</a><br><a href="https://www.npmjs.com/package/@creativecommons/fonts">https://www.npmjs.com/package/@creativecommons/fonts</a><br><a href="https://www.npmjs.com/package/@creativecommons/vue-vocabulary">https://www.npmjs.com/package/@creativecommons/vue-vocabulary</a></td>
+<td><a href="https://github.com/cc-archive/vocabulary-legacy/pull/649">https://github.com/cc-archive/vocabulary-legacy/pull/649</a><br><a href="https://www.npmjs.com/package/@creativecommons/vocabulary">https://www.npmjs.com/package/@creativecommons/vocabulary</a><br><a href="https://www.npmjs.com/package/@creativecommons/fonts">https://www.npmjs.com/package/@creativecommons/fonts</a><br><a href="https://www.npmjs.com/package/@creativecommons/vue-vocabulary">https://www.npmjs.com/package/@creativecommons/vue-vocabulary</a></td>
 </tr>
 <tr>
 <td>Configured GitHub native dependabot</td>
-<td><a href="https://github.com/creativecommons/vocabulary/pull/452">https://github.com/creativecommons/vocabulary/pull/452</a></td>
+<td><a href="https://github.com/cc-archive/vocabulary-legacy/pull/452">https://github.com/cc-archive/vocabulary-legacy/pull/452</a></td>
 </tr>
 <tr>
 <td>Added phone screen backgrounds</td>
-<td><a href="https://github.com/creativecommons/vocabulary/pull/445">https://github.com/creativecommons/vocabulary/pull/445</a></td>
+<td><a href="https://github.com/cc-archive/vocabulary-legacy/pull/445">https://github.com/cc-archive/vocabulary-legacy/pull/445</a></td>
 </tr>
 <tr>
 <td>Introduce Snapshot Testing to Vocabulary using Chromatic</td>
-<td><a href="https://github.com/creativecommons/vocabulary/issues/735">https://github.com/creativecommons/vocabulary/issues/735</a></td>
+<td><a href="https://github.com/cc-archive/vocabulary-legacy/issues/735">https://github.com/cc-archive/vocabulary-legacy/issues/735</a></td>
 </tr>
 <tr>
 <td>Add a maintained with Lerna badge</td>
-<td><a href="https://github.com/creativecommons/vocabulary/issues/807">https://github.com/creativecommons/vocabulary/issues/807</a><br><a href="https://github.com/creativecommons/vocabulary/blob/main/README.md">https://github.com/creativecommons/vocabulary/blob/main/README.md</a></td>
+<td><a href="https://github.com/cc-archive/vocabulary-legacy/issues/807">https://github.com/cc-archive/vocabulary-legacy/issues/807</a><br><a href="https://github.com/cc-archive/vocabulary-legacy/blob/main/README.md">https://github.com/cc-archive/vocabulary-legacy/blob/main/README.md</a></td>
 </tr>
 <tr>
 <td>Add new install size badges for our packages</td>
-<td><a href="https://github.com/creativecommons/vocabulary/issues/776">https://github.com/creativecommons/vocabulary/issues/776</a><br><a href="https://github.com/creativecommons/vocabulary/blob/main/README.md">https://github.com/creativecommons/vocabulary/blob/main/README.md</a</td>
+<td><a href="https://github.com/cc-archive/vocabulary-legacy/issues/776">https://github.com/cc-archive/vocabulary-legacy/issues/776</a><br><a href="https://github.com/cc-archive/vocabulary-legacy/blob/main/README.md">https://github.com/cc-archive/vocabulary-legacy/blob/main/README.md</a</td>
 </tr>
 <tr>
 <td>Customise individual README's for our packages</td>
-<td><a href="https://github.com/creativecommons/vocabulary/issues/736">https://github.com/creativecommons/vocabulary/issues/736</a></td>
+<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>

content/blog/entries/cc-vocabulary-week9-13/contents.lr

@@ -18,7 +18,7 @@ body:
 This will be my last blog as an Outreachy intern. My watch as an intern has come to an end.  I am glad I chose the Creative Commons community or rather am glad Creative Commons chose me (am not the chosen one). I have gained a lot of valuable knowledge, skills and I am more confident in my abilities.
 
 ##Summary of  My Internship with Vocabulary
-I have been more involved with the Vocabulary project during my internship and am happy with the work that has been done so far. I made 24 pull requests with 17 merged. My last contribution was adding a [header component](https://github.com/creativecommons/vocabulary/pull/145) to the revamped Vocabulary. Here is a summary of my time with Vocabulary.
+I have been more involved with the Vocabulary project during my internship and am happy with the work that has been done so far. I made 24 pull requests with 17 merged. My last contribution was adding a [header component](https://github.com/cc-archive/vocabulary-legacy/pull/145) to the revamped Vocabulary. Here is a summary of my time with Vocabulary.
 
 ###When I started my Internship, Vocabulary comprised of:
 - UI components built with Vue

content/community/write-a-blog-post/contents.lr

@@ -29,7 +29,7 @@ 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/))
 
-<p class="text-muted"><em>If you have more tips, <a href="https://github.com/creativecommons/vocabulary/blob/main/content/community/write-a-blog-post/contents.lr">submit an edit to this page</a>.</em></p>
+<p class="text-muted"><em>If you have more tips, <a href="https://github.com/creativecommons/creativecommons.github.io-source/blob/main/content/community/write-a-blog-post/contents.lr">submit an edit to this page</a>.</em></p>
 
 ## How to post
 

content/contributing-code/github-repo-guidelines/contents.lr

@@ -38,9 +38,9 @@ these files:
 [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/vocabulary/blob/main/CODE_OF_CONDUCT.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/vocabulary/blob/main/CONTRIBUTING.md
+[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