 So, my name is Jai Kanakya and I am an avid tracker and a front-end developer at Sokrati. Today, I am going to show you how you can become a better front-end developer by maintaining a daily jQuery plugins website. So, just a quick show of hands. How many of you have used jQuery plugins before? Okay. That covers almost most of the audience. How many have created jQuery plugins before? Okay. A good amount. So, we all know that jQuery is the most popular JavaScript library right now. As Chris had previously shown, jQuery powers 65% of the top 10,000 websites. So, how did jQuery reach such a high usage amount? I believe it is because of the following factors. Simplicity. So, the first time I saw that you can chain methods, I was mind blown. Second cross browser. So, the initial reason why people adopted jQuery in the first place. You have to just write code once and it should be able to run across all browsers. So, that means you have got lesser code to write and maintain. The fourth one is community. So, you have got a huge and robust community with active maintenance, which makes sure that all your browser-specific bugs are acquired and your website runs smoothly across all the browsers. And I believe one of jQuery's greatest power lies in the variety and diversity of its plugins that developers have built upon it. So, a famous quote from John Desig, I just like the plugins where you just snap something in and things just work. So, this was what got me hooked on to jQuery in the first place. From the most complex plugins that creates 3D parallax scrolls to the most simplest one that just let's say submits a form using Ajax. jQuery has got each and every type of plugin available. So, how many have visited this website once before? So, what is jQuery.in? A quick show of hands. Okay, one. So, jQuery.in is a very simple curation engine that features one jQuery plugin a day. It has got prominent links to the home page, to the author, to the demo, and to the download links. You get to start it as fast as possible in using that plugin. So, currently it lists about 1300 unique jQuery plugins. So, let's say you want to add some amazing audio effects to your website. You can use easyaudioeffects.js. Let's say you want to add some snazzy background particle system on your website. You can use particle around.js. Let's say you want to visualize complex calendar schedules on your app. I've got the one for you. grassschedule.js. So, similarly, let's say you want to add some intelligent time-away flat shadows to your DOM elements. jQuery has got you covered. You have got four shadows.js. So, I can go on and on about the 1 to 9-6 plugins that are more available. So, let me give you a bit of a background. So, why I started jQuery.in. So, back in June 2012, I was just getting started with my web designing career and plugins.jQuery was down and there was no website or app where you can just discover new jQuery plugins and search for newer tools. And at that time, I also wanted to learn WordPress. And I was using browser bookmarks to save and link to all the important scripts, tutorials, code or anything interesting that I found that was quickly becoming unfeasible. So, this is why I launched jQuery.in. So, what is the most important thing in maintaining a daily jQuery plugins blog? It's curation. So, curation is a field of endeavor that is involved in managing, assembling and presenting a select list of items. So, how does this help you as a front-end developer? So, every weekend, I go through a lot of Twitter feeds, a lot of RSS feeds, a lot of NPM repositories, a lot of GitHub repositories in order to search for newer and better jQuery plugins. So, how does this help me as a front-end developer is that, one, I always get to stay in touch with the current trends and the latest tools. Second, for any new project that I use, because I've got this vast knowledge of jQuery plugins, I can cherry-pick the most useful or the best jQuery plugins to use in my next project. The most important thing I learned over here is patience. Because doing this for the past three years for every weekend, it requires a lot of patience and persistence. Especially in front-end development, learning a new framework, whether you are learning a new language, whether you are solving a very hard-to-debug bug or whether you are thrown in an existing project of which you have no idea about, you should have the patience and the persistence to continue with it. Also, the next time your client or your designer or your project manager asks you if a particular effect, animation or user interface can be implemented, you always know the answer because you have listed so many jQuery plugins. So this is how it helps in your current projects. The next thing it improves is your skill set. So today, if you go through the careers page for any front-end developer today, the number of skills that are listed goes on increasing day by day. So because of which coding is not the only thing that front-end developers need to be mastered in. So every day, you have got to work in sync with the clients, with the design team, with the marketing team, with your project managers, with the back-end teams, with your DevOps teams in order to get something online. So it's always advantageous to have a basic knowledge of how things work across all the domains. So if you're maintaining a daily online blog, you automatically get to learn all of these things and you are able to solve problems in other teams as well. So this is how you can remain in better sync with other teams because you have already worked in that team and you have some very basic knowledge of how it works. The next thing I learned is marketing. So out of the rules, laws, axioms, gans of marketing, I believe these following points form the main foundation. First, marketing starts before starting any project. Marketing should never stop even after a successful product launch or a successful product. Third, content email marketing, content marketing, word of mouth marketing, so these are the best mediums. And the last one, you should always have the ability to run experiments of let's say A and B tests in front of actual users. So in my case, whenever I want to launch anything new, I first run some basic marketing on jQuery.in in order to get some beta feedback and I should be able to measure them effectively. The next thing I learned is search engine optimization. Now SEO was a very hard-learned initial lesson for me. SEO is not something that you can just lay off doing for a very long time. Think of it like this, SEO is a long-term game plan and if your app is dependent on SEO, you have to go to include it from the beginning. So some key points for SEO I learned is that one, black hat SEO does not work. You can try your best but it just does not work. These three points always contribute to a good SEO score. The first is content, so which is the king. The next is regularity or the frequency of your posts. The last one is social media. Don't just have accounts across every social media. You have to be active and interactive across all of them. Coming back to the less sexy part of the job is maintenance. If you build it, you got to maintain it. So some key points over here I learned is that you don't realize the importance of backups until you lose data once. So I've lost data once and I know how important, how difficult it is to get it back up and running again. The next thing, always get a reliable host with a good hosting plan and quick support. Server prices have decreased drastically in this last few years and hosting is one of the area that you should definitely splurge on. Some quick pointers to you always maintain revisions. So that's basically and a quick rule of thumb is that let's say tomorrow you lose everything. You should be able to set up everything right from DNS to automated email marketing in less than a day. So this is a ground rule that I always work upon. The most important thing that I have learned is source code hunting. Now everyone has got a different way of writing his or her own code. Some people like to make use of heavy use of software patterns. Some people follow very strict coding guidelines and structures. Some people write more comments than the code itself. Some might follow some entirely different conventions than you. Browsing source code is still considered one of the best ways to boost your development skills. As great writers or also voracious readers, we too should also learn to spend quality time reading quality code. So by reading so many codes, what I have learned is there are so many shortcuts in writing the same thing. There are so many new workflows of writing the same code. There are so many new tools and integrations that aid you to write better code. People have written so many integrations with existing apps that you weren't thought were possible before. The next thing is networking. So how many of you people say that networking is very important? So that is why we are all here in the first place. Because we want to interact and exchange ideas with other FEDs and we enjoy ourselves doing so. So in the case of jaco.in, I have tried to contact each and every plugin author whether it can be through Twitter, whether it can be through Facebook, whether it can be through LinkedIn, whether it can be through email, or even Google+. So because of contacting a new FED almost every day, I have gotten a lot of project recommendations, a lot of offers, a lot of ideas, a lot of collaboration opportunities, a lot of amazingly long email chains. So I've got to learn so many things. So I can tell you with certain certainty that if you are maintaining an online blog, your network will grow exponentially. And it's also great to be in touch with so many developers, opportunities. And coming back to career choices, so as a relative newcomer to the field, you can also make informed career decisions by asking some very crucial things to the more experienced peers. The next thing, automation. Everything that can be automated should be automated. So if you're running an online blog, every single bit of automation counts. So this is very important. So right now, jqa.in, so it has got some existing WordPress plugins. It has, I've written some custom WordPress plugins. I've written some custom book marklets. I've written some custom Chrome extensions. I have made use of some of integration with some online apps. Also, I've written some custom automation scripts. So right now, jqa.in has got the ability to buffer up push for one month to get the repo information to schedule them day by day, to check for broken links, then to schedule, then to publish them day by day, then to inform that author, then also simultaneously to share it across all the social media channels, including email, and later on do some basic SEO optimizations. So all this flow is currently automated. So how does this help you? So you can use this existing infrastructure to have to launch newer blogs, or you can use that existing pieces of code that you have to write more automation tools. Also, for every next project that you undertake, you will make sure you will write the project in such a way that it can later on be automated. So some key takeaways for you is that keep using jQuery plugins. It's never too late to start something. Just launch, you can iterate and optimize for it later. So thank you guys. I think so. So the slides are available online as well. It's kind of fresh through the slides. So I wanted to make this more interactive. So if you have got any more questions, any doubts, how do I launch, how do I do this, how do I do that, you can easily ask me. Any questions? Two different things. So jQuery plugins, Angular Directive Web Components. So this is how it is structured. But I think so Web Components is currently in kind of beta testing. Everyone is still trying to get to know them. Some jQuery plugins are trying to adapt to Web Components. So they are trying to write the code or they are trying to write the structure in such a way that later on, let's say one year later or two year later, they can then shift to Web Components. They can offer that same thing as a Web Component. Because I have seen many jQuery plugins that have become independent scripts or independent Angular Directives. So by separating the core logic, you can do that. Web Components, I think so is supported by Chrome and Firefox. But the adoption rate, so right now it is still getting that initial bunch of user, it hasn't still hit that sweet spot where everyone starts using it. Okay, thank you for being an amazing audience.