You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<li>Documents how to use a markdown component with CC Vocabulary</li>
449
+
<li>Documented how to use a markdown component with CC Vocabulary.</li>
449
450
<li>Embedded hyperlink to other open source projects to improve SEO.</li>
450
-
<li>Increased uniformity across documentation present in the storybooks</li>
451
-
<li>Adds alt descriptions & aria labels for certain images to improve accessibility.</li>
451
+
<li>Increased uniformity across documentation present in the storybooks.</li>
452
+
<li>Added alt descriptions & aria labels for certain images to improve accessibility.</li>
453
+
</ul>
454
+
<h3id="my-learnings-and-challenges">My Learnings And Challenges</h3><ul>
455
+
<li>Design is more than just picking colors and placing components on a grey screen.</li>
456
+
<li>It's important to read your own writings from an unbiased perspective to actually understand how well it would be perceived.</li>
457
+
<li>Publishing to npmjs is not difficult!</li>
458
+
<li>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.</li>
459
+
<li>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.</li>
460
+
<li>How essential it is to write neat code is something that's not spoken too often. (I wonder why...)</li>
461
+
<li>I always thought Vue.js sets up SPA's by default. I'm surprised you need to configure it additionally to do just that!</li>
462
+
<li>Storybook is just a really nifty OSS with great community support!</li>
463
+
<li>Vue.js is fantastic. Maybe I'm a Vue.js fan now. Should I remain loyal to React? I don't know.</li>
464
+
<li>Making a site responsive isn't the easiest of tasks, but it's certainly doable after a lot of stretching & compressing; lets say that.</li>
465
+
<li>"Code formatting is essential" would be an understatement to make.</li>
466
+
<li>Monorepo's have their own pro's and con's. But in our case the con's were negligible, thankfully!</li>
467
+
<li>GSoD isn't just about documentation; there's some serious amount of coding too!</li>
468
+
<li>You don't have to sit and write code for hours together. Take breaks, come back, and the fix will strike you sooner than ever.</li>
469
+
<li>Timelines change; improvisation being an essential aspect of any project!</li>
470
+
<li>MDX is a neat little format to code in! Documenting code is just so much easier.</li>
471
+
<li>Things become obsolete. Versions become outdated. Code maintaining is therefore, easier said than done!</li>
452
472
</ul>
453
473
<h3id="issues-pr-s-raised-during-gsod-period">Issues & PR's raised during GSoD period</h3><table>
Copy file name to clipboardExpand all lines: blog/feed.xml
+26-6
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@
39
39
<p><strong>Week 2</strong>
40
40
(09/22 - 09/28)</p>
41
41
<ul>
42
-
<li>Tackled queries regarding the choice of design, page structure etc., and sought approval from CC’s UX Designer.</li>
42
+
<li>Tackled queries regarding the choice of design, page structure etc., and sought approval from CC’s UX Designer.</li>
43
43
<li>Began to write the content which will need to fill up the main landing page.</li>
44
44
</ul>
45
45
<p><strong>Week 3</strong>
@@ -120,11 +120,11 @@
120
120
</ul>
121
121
<h3 id="the-vocabulary-site">The Vocabulary Site</h3><p>Here's the link to <a href="https://cc-vocab-draft.web.app">the landing site</a>.</p>
122
122
<ul>
123
-
<li>Went through <strong>3</strong> Design Iterations</li>
123
+
<li>Went through <strong>3</strong> Design Iterations.</li>
124
124
<li>Designed the mockups in <a href="https://figma.com">Figma</a>.</li>
125
125
<li>Wrote the content filling up the landing page.</li>
126
126
<li>After approval from the UX Designer, waited for an approval from the Frontend Engineer.</li>
127
-
<li>Sought continuous approval from my mentor</li>
127
+
<li>Sought continuous approval from my mentor<a href="https://opensource.creativecommons.org/blog/authors/dhruvkb/">dhruvkb</a>.</li>
128
128
<li>Used <a href="https://vuejs.org">Vue.js</a> + <a href="https://www.npmjs.com/package/@creativecommons/vocabulary">CC Vocabulary</a> to build a highly modularised site.</li>
129
129
<li>Went through a couple of iterations of the website itself.</li>
130
130
<li>Made about <strong>112</strong> commits (<strong>15,000</strong> lines of code) in my <em>gsod-nimish</em> branch.</li>
@@ -145,6 +145,7 @@
145
145
</pre><ul>
146
146
<li>PR was reviewed and merged on the <strong>25th of November</strong>.</li>
147
147
</ul>
148
+
<p>Here's how the site looks right now:</p>
148
149
<pre>
149
150
<center>
150
151
<img alt"The final website!" src="website.png"/><br>
@@ -168,10 +169,29 @@
168
169
<li>Modified the existing overview page.</li>
169
170
<li>Removed highly verbose sections from the docs. </li>
<li>Documents how to use a markdown component with CC Vocabulary</li>
172
+
<li>Documented how to use a markdown component with CC Vocabulary.</li>
172
173
<li>Embedded hyperlink to other open source projects to improve SEO.</li>
173
-
<li>Increased uniformity across documentation present in the storybooks</li>
174
-
<li>Adds alt descriptions &amp; aria labels for certain images to improve accessibility.</li>
174
+
<li>Increased uniformity across documentation present in the storybooks.</li>
175
+
<li>Added alt descriptions &amp; aria labels for certain images to improve accessibility.</li>
176
+
</ul>
177
+
<h3 id="my-learnings-and-challenges">My Learnings And Challenges</h3><ul>
178
+
<li>Design is more than just picking colors and placing components on a grey screen.</li>
179
+
<li>It's important to read your own writings from an unbiased perspective to actually understand how well it would be perceived.</li>
180
+
<li>Publishing to npmjs is not difficult!</li>
181
+
<li>Knowing the previously existing code in your project is of serious essence. It's important to understand the code styles, structure &amp; activity of the code that you are dealing with.</li>
182
+
<li>Be patient! Its fine to delay something if it makes sense to have it logically accomplished only after certain other tasks are done &amp; dusted with.</li>
183
+
<li>How essential it is to write neat code is something that's not spoken too often. (I wonder why...)</li>
184
+
<li>I always thought Vue.js sets up SPA's by default. I'm surprised you need to configure it additionally to do just that!</li>
185
+
<li>Storybook is just a really nifty OSS with great community support!</li>
186
+
<li>Vue.js is fantastic. Maybe I'm a Vue.js fan now. Should I remain loyal to React? I don't know.</li>
187
+
<li>Making a site responsive isn't the easiest of tasks, but it's certainly doable after a lot of stretching &amp; compressing; lets say that.</li>
188
+
<li>"Code formatting is essential" would be an understatement to make.</li>
189
+
<li>Monorepo's have their own pro's and con's. But in our case the con's were negligible, thankfully!</li>
190
+
<li>GSoD isn't just about documentation; there's some serious amount of coding too!</li>
191
+
<li>You don't have to sit and write code for hours together. Take breaks, come back, and the fix will strike you sooner than ever.</li>
192
+
<li>Timelines change; improvisation being an essential aspect of any project!</li>
193
+
<li>MDX is a neat little format to code in! Documenting code is just so much easier.</li>
194
+
<li>Things become obsolete. Versions become outdated. Code maintaining is therefore, easier said than done!</li>
175
195
</ul>
176
196
<h3 id="issues-pr-s-raised-during-gsod-period">Issues &amp; PR's raised during GSoD period</h3><table>
0 commit comments