Merge branch 'master' into blog-post-1

Author: mathemancer

.github/CODEOWNERS

@@ -1,7 +1,7 @@
 # These owners will be the default owners for everything in
 # the repo. Unless a later match takes precedence, they will 
 # be requested for review when someone opens a pull request.
-* @creativecommons/internal-tech
+* @creativecommons/internal-tech @creativecommons/ct-cc-open-source-core-committers 
 
 # These users own any files in the specified directory and 
 # any of its subdirectories.

content/blog/authors/makkoncept/contents.lr

@@ -5,6 +5,5 @@ name: Mayank Nader
 md5_hashed_email: 295aeb4b22aac290b7a5c29fdeb31107
 ---
 about:
-Mayank Nader is a sophomore Computer Science student from India. Currently, his main area of interest is Python scripting, JavaScript development, backend, and API development. He also likes to experiment with bash scripting and ricing and configuring my Linux setup. Apart from that, he likes listening to music and watching movies, documentaries, and tv shows. He is very much inspired by Open Source and tries to contribute whenever he can.
+Mayank Nader is a junior computer science student from India. His main area of interest is Python scripting, JavaScript development, Data-Structure and Algorithm design. He likes listening to music and watching movies, documentaries, and TV-shows. He is `@makkoncept` on CC slack.
 
-Mayank is working on [the CC Search browser extension](https://github.com/creativecommons/ccsearch-browser-extension) as part of [Google Summer of Code 2019](/gsoc-2019).

content/blog/categories/design/contents.lr

@@ -0,0 +1 @@
+name: Design

content/blog/entries/cc-browser-extension-upcoming-improvements/contents.lr

@@ -31,7 +31,7 @@ The extension, currently supports only 3 filters: `license`, `sources`, and `use
 #### Related Images and Image tags
 Showing related Images will help users find a variety of images that fit their requirements and also explore the images that would not usally show up on the initial pages of the search result. Whereas, Image tags will let the users incrementally make their queries better and more specific.
 
-#### Adding "Browser by Sources" section
+#### Adding "Browse by Sources" section
 Even though the users can see the number of sources supported by the extension from the drop-down filter, they might not be familiar with many of them and what kind of content they provide. Adding a "Browse by Source" section would make users appreciate the sources available for them to choose from. 
 
 #### Improving the bookmarks section

content/blog/entries/legal-database-design/cc-caselaw-home.png

@@ -0,0 +1,35 @@
+title: CC Legal Database: Design
+---
+categories:
+cc-legal-database
+product
+outreachy
+---
+author: krysal
+---
+series: outreachy-may-2020-legal-database
+---
+pub_date: 2020-06-09
+---
+body:
+Finishing the third week since the project started (for context see this [first post](/blog/entries/legal-database-a-new-beginning/)), so the design phase is almost over and a new site look is out of the oven. The focus on these weeks was to draw the mockups for the user-facing parts of the site, integrating styles of CC Vocabulary and to get the data model for the database.
+
+### Visual Styles
+The intention was to keep the content that is already present but improve its distribution and access by users. For this, the main menu was changed to provide direct links to listing of Cases and Scholarships. The old "Countries" page was removed and replaced by a more granular division by legal resource, so this data will be shown separately.
+
+The final look for the home site is as follows.
+
+<div style="text-align: center;">
+    <figure>
+        <img src="cc-caselaw-home.png" alt="New CC Caselaw Home Mockup" style="border: 1px solid black">
+        <figcaption>New Home page design with Vocabulary.</figcaption>
+    </figure>
+</div>
+
+I made use of as many Vocabulary components as possible, like header, footer and table. This way is easier to keep consistency between CC products and to develop the frontend part of the site because those components are already built and tested, though some will require certain modifications (e.g. card link with a search input), and some others have to be created from scratch, like a pagination component that is actually now required for two sites.
+
+### Data Model
+
+The second main task I worked on was coding the models on Django, which is in charge of creating the database schema through migrations. For this, I had to review the sources of information (CSV files, sheets, forms) and how they are used. The key point here is to keep constant communication with staff who are more involved in the *business case*.
+
+Several iterations were required for each task as well as some researching, and while the engineering and design work never seems to end, this makes good foundations to continue and advance.

content/blog/entries/legal-database-design/contents.lr

@@ -0,0 +1,44 @@
+title: Resource Gathering
+---
+categories:
+outreachy
+design
+open-source
+---
+author: dhruvi16
+---
+series: ux-design-cycle
+---
+pub_date: 2020-06-09
+---
+body:
+
+
+<div style="text-align: center;">
+  <figure>
+    <img src="cover.jpeg"/>
+    <figcaption>
+      <em>
+        Photo by <a href="https://unsplash.com/@dandimmock?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Dan Dimmock</a>
+      </em>
+    </figcaption>
+  </figure>
+</div>
+
+I will be describing the UX design cycle with a series of articles and this article is about describing the first step of the design cycle which is Resource Gathering.
+
+As an outreachy intern, I am handling the integration of [Creative Commons](https://creativecommons.org/) design library — [Vocabulary](https://cc-vocabulary.netlify.app/) with one of our web products — [CC OS](https://opensource.creativecommons.org/). I have been working the design library for 3–4 months now and I have enjoyed the experience the library caters and I am trying to achieve the same experience in the Open source website. To understand UX in-depth, I have been reading different resources and document this knowledge through this series of blogs. This in-depth information will help me achieve the desired experience through the library.
+
+The core concept of user experience design is that users use interfaces to accomplish a task. User experience design starts with the user and by user, I mean the individual that is using some technology to accomplish some goal.
+
+The interface consists of an input and output through which the user interacts with the system. For instance, clicking a photo requires the user to press the button (input) and an image is the desired output. Creating an affordable and usable interface is the main goal of this process. Design is a data-driven process and resource gathering is all about gathering this data.
+
+The resource gathering process is about figuring out how the task is currently accomplished by the user. There are 4 ways to gather data and below I will describe them all in detail. There are two types of data — Quantitative (numeric) and Qualitative (thematic) and designers prefer to use both types of data as per requirement.
+
+1. **Naturalistic observation** - The goal of naturalistic observation is to watch the user in action in their environment. Rather than asking the user what, when, and where accomplishes a given task, the designer goes out to where the task takes place and observes the user. Most naturalistic observations take place in the field rather than the lab because we want to get a sense of the environment where the task takes place. During the naturalistic observation session, the data collected can be either qualitative or quantitative. Qualitative data may be a set of notes written by the designer when observes the user. Quantitative data may be collected during a naturalistic observation session as well.
+
+2. **Surveys** - A survey it's a quite simply a set of questions. The goal of surveys is to get the user’s opinions. Most often, we get them to provide a self-report about their behavior, perceptions, attitudes, and feelings. We can also get their opinion about someone else. It can take place in the field or the lab. Surveys require little direct interaction, it may be physical where someone hands you a sheet of paper, but now it’s more common to have them be completely digital. Either you step up to a kiosk, or one opens up automatically when you browse a website.
+
+3. **Focus Groups** - The goal of conducting a focus group is to engage users in direct conversations. Focus groups take place in a controlled environment, usually a room where users can feel free to share and discuss information in a private setting. It involves users in a high degree of interaction, more than a survey, but less than an interview. A focus group allows the design team to meet with a group of five to ten users. This group should be representative of the user group that the designers want to address. The design team includes a trained moderator who organizes the topics of conversation among the users. A note-taker who keeps track of the major conversation points between the users and the moderator. And if possible it should also include a media person, who either audiotapes or videotapes the session.
+
+4. **Interview** - The goal of an interview is to gather in-depth information from a user. An interview can take place either in the field or in the lab. The one requirement is that there is enough privacy that the user can freely answer the questions being asked. The interview offers the designer an opportunity to have a conversation with the user. This is valuable because the interviewer can then follow any interesting lead the user can have. During the interview session, the data collected will mostly be qualitative.

content/blog/entries/resource-gathering/contents.lr

@@ -0,0 +1 @@
+name: UX Design Cycle

content/blog/entries/resource-gathering/cover.jpeg

@@ -82,6 +82,10 @@ The channels most relevant to CC's developer community are:
       <td><code>#cc-usability</code</td>
       <td>General usability discussions, seeking feedback on new releases of CC products from the community.</td>
     </tr>
+    <tr>
+      <td><code>#cc-dev-licenses</code</td>
+      <td>Discussion of the <a href="https://github.com/creativecommons/cc-licenses">CC license infrastructure overhaul project</a>.</td>
+    </tr>
   </tbody>
 </table>