Skip to content

Commit 000f4c8

Browse files
authored
Merge pull request creativecommons#338 from Dhruvi16/add_blog_2
2 parents ad7c98a + 2b7b46c commit 000f4c8

File tree

1 file changed

+35
-0
lines changed

1 file changed

+35
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
title: What is up? - CCOS Revamp
2+
---
3+
categories:
4+
outreachy
5+
tech
6+
open-source
7+
---
8+
author: dhruvi16
9+
---
10+
series: outreachy-2020-CCOS
11+
---
12+
pub_date: 2020-07-20
13+
---
14+
body:
15+
16+
17+
In my previous blog, I demonstrated what my Outreachy project was about. Here I will talk about my progress in the past 7 weeks.
18+
19+
### The Set-Up -
20+
21+
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.
22+
23+
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.
24+
25+
### Adding New Components to Vocabulary -
26+
27+
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.
28+
29+
### Updating Templates of the Theme -
30+
31+
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.
32+
33+
### My Experience so far -
34+
35+
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.

0 commit comments

Comments
 (0)