Merge branch 'main' into problems-compassion

possumbilities · web-flow · commit 7c23285d572e · 2025-02-04T12:25:23.000-06:00
diff --git a/Pipfile.lock b/Pipfile.lock
diff --git a/content/blog/authors/Queen/contents.lr b/content/blog/authors/Queen/contents.lr
@@ -0,0 +1,11 @@
+username: Queen
+---
+name: Queen Fawale
+---
+md5_hashed_email: 86cfa08b8d93b4f90882a8c19d2f23f3
+---
+about:
+Queen is a front-end engineer and currently an outreachy intern with Creative Commons. You can find me `@Queen` on [CC
+Slack](/community/) and [Queen-codes][github] on GitHub. 
+
+[github]:https://github.com/Queen-codes
diff --git a/content/blog/authors/ahmadbilaldev/contents.lr b/content/blog/authors/ahmadbilaldev/contents.lr
@@ -13,5 +13,5 @@ meetups, conferences and meeting new people. Cats are his weakness, and he is a
 sucker for well-engineered cars.
 
 Ahmad worked on [the CC WordPress
-plugin](https://github.com/creativecommons/wp-plugin-creativecommons) as part
+plugin](https://github.com/cc-archive/wp-plugin-creativecommons) as part
 of [Google Summer of Code (GSoC) 2019](/programs/history/).
diff --git a/content/blog/categories/outreachy-2024/contents.lr b/content/blog/categories/outreachy-2024/contents.lr
@@ -0,0 +1 @@
+name: outreachy-2024
diff --git a/content/blog/entries/2020-03-05-involucrate-gsoc-outreachy-es/contents.lr b/content/blog/entries/2020-03-05-involucrate-gsoc-outreachy-es/contents.lr
@@ -27,7 +27,7 @@ Las pasantías consisten en el desarrollo de un proyecto el cual debe ser llevad
 En las versiones pasadas de estos programas tuvimos excelentes resultados llevados a cabo por excelentes personas que pusieron toda su dedicación para concretar estos proyectos:
 
 ## GSoC 2019
-- [Wordpress Plugin](https://github.com/creativecommons/wp-plugin-creativecommons) por Ahmad Bilal
+- [Wordpress Plugin](https://github.com/cc-archive/wp-plugin-creativecommons) por Ahmad Bilal
 - [CC Search Browser extension](https://github.com/creativecommons/ccsearch-browser-extension) por Mayank Nader
 - [CC Vocabulary](https://github.com/creativecommons/vue-vocabulary) por Dhruv Bhanushali
 - [Revamping the CC Chooser](https://github.com/creativecommons/cc-chooser) por Ari Madian
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
@@ -59,7 +59,7 @@ We will continue to actively develop the following projects:
 -   [License Buttons](https://github.com/creativecommons/licensebuttons/) (maintainer: Timid Robot Zehta)
 -   [Platform Toolkit](https://github.com/creativecommons/mp/) (maintainer: Timid Robot Zehta)
 -   [Vocabulary](https://github.com/creativecommons/vocabulary) (maintainers: Zack Krida & Dhruv Bhanushali)
--   [WordPress Plugin](https://github.com/creativecommons/wp-plugin-creativecommons) (new maintainer: Zack Krida)
+-   [WordPress Plugin](https://github.com/cc-archive/wp-plugin-creativecommons) (new maintainer: Zack Krida)
 
 **Maintenance Mode**
 
diff --git a/content/blog/entries/2025-01-15-skipping-gsoc-2025/contents.lr b/content/blog/entries/2025-01-15-skipping-gsoc-2025/contents.lr
@@ -0,0 +1,58 @@
+title: Skipping Google Summer of Code (GSoC) 2025
+---
+categories:
+gsoc
+open-source
+community
+---
+author: TimidRobot
+---
+pub_date: 2025-01-15
+---
+body:
+
+The Creative Commons (CC) technology team regrets to announce **we will not be
+participating in Google Summer of Code (GSoC) 2025**. While the program remains
+excellent, we do not have the resources to participate this year and meet our
+core responsibilities.
+
+We are grateful to Google for the program and have found incredible value in
+participating in past years. We look forward to participating in future years.
+We are thankful for the work and time of contributors. This is not an exciting
+announcement, but we will be better equipped to engage with work programs in
+the future.
+
+
+## Preparing to re-engage
+
+In addition to revamping our CC Open Source website during the first quarter of
+this year, we will also be refreshing our structured community involvement, and
+improving our project lead resources.
+
+Our CC Open Source website is in the process of being updated to be less
+technologically complex and to leverage the current Vocabulary design system
+([creativecommons/vocabulary][vocabulary]).
+
+Our structured community involvement has languished since the technology team
+was downsized due to the COVID pandemic (202-12-07 [Upcoming Changes to the CC
+Open Source Community — Creative Commons Open Source][changes]). We will be
+simplifying community involvement so that we can be more responsive with
+increased visibility.
+
+The most resource intensive period of a work program is the application phase.
+During this time there is a deluge of activity that has often exceeded our
+capacity. Developing our project lead resources will allow us to better set
+expectations, ease communications, and better point applicants on productive
+trajectories.
+
+[vocabulary]: http://github.com/creativecommons/vocabulary
+[changes]: https://opensource.creativecommons.org/blog/entries/2020-12-07-upcoming-changes-to-community/
+
+
+## Past participation
+
+For information on the excellent work completed during past participations,
+please see: [Open Source Work Programs: History — Creative Commons Open
+Source][history].
+
+[history]: https://opensource.creativecommons.org/programs/history/
diff --git a/content/blog/entries/cc-wp-plugin-final-phase/contents.lr b/content/blog/entries/cc-wp-plugin-final-phase/contents.lr
@@ -78,6 +78,6 @@ option, which is much better than previous footer implementation.
 - Integrate WPGulp workflow and improve i18n.
 - Improve documentation with a visual walk-around of every feature.
 
-Thank you for reading. For more, see the [GitHub repository](https://github.com/creativecommons/wp-plugin-creativecommons).
+Thank you for reading. For more, see the [GitHub repository](https://github.com/cc-archive/wp-plugin-creativecommons).
 
 If you have any feedback or suggestions, let us know in the discussion on `#cc-dev-wordpress` Slack channel. Looking forward!
diff --git a/content/blog/entries/cc-wp-plugin-second-phase/contents.lr b/content/blog/entries/cc-wp-plugin-second-phase/contents.lr
@@ -23,7 +23,7 @@ For the context, I am working with my mentor [Timid Robot](https://creativecommo
 
 ### Release of v2019.7.1
 
-We have released the latest stable version of the plugin. `v2019.7.1` is out and tagged in the [wp-plugin-creativecommons repository](https://github.com/creativecommons/wp-plugin-creativecommons/releases). Given that a stable release is available, we have submitted it to [WordPress.org plugin directory](https://en-nz.wordpress.org/plugins/). As soon as their team approves it, the plugin will be available to install for all WordPress users, which is substantial.
+We have released the latest stable version of the plugin. `v2019.7.1` is out and tagged in the [wp-plugin-creativecommons repository](https://github.com/cc-archive/wp-plugin-creativecommons/releases). Given that a stable release is available, we have submitted it to [WordPress.org plugin directory](https://en-nz.wordpress.org/plugins/). As soon as their team approves it, the plugin will be available to install for all WordPress users, which is substantial.
 
 ### What's next
 
@@ -34,6 +34,6 @@ Although the current implentation does the job, but we want it to use new [CC Li
 - Changes in design and features.
 - Improve the documentation.
 
-For more, see the [GitHub repository](https://github.com/creativecommons/wp-plugin-creativecommons).
+For more, see the [GitHub repository](https://github.com/cc-archive/wp-plugin-creativecommons).
 
 If you have any feedback or suggestions, let us know in the discussion on `#cc-dev-wordpress` Slack channel. Looking forward!
diff --git a/content/blog/entries/my-outreachy-internship-with-creative-commons/contents.lr b/content/blog/entries/my-outreachy-internship-with-creative-commons/contents.lr
@@ -0,0 +1,56 @@
+title: My Outreachy Internship With Creative Commons
+---
+categories:
+outreachy
+outreachy-2024
+open-source
+community
+---
+author: Queen
+---
+series: outreachy-dec-2024-consolidating-and-implementing-vocabulary
+---
+pub_date: 2024-12-10
+---
+body:
+
+## Introduction  
+Hi, everyone! My name is Queen, and I’m a fresh pharmacy graduate with a passion for tech. My journey into coding started four years ago when I wrote my first HTML code and thought, "Yes, I’m FAANG-ready!" Spoiler: I wasn’t — but that didn’t stop me from dreaming big. Balancing pharmacy school and learning to code often felt like I was biting off more than I could chew, but I’m proud that I never gave up on my dream of becoming a front-end developer.
+
+## My Core Values  
+When I think about my core values, three words come to mind: **Growth**, **Curiosity**, and **Knowledge**.  
+
+- **Growth**: I strive to improve in every aspect of life—mentally, physically, intellectually, and even spiritually. Every setback is just a stepping stone for me.  
+- **Curiosity**: This one’s a work in progress, but I’m learning to ask questions and embrace not knowing. I love understanding *why* things work the way they do.  
+- **Knowledge**: I read a lot because I genuinely enjoy learning new things. For me, knowledge is the key to confidence and growth.
+
+## My Journey to Outreachy  
+Outreachy is a three-month paid open-source internship program for underrepresented people in tech. I first heard about it last year—just two days before the application deadline. I didn’t make it past the initial application stage that time.  
+
+When the December 2024 cohort initial application opened, it was the perfect timing for me. By then, I had finished my pharmacy degree and was ready to gain professional experience in front-end development and most especially, in open source. This time, I was determined to get it right.  
+
+I applied on the same day the application opened, I had already kept answers for the essay questions in my notes app. While waiting for the results, I brushed up on my skills and read articles from past interns to prepare for the contribution period.
+
+When I received the email saying my initial application had been approved, I felt a rush of excitement. To move forward and be able to make a final application, I needed to make at least one contribution to a project. I narrowed my choices to two based on the skills required, but Creative Commons stood out to me. Their mission and the project description piqued my interest more.  
+
+## The Contribution Period  
+The contribution period was competitive—and intimidating. Seeing the amazing work other applicants were doing made me doubt myself. But I loved the project and found the community so welcoming that I couldn’t give up.  
+
+The mentors were incredibly supportive, giving feedback that helped me improve with each contribution. When it was time to draft my final application and proposal, I worked with my mentor, sharing my plans and got her input which helped me in creating my project timeline.  
+
+Even before I knew if I’d be selected, I felt fulfilled. Contributing to Creative Commons was a rewarding experience, and I knew I wanted to continue contributing to the community, intern or not.  
+
+## My Internship Project  
+### **Consolidating and Implementing the Vocabulary Design System**  
+During my internship, I’ll be working on consolidating and implementing the Vocabulary design system across Creative Commons' ancillary websites.  
+
+Vocabulary is a design system that ensures a consistent user interface (UI) and user experience (UX) across all Creative Commons websites. However, its implementation has been inconsistent, with variations in features and versions across different sites. My role is to identify these inconsistencies and work on a unified implementation that also focuses on accessibilty. I'd also be implementing features that might be a good addition to the design system.
+
+I’m excited about this project because it aligns with my passion for front-end development and allows me to contribute meaningfully to a global community. I also get to improve my skills and gain new ones.
+
+## Conclusion  
+This internship is more than just a milestone for me—it’s a testament to perseverance and growth. I’m thrilled to embark on this journey with Creative Commons, and I can’t wait to see where it leads.  
+
+If you’re considering applying for Outreachy, my advice is simple: believe in yourself, stay curious, and never stop learning. Your journey might just surprise you.  
+
+Thank you for reading!  
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
@@ -0,0 +1,73 @@
+title: Outreachy Midpoint Progress With Creative Commons
+---
+categories:
+outreachy
+outreachy-2024
+open-source
+community
+---
+author: Queen
+---
+series: outreachy-dec-2024-consolidating-and-implementing-vocabulary
+---
+pub_date: 2025-01-19
+---
+body:
+# Outreachy Midpoint Blog Post
+
+Hi there! My name is Queen, and I’m an Outreachy intern at Creative Commons. My project involves consolidating and implementing the Vocabulary design system across Creative Commons ancillary websites. In this post, I’ll share my progress and key takeaways from the first half of my internship.
+
+## Project Overview
+
+The goal of my project is to implement the Vocabulary design system across several Creative Commons ancillary websites like the [CC Open Source](https://opensource.creativecommons.org/), [CC Legal Database](https://legaldb.creativecommons.org/en/), [CC Search Portal](https://search.creativecommons.org/), and [CC Resource Archive](https://resources.creativecommons.org/).
+## Progress So Far
+
+### Phase One: Refactoring Markup to Align with Vocabulary
+
+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.
+
+### 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.
+
+## Current Status
+
+I’m a little behind schedule—I had planned to start work on the Legal Database website by now. However, I’m wrapping up the CC Open Source website this week and will move on to the next phase soon.
+
+## Lessons Learned
+
+This internship has been an incredible learning journey. Here are some key takeaways:
+
+### Technical Skills:
+- I’ve become comfortable working with [Lektor](https://getlektor.com/), a static site generator that was entirely new to me.
+- Implementing the Vocabulary design system has improved my problem-solving skills, especially when dealing with legacy code and adapting the system to fit unique website needs.
+- To localize the table component, I had to read the [DataTables documentation](https://datatables.net/), which helped my ability to learn on the go.
+
+### Collaboration:
+Working with mentors has taught me the value of clear communication, especially when addressing blockers or seeking feedback.
+
+### Project Management:
+Breaking tasks into smaller chunks, prioritizing effectively, and maintaining consistent progress have been critical in managing this project.
+
+This experience has significantly boosted my confidence as a front-end developer, particularly in creating user-friendly and accessible interfaces.
+
+That’s it for now! Thank you for reading about my progress. I’m excited to see how the second half of this journey unfolds!
diff --git a/content/blog/series/outreachy-dec-2024-consolidating-and-implementing-vocabulary/contents.lr b/content/blog/series/outreachy-dec-2024-consolidating-and-implementing-vocabulary/contents.lr
@@ -0,0 +1 @@
+name: Outreachy Dec 2024: Consolidating and Implementing Vocabulary
diff --git a/content/community/contents.lr b/content/community/contents.lr
@@ -53,7 +53,6 @@ The channels most relevant to CC's developer community are:
 | `#cc-dev-platform-toolkit` | [mp][mp] project (CC Platform Toolkit) |
 | `#cc-dev-searchportal` | [search][search] project |
 | `#cc-dev-vocabulary` | [cc-vocabulary][cc-vocabulary] project |
-| `#cc-dev-wordpress` | [wp-plugin-creativecommons][wp-plugin-creativecommons] project (creativecommons WordPress plugin) |
 | `#cc-dev-workprograms` | **GSoC, GSoD, Outreachy, and other [work programs][workprograms] or internships** |
 | `#cc-developers` | **general technical issues, new tech blog posts, etc.** |
 | `#cc-translation` | Coordinating translation efforts |
@@ -66,7 +65,6 @@ The channels most relevant to CC's developer community are:
 [mp]: https://github.com/creativecommons/mp
 [cc-vocabulary]: https://github.com/creativecommons/cc-vocabulary
 [search]: https://github.com/creativecommons/search
-[wp-plugin-creativecommons]: https://github.com/creativecommons/wp-plugin-creativecommons
 [workprograms]: /programs/
 
 
diff --git a/content/community/write-a-blog-post/contents.lr b/content/community/write-a-blog-post/contents.lr
@@ -54,6 +54,8 @@ Once you have written your post, you can either send it to us (Markdown is easie
   ---
   pub_date: Replace this text with the publication date in YYYY-MM-DD format.
   ---
+  excerpt: Replace this text with a summary of your blog post. This is an optional field. If left blank, the first 100 characters of your blog post will be used.
+  ---
   body:
   Replace this text with your post's content (minus the title). This field accepts Markdown for formatting.
   If you're including images, you can use the Markdown image syntax i.e. ![image-title](image-file-name.jpg).
diff --git a/content/programs/contents.lr b/content/programs/contents.lr
@@ -22,25 +22,21 @@ CC isn't currently participating in Google Season of Docs (GSoD).
 
 ### Google Summer of Code
 
-CC will apply for participation in Google Summer of Code (GSoC) 2025.
+CC is [Skipping Google Summer of Code (GSoC) 2025][skipping2025]. We hope to
+apply again to participate in 2026.
 
 - [Program website](https://summerofcode.withgoogle.com/)
 
-<!--
-- [CC's GSoC 2025 page][gsoc2025cc]
-
-[gsoc2025cc]: https://summerofcode.withgoogle.com/programs/2025/organizations/creative-commons
--->
+[skipping2025]: /blog/entries/2025-01-15-skipping-gsoc-2025/
 
 
 ### Outreachy
 
-CC is participating in the December 2024 cohort.
+CC is participating in the December 2024 cohort. We are planning on also participating in the December 2025 cohort.
 
 - [Program website](https://www.outreachy.org/)
 - [CC's Outreachy page][outreachycc]
 
-[dec2022]: https://www.outreachy.org/apply/project-selection/#creative-commons
 [outreachycc]: https://www.outreachy.org/communities/cfp/creative-commons/
 
 
diff --git a/databags/community_team_members.json b/databags/community_team_members.json
diff --git a/databags/repos.json b/databags/repos.json
diff --git a/models/blog-post.ini b/models/blog-post.ini
diff --git a/themes/vocabulary_theme/templates/macros/posts.html b/themes/vocabulary_theme/templates/macros/posts.html
diff --git a/webpack/package-lock.json b/webpack/package-lock.json

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+name: Outreachy Dec 2024: Consolidating and Implementing Vocabulary`