Merge branch 'master' into open-graph-image-generation

Author: zackkrida

content/blog/authors/krysal/contents.lr

@@ -5,4 +5,4 @@ name: Krystle Salazar
 md5_hashed_email: f36bcb2678c0c0845f8adf634c4d764b
 ---
 about:
-Krystle is a Software Developer from Venezuela, working on **Reimplement [CC’s Legal Database](https://github.com/creativecommons/caselaw) using Django** as part of Outreachy Summer round of 2020. You can find her as `@krysal` on the CC Slack.
+Krystle is a Software Developer from Venezuela, working on **Reimplement [CC’s Legal Database](https://github.com/creativecommons/legaldb) using Django** as part of Outreachy Summer round of 2020. You can find her as `@krysal` on the CC Slack.

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

@@ -0,0 +1,87 @@
+title: Vocabulary Site Mid-Internship Update (v2)
+---
+categories:
+cc-vocabulary
+gsod
+gsod-2020
+---
+author: nimishbongale
+---
+series: gsod-2020-vocabulary-usage-guide
+---
+pub_date: 2020-11-09
+---
+body:
+This is a mid-internship blog post. Wait. what!? Already? Let's glance over my progress, shall we?
+
+## Vocabulary Site Updates (Edition 2/many more to come)
+
+Oh boy! 1.5 months have passed since I've been investing time in building a landing site & usage guide for CC Vocabulary. A lot has changed since the time of posting my last blog post. **A lot**.
+
+<center>
+<img alt"Halfway There" src="speed.gif"/><br>
+<small class="muted">Hitting "the point of no return" has never been this exciting! Time to step on the throttle! Source: <a href="https://cliply.co">Cliply</a></small>
+</center>
+
+### What I've been up to
+
+> **Designing** ⇨ **Drafting** ⇨ **Developing** ⇨ **Debugging** ⇨ **Deploying**
+
+And the cycle contrinues. I guess it sums it all up very nicely. _Can somebody appreciate the alliteration though?_ 
+
+Here's a gist of what I've achieved so far:
+
+- I've gone through **2** iterations of the design. I'm happy with how the new site looks (and I genuinely hope the design team does too!).
+- I've drafted around **5+** writeups dealing with Monorepo Migration, Getting Started guide, Vocabulary Overview and of course these blog posts.
+- My branch on the vocabulary repository now has over **50+** commits & over **13,000** lines of code (not that I've written all of them, but you know, just for the stats)
+- The first draft of the vocabulary site is now live! I'm expecting a whole bunch of changes still, but here it is if you want to have a sneak peek: [https://cc-vocab-draft.surge.sh](https://cc-vocab-draft.surge.sh)
+-  I've consumed the [Github API](https://docs.github.com/en/free-pro-team@latest/rest) to get live release history, forks and starrers count. I think it adds a really nice touch to the site in general.
+- I've used [surge.sh](https://surge.sh) to deploy the draft site. I believe it's a really simple tool to have your site deployed within seconds!
+
+<center>
+<img alt"Github commit gif" src="github.png"/><br>
+<small class="muted">My github contribution chart is filling up!</small>
+</center>
+
+### What I've learnt
+
+Some say it's hard to learn through virtual internships. Well, let me prove you wrong. Here are my leanings in the past few weeks:
+
+- It's surprising how subjective (& yet objective) designing really is.
+- Vue.js is _fantastic_. Maybe I'm a Vue.js fan now. Should I remain loyal to React? I don't know.
+- Making a site responsive isn't the _easiest_ of tasks, but it's certainly doable after a lot of stretching & compressing; lets say that.
+- "Code formatting is essential" would be an _understatement_ to make.
+- Monorepo's have their own pro's and con's. But in our case the con's were negligible, thankfully! 
+-  I'll be following up with some performance & accessibility testing this coming week, so let's see how that plays out!
+- A mentor plays a vital role in any project. My mentor `@dhruvkb` has been very supportive and has made sure I stick to my timeline!
+
+### Other community work tidbits
+
+I believe apart from the internship work that I'm engaged in, I should also help around with some community PR work. I've been told I'm always welcome to, which is great!
+
+- I got the opportunity to speak at a CCOS event alongwith fellow speakers [dhruvkb](https://opensource.creativecommons.org/blog/authors/dhruvkb/) & [dhruvi16](https://opensource.creativecommons.org/blog/authors/dhruvi16/). I had a blast talking to budding students from DSC-IIT Surat & DSC-RIT.
+- The dark mode (as promised) should be out before my next blog post.
+- Deployed the vocabulary storybook on [Chromatic](https://chromatic.com) and compared & contrasted the pros & cons. Snapshot testing in the near future maybe? 
+- Completed the hacktoberfest challenge. 
+
+### Bonus content
+Not many of you may know this, but this site uses the [Lektor](https://getlektor.com) CMS. I needed to have it installed on my system (windows 10 OS) to run the code in our site repository. 
+Lektor suggests running the following code in powershell as an installation step:
+```powershell
+(new-object net.webclient).DownloadString('https://www.getlektor.com/installer.py') | python
+```
+
+I just didn't think this is a very elegant way. Being an ardent [chocolatey.org](chocolatey.org) fan, I just had to have it up on there! Now the installation step for lektor is simply:
+
+```powershell
+choco install lektor
+```
+on the Windows PowerShell!
+
+Have a look at the package here:
+
+[https://chocolatey.org/packages/lektor](https://chocolatey.org/packages/lektor)
+
+<p align="center">
+    <strong>Thank you for your time! Stay put for the next Vocabulary site update!</strong>
+</p>

content/blog/entries/cc-vocabulary-docs-updates-2/github.png

@@ -0,0 +1,64 @@
+
+title: Vocabulary Site Updates (Part 3/n)
+---
+categories:
+cc-vocabulary
+gsod
+gsod-2020
+---
+author: nimishbongale
+---
+series: gsod-2020-vocabulary-usage-guide
+---
+pub_date: 2020-11-25
+---
+body:
+Excited to know more about this week's vocabulary site updates? Read on to find out!
+
+## Vocabulary Site Updates (Edition 3/many more to come)
+
+### What I've been up to
+
+<center>
+<img alt"Halfway There" src="merged.png"/><br>
+<small class="muted">The surreal feeling...</small>
+</center>
+
+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.   
+- 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](https://opensource.creativecommons.org/blog/authors/zackkrida/) has been kind enough to point and enumerate all of them for me!
+- After receiving a final approval from the engineering team, my PR was finally merged!
+- The final draft of the vocabulary site is live! It will soon be deployed (on [Netlify](https://netlify,com)) and be made available for public viewing.
+- For my readers, here's [exclusive preview](https://cc-vocab-draft.web.app) of the final draft. 
+- I've tried making it as optimised as possible, but if you have any inputs whatsoever feel free to raise issues over on our [GitHub repository](https://github.com/creativecommons/vocabulary). 
+- The famed [Lighthouse report](https://developers.google.com/web/tools/lighthouse) suggests that it's a pretty good start! I've also taken care of the [accessibility aspect](https://www.w3.org/standards/webdesign/accessibility) wherever applicable.
+
+<center>
+<img alt"Halfway There" src="light.png"/><br>
+<small class="muted">Aiming high!</small>
+</center>
+
+### What I've learnt
+
+- GSoD isn't just about documentation; there's some serious amount of coding too!
+- You don't have to sit and write code for hours together. Take breaks, come back, and the fix will strike you sooner than ever.
+- Timelines change; improvisation being an essential aspect of any project!
+- [MDX](https://mdxjs.com/) is a neat little format to code in! Documenting code is just so much easier.
+- Things become obsolete. Versions become outdated. Code maintaining is therefore, easier said than done!
+
+### Other community work tidbits
+
+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!
+- 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!) 
+- 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/).
+
+<p align="center">
+    <strong>Thank you for your time! Stay put for the season finale!</strong>
+</p>

content/blog/entries/cc-vocabulary-docs-updates-2/speed.gif

@@ -0,0 +1,32 @@
+title: Presenting CC Base docs - A WordPress Base Theme Usage Guide for the CC Base Theme
+---
+categories:
+cc-wp-base-theme
+gsod
+gsod-2020
+---
+author: JackieBinya
+---
+series: gsod-2020-wordpress-base-theme-usage-guide
+---
+pub_date: 2020-11-27
+---
+body:
+
+We are live 🎉
+
+The CC Base documentation is live and its available on this [link](https://cc-wp-theme-base.netlify.app/).
+
+The docs were successfully migrated from Google Docs to the site! One of the most notable changes in the theme and consequently reflected in the documentation is the product name change. The CC WP Theme Base has been renamed to CC Base.
+
+But the old adage says good documentation is never complete, we hope to engage the Creative Commons Community and perform usability tests. Any feed back gathered from the usability tests will then be used to further improve the CC Base docs.
+
+
+In future iterations of the docs development we hope to include the following features:
+- Increase the quantity of illustrative media so as to make the docs more intuitive this will be marked by adding video tutorials on how to use certain features of the CC Base theme and also adding illustrative tree diagrams to explain hierarchy of key directories and files in the CC Base project structure.
+- Integration of [Algolia](https://www.algolia.com/) a software tool used to power search functionality in static generated sites. 
+- We also hope to improve SEO for the site.
+
+All the above mentioned improvements are geared at improving the overall user experience of the docs as well as ensure faster onboarding for our community members to get started on using the CC Base theme.
+
+In conclusion I would like to thank all members of the Creative Commons engineering team, with special mention to Hugo Solar and Kriti Godey. Thank you for your guidance and faith in my abilities as a technical writer and software developer.

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

@@ -0,0 +1,39 @@
+title: Finish GSoD Tasks and Explore CC Catalog Documentation
+
+---
+categories:
+cc-catalog
+gsod
+gsod-2020
+open-source
+community
+---
+author: ariessa
+---
+series: gsod-2020-cccatalog-api-usage-guide
+---
+pub_date: 2020-11-20
+---
+body:
+
+Today marks my fifth blog entry on Creative Commons. 
+For week 9 and 10, I explored CC Catalog documentation and began improving the documentation by removing keys and generalizing instructions.
+
+### Week 9
+
+I had completed all GSoD tasks by week 9. 
+So, I took a couple of days off and fixed last week's PR. 
+Kriti assigned me with new tasks, which is to port CC Catalog documentation from the internal wiki into GitHub repository. 
+Brent, the CC Catalog maintainer explained to me about what needs to be done.
+
+### Week 10
+
+For week 10, I started exploring CC Catalog and its documentation. 
+Reminds me a lot about the first and second weeks of GSoD. 
+Trying to understand new stuff and having an "aha" moment when the dots finally connect. 
+I started to move the documentation from the internal wiki to CC Catalog’s GitHub repository. 
+I also wrote and published this blog post.
+
+----
+
+End of blog entry.

content/blog/entries/cc-vocabulary-docs-updates-3/light.png

@@ -0,0 +1,37 @@
+title: Finish Video Presentation, Project Report and Evaluation Form
+
+---
+categories:
+cc-catalog
+gsod
+gsod-2020
+open-source
+community
+---
+author: ariessa
+---
+series: gsod-2020-cccatalog-api-usage-guide
+---
+pub_date: 2020-12-01
+---
+body:
+
+For week 10 and 11, I finished porting CC Catalog documentation, submitted a video presentation, and wrapped up my GSoD 2020 journey.
+
+### Week 11
+
+For Week 11, I finished working on porting CC Catalog documentation from internal wiki to CC Catalog’s GitHub repository.
+Kriti told me that there would be a meeting in which I have to present what I've done for GSoD.
+Since the meeting will take place at 1AM in my local time, Kriti told me that I should send a video presentation instead.
+
+### Week 12 
+
+For this week, I submitted a video presentation to Kriti.
+Finished writing project report and evaluation for GSoD.
+I published 2 blog posts this week.
+One for updates on Week 11 and Week 12.
+Another one is a summary of my GSoD 2020 journey, which also serves as a project report.
+
+----
+
+Signing off.

content/blog/entries/cc-vocabulary-docs-updates-3/merged.png

@@ -53,10 +53,10 @@ It has only been a week so we're just starting, so next task to do sooner are:
 ### How you can help
 
 We are still discussing the new image before start coding so these are some options if you want to get involved:
-- Suggest improvements to designs/UX or new features joining the discussion on the [`#cc-dev-legal-database`](https://creativecommons.slack.com/channels/cc-dev-legal-database) Slack channel or on the [github](https://github.com/creativecommons/caselaw) project.
+- Suggest improvements to designs/UX or new features joining the discussion on the [`#cc-dev-legal-database`](https://creativecommons.slack.com/channels/cc-dev-legal-database) Slack channel or on the [github](https://github.com/creativecommons/legaldb) project.
 - Contribute directly to the CC's Vocabulary design system on [github](https://github.com/creativecommons/vocabulary).
 - Submit a case or a scholarship related to CC licenses on the [current site](https://labs.creativecommons.org/caselaw/contribute/).
 
 **CC Legal Database** is my Outreachy project for this summer, under the guidance of Director of Engineering [Kriti Godey](https://creativecommons.org/author/kriticreativecommons-org/) and Core Systems Manager [Timid Robot Zehta](https://creativecommons.org/author/timidcreativecommons-org/), they are very supportive and the CC community is notable welcoming.
 
-This is the first post of a series so stay tuned if you're interested to know more.
+This is the first post of a series so stay tuned if you're interested to know more.

content/blog/entries/cc-wp-base-theme-docs-launch/contents.lr

@@ -39,7 +39,7 @@ While developing the mentioned functionalities I was also in charge of adding au
     <figcaption>Example of page obtained when requesting a case detail that is not published or doesn't exist.</figcaption>
 </figure>
 
-In this process of adding automated tests I wanted them to run on every pull request created, so I learned how to write a GitHub Action with a PostgreSQL service, the DBMS used in this case. Previously, I had already created a job for linting, so I needed to add another one to run in parallel to save time. This service provided by GitHub is pretty cool and useful, it opens up a world of possibilities, from running third party services like [Lighthouse test](https://github.com/GoogleChrome/lighthouse-ci) to even [send tweets](https://github.com/gr2m/twitter-together)! If you want to see the GitHub Action file configurated for this project, check it out: [`.github/workflows/main.yml`](https://github.com/creativecommons/caselaw/blob/31c3002a7860d78f3fdb464150c5c1b2f8bb86fc/.github/workflows/main.yml).
+In this process of adding automated tests I wanted them to run on every pull request created, so I learned how to write a GitHub Action with a PostgreSQL service, the DBMS used in this case. Previously, I had already created a job for linting, so I needed to add another one to run in parallel to save time. This service provided by GitHub is pretty cool and useful, it opens up a world of possibilities, from running third party services like [Lighthouse test](https://github.com/GoogleChrome/lighthouse-ci) to even [send tweets](https://github.com/gr2m/twitter-together)! If you want to see the GitHub Action file configurated for this project, check it out: [`.github/workflows/main.yml`](https://github.com/creativecommons/legaldb/blob/31c3002a7860d78f3fdb464150c5c1b2f8bb86fc/.github/workflows/main.yml).
 
 ### Accessibility
 
@@ -67,4 +67,4 @@ Some other features were implemented but only relevant to our registered users,
 
 After reviewing all done this last month I see significant progress has been made, I have learned many things along the way: more of what Django and its ecosystem offers, about accessibility, continuous integration in Heroku and GitHub, and more. One of the things that makes me most happy is being able to be contributing and being part of an Open Source organization, knowing how it moves and works inside, something I never imagine before.
 
-Time flies and there are less than two weeks left to finish, so if you want to follow the project here is the repository to suggest improvements or report bugs, or if you prefer something less technical you can join us on the [slack channel](https://creativecommons.slack.com/channels/cc-dev-legal-database).
+Time flies and there are less than two weeks left to finish, so if you want to follow the project here is the repository to suggest improvements or report bugs, or if you prefer something less technical you can join us on the [slack channel](https://creativecommons.slack.com/channels/cc-dev-legal-database).

content/blog/entries/finish-gsod-tasks-and-explore-cc-catalog-documentation/contents.lr

@@ -0,0 +1,34 @@
+title: Restructure README and Add Documentation Guidelines
+
+---
+categories:
+cc-catalog-api
+gsod
+gsod-2020
+open-source
+community
+---
+author: ariessa
+---
+series: gsod-2020-cccatalog-api-usage-guide
+---
+pub_date: 2020-11-5
+---
+body:
+
+This is my fourth blog entry on Creative Commons. 
+For week 7 and 8, I restructured the file README to be more digestible to new users and created Documentation Guidelines for CC Catalog API documentation.
+
+### Week 7
+For this week, I restructured the file README in CC Catalog API repository. 
+I added a step by step guide on how to run the server locally. 
+I hope new users will be less intimidated to contribute to this project with the updated guide on how to run the server locally. 
+
+### Week 8
+
+For week 8, I created Documentation Guidelines which provides steps on how to contribute to CC Catalog API documentation, documentation styles, and cheat sheet for drf-yasg. 
+I also wrote and published this blog post.
+
+----
+
+Finis.