Skip to content

Commit 2366b0b

Browse files
authored
Merge pull request creativecommons#549 from nimishbongale/master
Nimish GSoD Blog Post (Vocabulary Site Updates v1)
2 parents a5b0359 + 6039bad commit 2366b0b

File tree

1 file changed

+40
-0
lines changed
  • content/blog/entries/cc-vocabulary-docs-updates-1

1 file changed

+40
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
title: Vocabulary Site Updates (v1)
2+
---
3+
categories:
4+
cc-vocabulary
5+
gsod
6+
gsod-2020
7+
---
8+
author: nimishbongale
9+
---
10+
series: gsod-2020-vocabulary-usage-guide
11+
---
12+
pub_date: 2020-10-26
13+
---
14+
body:
15+
16+
Hello there! Well well well. It has been an eventful first few weeks, to say the least! Let's gauge my progress, shall we?
17+
18+
## Vocabulary Site Updates (Edition 1/many more to come)
19+
20+
### What I've been upto
21+
22+
I've mainly got myself invested in a survey of the existing documentation that vocabulary currently possesses, and find places where it could be made better. After clearing those issues out, I began building the main landing site for `Vocabulary`, `Vue-vocabulary` and `Fonts`. It wasn't particularly difficult to establish the necessary workflows as I had done something similar before. During the process of designing the basic structure of the site, I came across a few instances where I felt we needed new/improved components & I discussed the same with my team over on the sprint calls. The design of the site is nearly done. I'm also building the site parallelly & seeking approval from the CC Design Team. I've gotten myself involved in multiple other community contributions to CC as well across multiple of our repositories.
23+
24+
### What I've learnt
25+
- Knowing the previously existing code in your project is of serious essence. It's important to understand the code styles, structure & activity of the code that you are dealing with.
26+
- Be patient! Its fine to delay something if it makes sense to have it logically accomplished only after certain other tasks are done & dusted with.
27+
- How essential it is to write _neat code_ is something that's not spoken too often. (I wonder why...)
28+
- I always thought VueJS sets up SPA's by default. I'm surprised you need to configure it additionally to do just that!
29+
- Storybook is just a really nifty OSS with great community support!
30+
31+
### Other community work tidbits
32+
- I've been working on the Dark Mode (a much awaited feature, at least for me!) for our storybooks with some support from our community. It should be up and running shortly!
33+
- Fixed some formatting bugs in the `README.md` & suggested changes wrt to `npm v7` considerations.
34+
- Fixed storybook components docs for 2 features.
35+
- Raised a ticket for a component to render markdown text within vocabulary itself.
36+
- Raised a few other issues for potential hacktoberfest contributions.
37+
38+
<p align="center">
39+
<strong>Thank you for your time! To be continued...</strong>
40+
</p>

0 commit comments

Comments
 (0)