Merge branch 'master' into write-post-format

Author: hugosolar

content/blog/authors/obulat/contents.lr

@@ -0,0 +1,10 @@
+username: obulat
+---
+name: Olga Bulat
+---
+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).

content/blog/categories/cc-chooser/contents.lr

@@ -0,0 +1 @@
+name: cc-chooser

content/blog/entries/cc-browser-extension-a-gsoc-project/contents.lr

@@ -10,6 +10,8 @@ open-source
 ---
 author: makkoncept
 ---
+series: gsoc-2019-browser-extension
+---
 pub_date: 2019-06-20
 ---
 body:

content/blog/entries/cc-browser-extension-week5-6/contents.lr

@@ -8,6 +8,8 @@ open-source
 ---
 author: makkoncept
 ---
+series: gsoc-2019-browser-extension
+---
 pub_date: 2019-07-04
 ---
 body:

content/blog/entries/cc-browser-extension-week7-8/contents.lr

@@ -8,6 +8,8 @@ open-source
 ---
 author: makkoncept
 ---
+series: gsoc-2019-browser-extension
+---
 pub_date: 2019-07-19
 ---
 body:

content/blog/entries/cc-browser-extension-week9-10/contents.lr

@@ -1,39 +1,42 @@
-title: CC Browser Extension Week 9, 10
----
-categories:
-gsoc
-gsoc-2019
-cc-browser-extension
-open-source
----
-author: makkoncept
----
-pub_date: 2019-08-12
----
-body:
-
-For the context, I am working on my GSoC project that is to make a browser-extension to search CC Licensed content in the public domain by interacting with CC Catalog API.
-
-**Previous Blogs**:
--  [CC Browser Extension - A GSoC Project](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-a-gsoc-project/)
--  [CC Browser Extension Week 5, 6](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-week5-6/)
--  [CC Browser Extension Week 7, 8](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-week7-8/)
-
-### Work Done
-These weeks were spent on adding bookmarking feature to the extension and writing some unit tests.
-
-On clicking the bookmark icon, that appears when the image thumbnail is hovered on, the image will be bookmarked. Under the hood, the unique image identifier is saved in the local storage of the extension. The images ids are enough to get all the required image and attribution data needed using the `/image/{identifier}` endpoint of [CC Catalog API]([https://github.com/creativecommons/cccatalog-api](https://github.com/creativecommons/cccatalog-api).
-
-Bookmarked images persist even when the extension session terminates. User can view, inspect, delete the bookmarked images in the _'Bookmarks'_ section. There is also a button to delete all the bookmarks at once. 
-
-To let the users organize and share bookmarks, importing and exporting feature is also added. The buttons to export and import the bookmarks are in the options page. Simple `json` files are used for this feature.
-
-The rest of the time was spent on writing tests for the extension. One positive side-effect of this was cleaner and modular code. Finally, the CircleCi config file was modified to let the tests to run in CI pipeline.
-### Coming Up
-- Write more tests.
-- Test and fix bugs.
-- Modifying webpack config to spit out code for production.
-
-You can check out the project on [Github](https://github.com/creativecommons/ccsearch-browser-extension) and join the discussion on `#gsoc-browser-ext` channel on [slack](https://opensource.creativecommons.org/community/#slack).
-
-*Special Thanks*:  [Alden](https://creativecommons.org/author/aldencreativecommons-org/), [Timid](https://creativecommons.org/author/timidcreativecommons-org/) and [Kriti](https://creativecommons.org/author/kriticreativecommons-org/).
+title: CC Browser Extension Week 9, 10
+---
+categories:
+
+gsoc
+gsoc-2019
+cc-browser-extension
+open-source
+---
+author: makkoncept
+---
+series: gsoc-2019-browser-extension
+---
+pub_date: 2019-08-12
+---
+body:
+
+For the context, I am working on my GSoC project that is to make a browser-extension to search CC Licensed content in the public domain by interacting with CC Catalog API.
+
+**Previous Blogs**:
+-  [CC Browser Extension - A GSoC Project](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-a-gsoc-project/)
+-  [CC Browser Extension Week 5, 6](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-week5-6/)
+-  [CC Browser Extension Week 7, 8](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-week7-8/)
+
+### Work Done
+These weeks were spent on adding bookmarking feature to the extension and writing some unit tests.
+
+On clicking the bookmark icon, that appears when the image thumbnail is hovered on, the image will be bookmarked. Under the hood, the unique image identifier is saved in the local storage of the extension. The images ids are enough to get all the required image and attribution data needed using the `/image/{identifier}` endpoint of [CC Catalog API]([https://github.com/creativecommons/cccatalog-api](https://github.com/creativecommons/cccatalog-api).
+
+Bookmarked images persist even when the extension session terminates. User can view, inspect, delete the bookmarked images in the _'Bookmarks'_ section. There is also a button to delete all the bookmarks at once. 
+
+To let the users organize and share bookmarks, importing and exporting feature is also added. The buttons to export and import the bookmarks are in the options page. Simple `json` files are used for this feature.
+
+The rest of the time was spent on writing tests for the extension. One positive side-effect of this was cleaner and modular code. Finally, the CircleCi config file was modified to let the tests to run in CI pipeline.
+### Coming Up
+- Write more tests.
+- Test and fix bugs.
+- Modifying webpack config to spit out code for production.
+
+You can check out the project on [Github](https://github.com/creativecommons/ccsearch-browser-extension) and join the discussion on `#gsoc-browser-ext` channel on [slack](https://opensource.creativecommons.org/community/#slack).
+
+*Special Thanks*:  [Alden](https://creativecommons.org/author/aldencreativecommons-org/), [Timid](https://creativecommons.org/author/timidcreativecommons-org/) and [Kriti](https://creativecommons.org/author/kriticreativecommons-org/).

content/blog/entries/cc-chooser-lastweek/contents.lr

@@ -3,8 +3,11 @@
  categories:
  gsoc
  gsoc-2019
+ cc-chooser
 ---
  author: akmadian
+---
+series: gsoc-2019-chooser
 ---
  pub_date: 2019-08-22
 ---

content/blog/entries/cc-chooser-week2/contents.lr

@@ -3,8 +3,11 @@
  categories:
  gsoc
  gsoc-2019
+ cc-chooser
 ---
  author: akmadian
+---
+series: gsoc-2019-chooser
 ---
  pub_date: 2019-06-14
 ---

content/blog/entries/cc-chooser-week4/contents.lr

@@ -3,8 +3,11 @@
  categories:
  gsoc
  gsoc-2019
+ cc-chooser
 ---
  author: akmadian
+---
+series: gsoc-2019-chooser
 ---
  pub_date: 2019-06-24
 ---

content/blog/entries/cc-datacatalog-data-processing-2/contents.lr

@@ -10,6 +10,8 @@ open-source
 ---
 author: soccerdroid
 ---
+series: gsoc-2019-dataviz
+---
 pub_date: 2019-07-26 
 ---
 body:

content/blog/entries/cc-datacatalog-data-processing-3/contents.lr

@@ -10,6 +10,8 @@ open-source
 ---
 author: soccerdroid
 ---
+series: gsoc-2019-dataviz
+---
 pub_date: 2019-08-12 
 ---
 body:

content/blog/entries/cc-datacatalog-data-processing/contents.lr

@@ -10,6 +10,8 @@ open-source
 ---
 author: soccerdroid
 ---
+series: gsoc-2019-dataviz
+---
 pub_date: 2019-07-10
 ---
 body:

content/blog/entries/cc-datacatalog-data-thelinkedcommons/contents.lr

@@ -10,6 +10,8 @@ open-source
 ---
 author: soccerdroid
 ---
+series: gsoc-2019-dataviz
+---
 pub_date: 2019-09-03 
 ---
 body:

content/blog/entries/cc-datacatalog-visualization/contents.lr

@@ -10,6 +10,8 @@ open-source
 ---
 author: soccerdroid
 ---
+series: gsoc-2019-dataviz
+---
 pub_date: 2019-06-17
 ---
 body:

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

@@ -0,0 +1,21 @@
+title: CC Platform Toolkit Revamp - 2
+---
+categories:
+community
+platform-toolkit
+outreachy
+---
+author: apdsrocha
+---
+series: outreachy-dec-2019-platform-toolkit
+---
+pub_date: 2020-01-06
+---
+body:
+Time is really flying! I can hardly believe this is already week 5 as of my internship with CC (I'm part of the Outreachy program for the 2019-2020 round). I've been having a wonderful time working on this project (I'm helping revamp the [Platform Toolkit](https://creativecommons.org/platform/toolkit/)) and I'm excited to report on what's been going on for the past couple of weeks.
+
+Since the holidays got a bit in the way of user testing existing platform implementations, my mentors and I slightly altered the schedule. These past weeks have been dedicated to reworking the content that is currently online (revisiting writing and format) and suggesting an entirely new structure. I've been documenting that process [here](https://drive.google.com/open?id=1g7_76zFmgtqq7khb_aBS-l2Wx8tScMgR1NPBO0vOdkM) as I tackle each section.
+
+What I really loved about this process is the fact that I'm able to see the platform toolkit through a holistic lens: I'm thinking about how the user is currently interacting with this content, how the information could be made more palatable, how that can be achieved visually, and finally, how to do it in a way that won't be impossible to implement. 
+
+I'm excited about the questions and answers that have been coming up during this process. Even though I'm far from delivering a final version, I believe this first rough draft already brings important improvements. My focus has been on diminishing cognitive load. That means taking very dense content and delivering the same amount of information with an approach that steps away from full copy and comes closer to a UI format. I've been learning a lot with each step of this project and I'm eager to make a positive contribution by the end of the internship. Soon enough I'll be checking in again soon to give a new follow up!

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

@@ -7,6 +7,8 @@ outreachy
 ---
 author: apdsrocha
 ---
+series: outreachy-dec-2019-platform-toolkit
+---
 pub_date: 2019-12-16
 ---
 body:

content/blog/entries/cc-vocabulary-new-design-system/contents.lr

@@ -9,6 +9,8 @@ gsoc-2019
 ---
 author: dhruvkb
 ---
+series: gsoc-2019-vocabulary
+---
 pub_date: 2019-06-15
 ---
 body:

content/blog/entries/cc-vocabulary-so-far/contents.lr

@@ -9,6 +9,8 @@ gsoc-2019
 ---
 author: dhruvkb
 ---
+series: gsoc-2019-vocabulary
+---
 pub_date: 2019-07-05
 ---
 body:

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

@@ -9,6 +9,8 @@ gsoc-2019
 ---
 author: dhruvkb
 ---
+series: gsoc-2019-vocabulary
+---
 pub_date: 2019-07-19
 ---
 body:

content/blog/entries/cc-wp-plugin-final-phase/contents.lr

@@ -9,6 +9,8 @@ wordpress
 ---
 author: ahmadbilaldev
 ---
+series: gsoc-2019-wp-plugin
+---
 pub_date: 2019-08-23
 ---
 body:

content/blog/entries/cc-wp-plugin-first-phase/contents.lr

@@ -8,6 +8,8 @@ wordpress
 ---
 author: ahmadbilaldev
 ---
+series: gsoc-2019-wp-plugin
+---
 pub_date: 2019-06-20
 ---
 body:

content/blog/entries/cc-wp-plugin-second-phase/contents.lr

@@ -9,6 +9,8 @@ wordpress
 ---
 author: ahmadbilaldev
 ---
+series: gsoc-2019-wp-plugin
+---
 pub_date: 2019-07-20
 ---
 body:

content/blog/entries/improving-cc-license-chooser-weeks-1-2-design/contents.lr

@@ -0,0 +1,76 @@
+title: Improving CC License Chooser Weeks 1-2: Design
+---
+author: obulat
+---
+categories:
+
+outreachy
+cc-chooser
+---
+series: outreachy-dec-2019-chooser
+---
+pub_date: 2020-01-06
+---
+body:
+Creative Commons License Chooser has been helping creators to choose the most appropriate license for their work for a long time. As anything on the web, it needs updating. One of my mentors, [Ari Madian](https://opensource.creativecommons.org/blog/authors/akmadian/), has created the new version of this chooser as part of his 2019 GSoC Project. As a 2019-2020 Outreachy intern, I will be working on making it production-ready. The goals of my internship include:
+
+- Improving usability of the Chooser and making it easier for licensors to understand the process of selecting the most appropriate license.
+- Setting up and automating internalization.
+- Extracting License Chooser as a standalone npm package to make integrating Creative Commons licensing in other websites easier.
+
+During the first two weeks of my internship I mainly worked on redesigning the license selection process based on the usability testing feedback. We decided to set up license selection as a step-by-step process of answering yes/no questions guiding a novice or somewhat experienced user to the CC license that best suits their needs.
+
+----
+
+### **Here is the first draft:**
+
+![draft-1.png](draft-1.png)
+
+*Features of this draft that stayed in current version:*
+- A card to show the information about currently selected license is prominent on the page.
+- Four yes/no questions that help narrow the license choice.
+
+*What was changed in final version:*
+- The openness scale (which is drawn incorrectly, by the way) took up too much space on the first screen, not adding as much to the process.
+- Toggles as an answer to yes/no questions are confusing for some users.
+- Separate Personalization step was moved together with other steps.
+- License attribution information was merged with the selected license card, because the card is supposed to contain all the information about selected license, including author/work url/ source url, if they are available.
+
+----
+
+### **Draft 2**
+
+As a result of continuous communication with my mentors, I this draft to be discussed at our weekly meeting.
+
+![draft-2.png](draft-2.png)
+
+*Features that stayed in the current version:*
+- Two cards: one for the step-by-step process and the other for presenting license information.
+- All the information about selected license in the second card.
+- Personalization step as the last and optional step of choosing the license.
+
+*Features that were suggested during the meeting:*
+- License selection dropdown with all available licenses on the selected license card. This is for experienced users who know what license they want to choose and only need to add details, or copy the attribution text or html.
+- A link to a page with more information on how to use the license when sharing on the selected license card: for users who need help with that.
+----
+
+### **Currently Final Draft :)**
+
+![draft-3.png](draft-3.png)
+
+#### **License Chooser Stepper Card**
+
+- Stepper Card shows five steps to selecting a license, one for each feature of CC licenses and an optional personalization step. The stepper icons show current selection status: selected/unselected features and current feature being displayed. Clicking on an icon opens the corresponding step.
+- Each license feature has a yes/no question. A user clicks on a yes or no button to answer, and can immediately see what changed in the license, and the text beneath the buttons shows what current selection of the feature actually means. Default answer for each step besides the first one (attribution - 'BY') is 'no', so if a user simply clicks 'next' on each step, or clicks on the last step icon at the top, they get CC BY 4.0 license.
+
+#### **Selected License Card**
+
+- Current selection dropdown is for experienced users who can quickly select a license that they know they want to use. It also updates when a feature in the license selection process is changed.
+- Selected license information displays information about the license and its clauses, as well as its icons. The wording of this part will probably change the most after discussion with the community and legal team.
+- Attribution information for the license, with a choice between rich text or html code. These are displayed in tabs to save on space. 
+
+I created the wireframes in Figma, and I tried to integrate CC Vocabulary elements as much as possible.
+
+Next steps for my project will include coding to update the license chooser Vue.js project, and iterating over the design based on community feedback.
+
+You can follow my work at [https://github.com/creativecommons/cc-chooser](https://github.com/creativecommons/cc-chooser).

content/blog/entries/improving-cc-license-chooser-weeks-1-2-design/draft-1.png

@@ -10,6 +10,8 @@ product
 ---
 author: makkoncept
 ---
+series: gsoc-2019-browser-extension
+---
 pub_date: 2019-09-03
 ---
 body:

content/blog/entries/improving-cc-license-chooser-weeks-1-2-design/draft-2.png

@@ -9,6 +9,8 @@ gsoc-2019
 ---
 author: dhruvkb
 ---
+series: gsoc-2019-vocabulary
+---
 pub_date: 2019-08-19
 ---
 body:

content/blog/entries/improving-cc-license-chooser-weeks-1-2-design/draft-3.png

@@ -0,0 +1 @@
+name: GSoC 2019: CC Search Browser Extension

content/blog/entries/introducing-cc-search-extension/contents.lr

@@ -0,0 +1 @@
+name: GSoC 2019: Human Centered Education of CC Licenses

content/blog/entries/vocabulary-so-long/contents.lr

@@ -0,0 +1 @@
+name: GSoC 2019: The Linked Commons

content/blog/series/gsoc-2019-browser-extension/contents.lr

@@ -0,0 +1 @@
+name: GSoC 2019: CC Vocabulary

content/blog/series/gsoc-2019-chooser/contents.lr

@@ -0,0 +1 @@
+name: GSoC 2019: CC WordPress Plugin

content/blog/series/gsoc-2019-dataviz/contents.lr

@@ -0,0 +1 @@
+name: Outreachy Dec 2019 round: CC License Chooser

content/blog/series/gsoc-2019-vocabulary/contents.lr

@@ -0,0 +1 @@
+name: Outreachy Dec 2019 round: Platform Toolkit