Skip to content

Commit 1130c76

Browse files
committed
Add conclusion and series
1 parent 73e2ebf commit 1130c76

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

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

+9-3
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,9 @@ open-source
77
---
88
author: dhruvi16
99
---
10-
pub_date: 2020-07-13
10+
series: outreachy-2020-CCOS
11+
---
12+
pub_date: 2020-07-20
1113
---
1214
body:
1315

@@ -16,7 +18,7 @@ Well in my previous blog, I demonstrated what was my Outreachy project about. He
1618

1719
### The Set-Up -
1820

19-
The [Creative Commons Open Source](https://opensource.creativecommons.org/) website is built using Lektor. I was not very familiar with [Lektor](https://www.getlektor.com/), 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 and working of themes in a Lektor app. For integrating new styles from Vocabulary, I replaced templates/ folder with a theme/ folder.
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.
2022

2123
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.
2224

@@ -26,4 +28,8 @@ The [mock-ups](https://www.figma.com/file/mttcugI1UxvCJRKE5sdpbO/Mockups) for th
2628

2729
### Updating Templates of the Theme -
2830

29-
I started by updating the home page template. I try to make the code cleaner and more readable. Going through the Lektor documentation, I came across different ways to do so. One of them was flow blocks, 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.
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)