Skip to content

Commit d8fc80a

Browse files
committed
add blog
1 parent 2cd8e85 commit d8fc80a

File tree

1 file changed

+33
-0
lines changed
  • content/blog/entries/integartion-vocabulary-ccos

1 file changed

+33
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
title: Integration of Vocabulary with CCOS.
2+
---
3+
categories:
4+
outreachy
5+
tech
6+
open-source
7+
---
8+
author: dhruvi16
9+
---
10+
pub_date: 2020-07-08
11+
---
12+
body:
13+
14+
15+
This blog demonstrates the project I am working on during the course of my Outreachy internship. My project involves redesigning and reimplementing one of the web products of the CC network using our new cohesive design library — [Vocabulary](https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-introduction--page). After completion of my internship, the [Creative Commons Open Source](https://opensource.creativecommons.org/) website will have a completely different looking interface that will extensively use Vocabulary components.
16+
17+
## The Problem -
18+
19+
There exists a large variety of web products across the Creative Commons network. These products serve different purposes for the network and so do they vary in the way of presenting the existing content. So, to conquer the inconsistency across the different products we have our coherent design system called Vocabulary.
20+
21+
If we come to the current CC Open Source website, it is quite off-track considering our new design system Vocabulary. The styles and components of the website are not well aligned with the components of the Vocabulary. And thus it lacks harmony and consistency concerning the brand.
22+
23+
The purpose of a design system gets dissolved if it is not well incorporated with the products and we do have this problem with the CC Open Source website. Hence, there was a need for a redesign of CCOS as per the new Design Library. This project aims to rectify the problems and inconsistencies of the CCOS website and build a completely new website (as per Vocabulary).
24+
25+
## The Solution -
26+
27+
I started with trying out different mock-ups for the new website in Figma. You can see what I tried to make [here](https://www.figma.com/file/ka3zs1iYnqJvyLnvAV3cW7/Home-proposals). And then with the help of our UX designer Francisco, we created all the mock-ups and finalized how the website will look in a couple of weeks, here the [link](https://www.figma.com/file/mttcugI1UxvCJRKE5sdpbO/Mockups?node-id=759%3A516) for that.
28+
29+
I started my internship with going through the website’s tech stack, the website is made using Lektor, with which I was not very familiar. I read the official docs went through projects, tried making demo projects, and took help from mentors wherever I got stuck.
30+
31+
To keep the project clean I added a theme that only has templates for the project and alters no content (as per aim). While updating templates, some components were not available in the Vocabulary yet, so I worked on adding those components to the library. And then used them in my new templates. You can see the ongoing work [here](https://cc-open-source-dev.netlify.app/).
32+
33+
I have thoroughly enjoyed contributing to this project as I got to learn so much. And I am excited for what’s next to come in the coming weeks.

0 commit comments

Comments
 (0)