Merge branch 'master' into srinidhi-blogpost2

Author: kgodey

content/archives/contents.lr

@@ -6,4 +6,4 @@ body:
 
 This section contains archives related to older CC projects.
 
-* [CC Tech Blog (2007-2014)](/archives/old-tech-blog/entries)
+* [CC Tech Blog (2007-2014)](/archives/old-tech-blog/entries/)

content/blog/authors/ahmadbilaldev/contents.lr

@@ -7,4 +7,4 @@ md5_hashed_email: 870502bc55d77d77522ad3f27876b511
 about:
 Ahmad Bilal is a Computer Science undergrad from UET Lahore, who likes computers, problems and using the former to solve the later. He is always excited about Open Source, and is currently focused on Node.js, Serverless, GraphQL, Cloud, Gatsby.js with React.js and WordPress. He likes organizing meetups, conferences and meeting new people. Cats are his weakness, and he is a sucker for well-engineered cars.
 
-Ahmad is working on [the CC WordPress plugin](https://github.com/creativecommons/creativecommons-wordpress-plugin) as part of [Google Summer of Code 2019](/gsoc-2019).
+Ahmad is working on [the CC WordPress plugin](https://github.com/creativecommons/creativecommons-wordpress-plugin) as part of [Google Summer of Code 2019](/gsoc-2019/).

content/blog/authors/conye/contents.lr

@@ -7,4 +7,4 @@ md5_hashed_email: 9088efad6d512ef79556a3b6adcf048f
 about:
 Chidiebere Onyegbuchulem is a Frontend developer based in Lagos, Nigeria.
 
-Chidi is currently working on [CC Vocabulary](https://github.com/creativecommons/cc-vocabulary) as part of 2019-2020 [Outreachy Internship](/programs/outreachy/2019-12-start).
+Chidi is currently working on [CC Vocabulary](https://github.com/creativecommons/cc-vocabulary) as part of 2019-2020 [Outreachy Internship](/programs/outreachy/2019-12-start/).

content/blog/authors/dhruvkb/contents.lr

@@ -7,4 +7,4 @@ md5_hashed_email: 0eab64adad056cff2492e7c407a9aa21
 about:
 Dhruv Bhanushali is a Mumbai-based software developer and an Engineering-Physics graduate from IIT Roorkee. He started programming as a hobby in high-school and having found his calling, is now pursuing a career in the field. He is a huge fan of alternative and post-rock music and keeps his curated collection with him at all times. He also loves to binge watch TV shows and movies, especially indie art films.
 
-Dhruv developed [CC Vocabulary](https://opensource.creativecommons.org/cc-vocabulary/) as part of [Google Summer of Code 2019](/gsoc-2019) and now is a maintainer for the project. He is consistently [`@dhruvkb`](https://dhruvkb.github.io/) everywhere.
+Dhruv developed [CC Vocabulary](https://opensource.creativecommons.org/cc-vocabulary/) as part of [Google Summer of Code 2019](/gsoc-2019/) and now is a maintainer for the project. He is consistently [`@dhruvkb`](https://dhruvkb.github.io/) everywhere.

content/blog/authors/obulat/contents.lr

@@ -7,4 +7,4 @@ md5_hashed_email: acd34b5434369aeaf31de8ea94368bf0
 about:
 [Olga](https://creativecommons.org/author/obulat/) is a developer based in Istanbul, Turkey. She loves programming in Python and Javascript. Her main areas of interest are web development, Natural Language Processing, languages, geography and education. Apart from that, she is busy raising her (soon to be) three kids.
 
-Olga is currently working on improving [the CC License Chooser](https://github.com/creativecommons/cc-chooser) as part of 2019-2020 [Outreachy Internship](/programs/outreachy).
+Olga is currently working on improving [the CC License Chooser](https://github.com/creativecommons/cc-chooser) as part of 2019-2020 [Outreachy Internship](/programs/outreachy/).

content/blog/authors/soccerdroid/contents.lr

@@ -7,4 +7,4 @@ md5_hashed_email: a177edcce952c2c82ac8716a4586a28f
 about:
 Maria is a Bachelor of Computer Science from Ecuador. As a research assistant, she worked in projects including computer vision, the estimation of socio-economic indexes through CDRs analysis, and a machine learning model with sensors data. During her spare time, she likes to watch animes and read. She loves sports, especially soccer. She is also committed to environmental causes, and she is a huge fan of cats and dogs (she has 4 and 1 respectively).
 
-Maria worked in the [data visualizations of the CC Catalog](https://github.com/creativecommons/cccatalog-dataviz) as part of [Google Summer of Code 2019](/gsoc-2019), and is currently a mentor in this year's edition of the program.
+Maria worked in the [data visualizations of the CC Catalog](https://github.com/creativecommons/cccatalog-dataviz) as part of [Google Summer of Code 2019](/gsoc-2019/), and is currently a mentor in this year's edition of the program.

content/blog/authors/subhamX/contents.lr

@@ -5,4 +5,4 @@ name: Subham Sahu
 md5_hashed_email: 1ca2562f3046509e3273fe5afd3fdab2
 ---
 about:
-Subham Sahu is an undergraduate student from Indian Institute Of Technology, Ropar. He is currently working on the [Linked Commons](https://github.com/creativecommons/cccatalog-dataviz) as part of [Google Summer of Code 2020](/gsoc-2020).
+Subham Sahu is an undergraduate student from Indian Institute Of Technology, Ropar. He is currently working on the [Linked Commons](https://github.com/creativecommons/cccatalog-dataviz) as part of [Google Summer of Code 2020](/gsoc-2020/).

content/blog/entries/cc-vocabulary-the-main-course/contents.lr

@@ -85,7 +85,7 @@ brainchild comes of age.
 There are a number of components under construction right now such as cards and social media buttons. They will be
 published on the styleguide very soon. After these, the final month, phase III of of the project's GSoC term will be
 spent continuously polishing the project to suit the needs of all CC apps as discovered during the integration with
-CC Search as mentioned by [Breno Ferreira](/blog/authors/brenoferreira) in the 'Next steps' in his post on
+CC Search as mentioned by [Breno Ferreira](/blog/authors/brenoferreira/) in the 'Next steps' in his post on
 [CC Search Redesign](/blog/entries/cc-search-redesign/).
 
 In keeping with the culinary theme of this post, think of it as sweet sweet dessert.

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

@@ -54,4 +54,4 @@ Before this internship, I had just switched careers from Network engineering to
 
 I will continue to contribute to CC open source projects especially to the Vocabulary project that I have become a part of. I would love to see the application of Vocabulary to the development of other CC platforms and applications.  I also want to apply the skills that I have acquired to get a full-time software developer position.
 
-My special appreciation to Outreachy for this opportunity, the entire CC team especially those I worked with, My mentors [Hugo Solar](/blog/authors/hugosolar) and [Dhruv Bhanushali](/blog/authors/dhruvkb) for their guidance, direction, and help whenever I got stuck, also to the Director of Engineering [Kriti Godey](/blog/authors/kgodey) for always checking up on me ensuring I had a wonderful internship experience.
+My special appreciation to Outreachy for this opportunity, the entire CC team especially those I worked with, My mentors [Hugo Solar](/blog/authors/hugosolar/) and [Dhruv Bhanushali](/blog/authors/dhruvkb/) for their guidance, direction, and help whenever I got stuck, also to the Director of Engineering [Kriti Godey](/blog/authors/kgodey/) for always checking up on me ensuring I had a wonderful internship experience.

content/blog/entries/what-is-up-ccos/contents.lr

@@ -0,0 +1,35 @@
+title: What is up? - CCOS Revamp
+---
+categories:
+outreachy
+tech
+open-source
+---
+author: dhruvi16
+---
+series: outreachy-2020-CCOS
+---
+pub_date: 2020-07-20
+---
+body:
+
+
+In my previous blog, I demonstrated what my Outreachy project was about. Here I will talk about my progress in the past 7 weeks.
+
+### The Set-Up -
+
+The [Creative Commons Open Source](https://opensource.creativecommons.org/) website is built using [Lektor](https://www.getlektor.com/). I was not very familiar with it, so I started by going through the documentation and the official website code. I learned how awesome it is and can also be used by non-coders. I got familiar with the [jinja templates](https://palletsprojects.com/p/jinja/) and working of themes in a Lektor app. For integrating new styles from Vocabulary, I replaced `templates/` folder with a `theme/` folder. Here is the link to how [templates](https://www.getlektor.com/docs/templates/) work in Lektor.
+
+As the revamping process is gradual, there was a need of setting up a staging environment where we could test the website. Deploying the branch that consists of the ongoing changes was pretty easy, I just followed the official [documentation](https://www.netlify.com/blog/2016/05/25/lektor-on-netlify-a-step-by-step-guide/) provided by Netlify and deployed it.
+
+### Adding New Components to Vocabulary -
+
+The [mock-ups](https://www.figma.com/file/mttcugI1UxvCJRKE5sdpbO/Mockups) for the new CCOS website extensively use Vocabulary components, styles, and patterns, and it had components that were not available in Vocabulary. So, I worked on building them from scratch. I enjoyed this part a bit too much. And also this was a part of the project, I did not think would take up like 2 weeks but it did. I enjoyed questioning the scope, the design, the experience of the components, and getting satisfactory answers. Maintaining the practices, focusing on details were fun things to do. It felt like I own those components. You can check them out [here](https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-introduction--page) and also use them wherever needed.
+
+### Updating Templates of the Theme -
+
+I started by updating the home page template. I try to make the code cleaner and more readable. Going through the [Lektor](https://www.getlektor.com/) documentation, I came across different ways to do so. One of them was [flow blocks]((https://www.getlektor.com/)), I like how it makes a template more modular and readable so I implemented the home page using flow blocks. This one after one, I started updating every template. For now, I have updated 10 templates and I plan to update the remaining in upcoming weeks.
+
+### My Experience so far - 
+
+This has been one heck of a journey for me. I have never collaborated with such a huge open-source organization and so that was something new for me. I have learned a lot of things both technical and non-technical so far. I have become more alert about the code I write, this journey has helped me improve the questions I ask to myself while writing code or thinking about the solution, I got to learn about new technologies such as [Lektor](https://www.getlektor.com/), [Webpack](https://webpack.js.org/), [SCSS](https://sass-lang.com/documentation/syntax) and many more. I am just very glad to be a part of this.

content/community/code-of-conduct/enforcement/contents.lr

@@ -10,7 +10,7 @@ body:
 
 This document provides incident reporting guidelines and an enforcement manual for the following codes of conduct used by Creative Commons:
 
-* [CC Open Source Code of Conduct](/community/code-of-conduct)
+* [CC Open Source Code of Conduct](/community/code-of-conduct/)
 * [Slack/Code of Conduct](https://wiki.creativecommons.org/wiki/Slack/Code_of_Conduct)
 
 ## Reporting Guidelines

content/community/community-team/contents.lr

@@ -29,8 +29,8 @@ Joining [one of our community forums](https://opensource.creativecommons.org/com
 There are two main groups of roles – project roles and community building roles. Project roles are intended for folks interested in contributing to a specific project or codebase. Community building roles are for folks interested in interacting with people and helping grow the community.
 
 Please read more about the roles here:
-* [Project roles](/community/community-team/project-roles)
-* [Community building roles](/community/community-team/community-building-roles)
+* [Project roles](/community/community-team/project-roles/)
+* [Community building roles](/community/community-team/community-building-roles/)
 
 Please note that we do not expect you to do work just because you have a role on the Community Team. Any role you are granted is based on appreciation for the work you’ve _already_ done.
 

content/community/contents.lr

@@ -6,7 +6,7 @@ title: Join the CC Developer Community
 ---
 body:
 
-<p class="lead">Join our Slack or mailing list communities to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time engineering staff. You can also keep up with us on the <a href="/blog">CC Open Source Blog</a> or via <a href="https://twitter.com/cc_opensource">Twitter</a>.</p>
+<p class="lead">Join our Slack or mailing list communities to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time engineering staff. You can also keep up with us on the <a href="/blog/">CC Open Source Blog</a> or via <a href="https://twitter.com/cc_opensource">Twitter</a>.</p>
 
 ## Mailing Lists
 

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

@@ -6,7 +6,7 @@ title: Write a Blog Post
 ---
 body:
 
-<p class="lead">We invite members of the Creative Commons community to write guest posts on <a href="/blog">our technical blog</a>.</p>
+<p class="lead">We invite members of the Creative Commons community to write guest posts on <a href="/blog/">our technical blog</a>.</p>
 
 ## What to write about
 
@@ -18,7 +18,7 @@ You can write about anything that generally intersects with CC and technology. S
 - guides to best practices of working with technologies in the context of a CC-related project
 - *your idea here*
 
-It is a good idea to float what you're going to write about [with the CC tech team](/community) ahead of time so that we can give you feedback before you put in the work of writing it.
+It is a good idea to float what you're going to write about [with the CC tech team](/community/) ahead of time so that we can give you feedback before you put in the work of writing it.
 
 ## Writing tips
 
@@ -35,7 +35,7 @@ If you're writing about a project you're working on, here are a few ways you cou
 
 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 **[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).
 
 1. Each blog entry lives in its own subdirectory of the [content/blog/entries](https://github.com/creativecommons/creativecommons.github.io-source/tree/master/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.

content/contributing-code/contents.lr

@@ -12,7 +12,7 @@ We do all of our development [on GitHub](https://github.com/creativecommons/). I
 
 ## Finding an issue
 
-Here's a list of [all our current projects](/projects). We use GitHub issues associated with each project to track the work associated with that project. That's where you can find things to work on.
+Here's a list of [all our current projects](/projects/). We use GitHub issues associated with each project to track the work associated with that project. That's where you can find things to work on.
 
 We make extensive use of issue labels to desginate the status of various issues. We have a standard set of labels across all projects, [documented here](https://github.com/creativecommons/ccos-scripts/blob/master/normalize_repos/labels.py). Here are some of the ones that are most relevant to finding a good issue to work on:
 
@@ -39,7 +39,7 @@ Once you've found an issue you'd like to work on, please follow these steps to m
 
 1. Comment on it and say you're working on that issue. This is to avoid conflicts with others also working on the issue.
     * A project maintainer may mark the issue with an `in progress` label at this point, but we don't always get around to that.
-2. Write your code and submit your pull request. Be sure to read and follow our **[pull request guidelines](/contributing-code/pr-guidelines)**!
+2. Write your code and submit your pull request. Be sure to read and follow our **[pull request guidelines](/contributing-code/pr-guidelines/)**!
 3. Wait for code review and address any issues raised as soon as you can.
 
 **A note on collaboration:** We encourage people to collaborate as much as possible. We especially appreciate contributors reviewing each others pull requests, as long as you are [kind and constructive](https://medium.com/@otarutunde/comments-during-code-reviews-2cb7791e1ac7) when you do so.
@@ -53,4 +53,4 @@ If you want to work on something that there is no GitHub issue for, follow these
 2. The issue will automatically have the `not ready for work` label applied. Wait for a project maintainer to evaluate your issue and decide whether it's something that we will accept a pull request for.
 3. Once the project maintainer has approved the issue and removed the `not ready for work` label, you may start work on code as described in the "Contribution process" section above.
 
-When in doubt, ask a question on [one of our community forums](/community).
+When in doubt, ask a question on [one of our community forums](/community/).

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

@@ -64,6 +64,6 @@ Each repo should have a `.cc-metadata.yml` file in the root directory with the f
   </code>
 </pre>
 
-This metadata file is used in the [Projects](/projects) page. Repos that are marked as non-engineering projects are not displayed in the page and repos marked as featured as displayed at the top of the page. Repos should be marked as featured if we are actively looking for community contributions and have the bandwidth to review them quickly.
+This metadata file is used in the [Projects](/projects/) page. Repos that are marked as non-engineering projects are not displayed in the page and repos marked as featured as displayed at the top of the page. Repos should be marked as featured if we are actively looking for community contributions and have the bandwidth to review them quickly.
 
 Repos without this metadata file are treated as `engineering_projects: true`, `featured: false` and `slack: ""`. A default is necessary since it will take time for us to clean up and add metadata to all our repos.