Hello there, 

Its good to see you here.

So, this week I created a new PR for the new cheatsheet and also to fix a few responsiveness bugs on the landing page. My work for that PR is done. I have to fix a few things on the new cheatsheet too. There are a few features that require popper.js but thing is that popper.js is not working properly with the CDN so I need to download it and use it offline like we use bootstrap in vendors.min.css file. For using popper.js offline I need to edit a lot of stuff including gulp files. That's why I am first going to design a new documentation page for EOS Icons first then later I will fix the popper issue.

Ahh. I think that's it for now.

Peace!

Hi and welcome again!

Let's get going.

What did you do this week?

Last week I was fixing bugs and errors in the landing page code. I finished with that(almost). I had a really hard time, because I created a lot more errors while fixing a few errors. But Finally, I don't remember how but I fixed those. Well, I still need to do a few more adjustments but its fine. Also, I wrote the code for the cheatsheet and its almost ready.

What's coming next?

After I finish with the Landing page and cheatsheet, I will create a Mockup for the documentation page of EOS and later I may have to implement it too. Those are some later plans.

Did you stuck anywhere?

Yes, yes I was stuck for a long time here, when I was fixing the landing page. Man, I don't know how but some vs-code extension played with my code and created some .map files on its own. And keeps on generating those files automatically every time I use gulp. That was a pain but eventually, I was able to fix that!

Hey! Welcome. 

I hope you are doing well. Oh, you are here to see how am I doing right?

Well, I started implementing cheatsheet(remember what cheatsheet is?If not then see previous blogs!). I planned to first create basic html, css and javascript files. But something else happened. 

Remember that landing page I created earlier?It's not working properly since my mentors shifted everything to new SMACSS structure. So, now I decided to stop the implemetation for now. First I will fix the landing page, then insted of first creating basic pages in Html, CSS and javascript. I will directly code in pug, SCSS and will use javascript in it in accordance with the brand new SMACSS structure. This all is not much of a big deal. Cheatsheet doesn't require much time to finish. I just need to fix the landing page first.

So, I am working on it right now. See u later!

Till then, Peace!

Hello there! Good to see u here.

Now, I'll tell what you are here for!

What did you do this week?

So, I finished the implementation last week and its already merged. This week I completed mockup for the cheatsheet(that's what we are calling that). Its a subpage of main EOS icons landing page which contains all the icons. Its has two subsections itself one is for EOS icons and second one is for extended EOS icons that are made 1-1 from google material icons. Currently mentors are reviewing that mockup and I am modifying the changes accordingly.

What's coming next?

After this is over I'll start the implementation of the cheatsheet. First I will create everything in basic HTML, CSS and bootstrap 4 they I'll have to convert it to pug and SCSS according to our new SMACSS structure that my mentors introduced recently.

Did you stuck anywhere?

Not really but, yes I was stuck a bit when I was testing the converting HTML into pug. But my mentors helped me out of it.

So, ya that's it for now. See you next week!

Hello and welcome to my fourth blog for gsoc 2019.

So, this week was really challenging for me because I was implementing the Landing page for EOS icons. Yes, its the same page I started implementing more than a week ago, but things have changed since then. Earlier I was trying to create my own CSS but it was getting very lengthy and hard so I removed it all and shifted to bootstrap 4 and also I converted all the html to pug. I also had to change grunt files but my mentors recently thought of not using grunt anymore and shift to gulp. So now we will generate our webpage with gulp. After all this I created the PR and pushed all my changes to it.

This might sound very simple and straight forward but actually it wasn't. I had a really bad time removing all the layout errors, keeping in mind the responsiveness of the webpage. Overall this was a great experience, especially when I finally saw the landing page, I was like questioning myself "Am I the one who wrote the code for all this?really?me? " 

Anyways this was fun. So, see u later. Stay tuned! 

Peace!