Ravi kumar

Okay. So hello. I am Ravi. I have a strong background in the software development and have been working in business industry for over 5 years. I have a degree in bachelor of technology, which has enabled me to design and develop complex software system. In my current role, I have experience with a different technology such as Node, uh, Node. Js, React. Js, React Native, Angular. Js, and MySQL, right, and many others. Recently, I have been significantly reduced API latency by approximate, uh, 85% by implementing bullQ for the large scale, uh, email handling. We stabilize our product up to 45% and optimize the SQL query for our large extensive customer data. Uh, enhanced come due to this, uh, due to this, uh, our enhanced system performance by 40%. Adaptability and teamwork are 2 of my core strength. I am adept at quickly adapting to new environment and collaborating effectively with the team member to achieving, uh, project goals. My comprehensive understanding of Node. Js and React. Js enable me to contribute seamless to upcoming project with minimal supervision. I am confident that my academic background, technical expertise, and skills make me a valuable asset to any team. This is all about me.

Okay. So, uh, story broke. Alright. Yeah. So, uh, actually, I am familiar with the, uh, Storyblock.com. I'll explain, uh, this what is the, uh, what is this service and how, uh, this will work. Right? Okay. Let me alright. Okay. So, uh, basically, what is okay. Fine. So, uh, what is what is storyblock.com? Okay. So, basically, uh, this is the CMS, uh, basically, system. CMS means the content management system. That is okay. Uh, it enable developer to create and manage content rich website, okay, and application. So, basically, uh, what is what is, uh, what actually actually it is does, it provide a flexible and, uh, innovative interface, right, to the editor, right, who can edit, create, uh, and organize the digital content, uh, with the panel. Okay? So, basically, what is the what is, uh, CMS? Uh, it is a dynamically front end experience. Right? Uh, we we don't we don't need the, uh, back end part. All the content will be dynamically at the front end. Okay. So, uh, the key feature, uh, the, uh, this CMS system have, first is the visual editor, okay, which, uh, which offer a, uh, basically, visual editor allow to content, uh, to edit, create any content with the with the context of their website and the application. So that is, uh, it it it also have the, uh, content block, basically. Right? Uh, what is content block? Basically, this is the this can be user this we we can also call it a reusable block. Right? For example, such as task block, uh, image block. Right? And there is also a custom, uh, component like a file system and structure. Right? So this is, uh, this is how the content block works. And it also has the, uh, basically, uh, localization. Right? What is localization means? Uh, it will support the multilingual. Right? Suppose if, uh, if some of the client are from, uh, client from the south side. Right? I mean, Tamil side and some of the, uh, client are from, like, a Punjab side. Right? Or or we we can also the international language as well, like, uh, some of, uh, the, uh, from the, uh, Saudi Arabia. Right? Uh, some of the language has Kundu, uh, and, uh, UK English and furthermore. Right? Thai language, uh, Western. Right? So it will consider, uh, it will, uh, help the localization part as well. K. So it is also the API driven.

Basically, uh, the c m CMS architecture provide a RESTful API. Right? That developer fetch the, uh, front end and integrate to their front end application. K? So this is how, uh, it is here. Okay. So it also provide the CDN, global CDN. What is CDN? CDN means, uh, if you are in India, right, and you are, uh, using uh, you are fetching the data from the another country like USA. Right? So it will take time. So rather than to fetch the data from the USA part, we will but we will know, we will get the, uh, data from the, uh, basically, CDN from India. Right? So that is how our CDN work in this database platform. Okay. Alright. Okay. So next question will come. Describe our development experience working with GMX platform like Starburst, WordPress, Nagento, and Shopify. Okay. So development experience. Alright. First of all, uh, this this type of CMS platform development, uh, experience is very smooth. Right? We don't need to, uh, write a a a heavy code or the bulky code. Right? We what we can do simply, we can, uh, drop and drag feature, uh, put that in there. Right? Sometime, we if you want to, uh, if you want to add a particular block and a particular section, right, for, uh, for I want to use the testimonial section in our website. Right? So I can simply create a section of testimonial and update the update the content related to that testimonial. Right? So this is how it's work. Uh, it also provide the many add on features, right, uh, in our, uh, CMS panel to, uh, to integrate with our, uh, to integrate with our application. Right? So it will make a more easier way, right, to manage our application. For example, I'll give you example of that word phrase. Right? Uh, if we use the element in a wordpress, right, so our our work is to simplify. Right? We can simply add a custom section. We can add a text section. Right? We can add a image. Right? So there is a multiple way. So we can create our website in a in a simple manner, in a less time. Right? So our time, uh, our time and our efficiency of, uh, code management will easy. Our time will save. Right? So our development experience working like a CMS platform is very, uh, easy. One more thing, uh, we need to think about the CMS platform. We don't have to manage the back end technology. Right? In a c s CSM platform, our back end technology will be automate. Right? We just focus on the, uh, front end part, means the design part, how our website is look like. Right? We we are focused to that, uh, that particular area. We don't need to, uh, think about the how technology, uh, what are the API, right, security purpose. So we don't use to them. Right? We we are going to simply manage, uh, if you want to, uh, be secure our website. So there are the multiple, uh, plug in, right, or the, uh, add on. We can add to, uh, simply any, uh, CMS platform like a WordPress or the storybooks also. Right? So this is how, uh, what we so what is the final conclusion of about the development experience? It is very smooth, uh, less time taking. Right? Uh, complete complete, uh, city will reduce to very much. Right? We don't we don't need to, uh, integrate with the back end. We don't think about the back end as well as the database. Database also be managed by insight. Right? Uh, this so this is how, uh, our, uh, development experience is very, uh, good. You know? So that is.

Okay. Yes. Also, I have, uh, I have been working with the Next. Js for the React. So I'll give you an example. Uh, I'll compare the, uh, basically, React with the CMS development. Okay. Uh, I'll give you an example. I also work on the Next. Js and the React. Uh, but I'll give a comparison between the, uh, one react and the CMS developer. Okay. So what is react? So react basically is a library frame the library. Right? So in the react, we we have to write the code, right, code of every front end. Means, if we want to use a section uh, like a testimonial section for any website, though we then we have to, uh, make, uh, we have to write a code for that particular section. Okay. But in a CMS develop in a CMS platform, we don't we don't need to write a code. We see we are simply add on any, uh, plug in, right, like Elementor. Right? And create a section easily in a in a few minutes or a few, uh, basically, hours. But if we go to the React, then it will, uh, take it will take time, right, to, uh, write the code. Okay? And we also use the, uh, some CSS part to to beautify our the, uh, basically, section. Right? This is how. And, uh, and what is and second difference is basically, what is second difference? Second difference is, uh, in a React, it is a plat it is a multiplatform. Right? Means, if we if we write a code in a React, then we can, uh, some modify and some, uh, some modify and some manipulation after, we can export, uh, the our platform for a web for a mobile application as well as the app iOS application or Android application. Right? But in the CMS development, what we need to we need to use our basically, uh, if you want to use, uh, for Android app or the iOS app, so we can't do that. Right? So it is only work on the website. Right? So, uh, so this is, uh, this is this is a big disadvantage of the CMS Development. Right? And for the scalability, right, for the scalability, React is very good, right, rather than the CMS development. Right? Because because, uh, if if we initially suppose if we initially, uh, our page like a blog website. Right? Right? So a a globe type website is easily created in a CMS development within few days, maybe 1 or 2 days. Right? But if we want to, we use React, then it will take, uh, uh, 7 days, 10 days, means, uh, longer than the CMS development. Right? But once you did a website once you did make a website, after that after that, uh, you can scale, uh, if you want to convert this blog website into the, uh, basically, uh, ecommerce website. So you can you can basically integrate some pages of, uh, ecommerce website and convert their, uh, and convert your website to the, uh, uh, basically, ecommerce website. But in that CMS development, you can't. Right? You have to make another website of the, uh, basically, ecommerce system. But if you want to, uh, also create ecommerce system, then then you won't be, uh, uh, you won't be more scalable. Right? You cannot handle this so much, uh, how, uh, large data for the client. Right? Suppose if client if client want uh, I'll give you an a brief example. Right? How your system will not handle for large data. Suppose your client will require the functionality of import data. Right? And after import import data from the Excel sheet, right, there may be a 50,000 data or the 1 lakh data. Right? So you can you can do with the CMS development. So you have to use a React and any back end technology like a Node. Js. Right? So what you can simply do, you can simply put a excel sheet and excel sheet will upload all the data with the SQL query. Insert query. Basically simple. Right? And, uh, insert all the data in our database, but you can't do with the c CMS development like a WordPress or any development story flow. K. So this is the major difference between the React and the CMS development.

Okay. So most, uh, complex website you haven't created or managed. Okay. So the most important website that we have created, right, that is performance review. Right? In the performance, uh, basically, our, uh, people's stone product. Right? So what is that? I'll I'll give you a glimpse how how complex this function. Right? So there is a large there is a large number of customer existing customer percent there. Right? So what we need to do, we need to, uh, in a in a goal see, we have first goal management in our product. Right? So there is a loss of customer. Right? Uh, loss of client we have, and all the client have the large number of customer. Right? So we have around 10 lakh customer in our goal management part. Then we have to migrate all the goal management customer to the performance review. Right? So we need to create a website or we need to create a website or the feature or the a different module. We can say different module of the same product. Right? Uh, so I have to write the code entire code of the performance review. Right? And have to migrate all the customer to the our existing, uh, so our new basically, new, uh, website. Right? So I have I I I have done this project, uh, basically, uh, individually or with the few team member. So what we need to do? 1st, we have, uh, goes to the migration script. Right? We have to move all the data with the another customer another day database or we have to synchronize our database. Right? So so what we knew but we will but we have to to, uh, tackle this program. Right? First first, we, uh, we use the technology of Node. Js, right, and the React as well, right, to create the, uh, to create the website. If we use the Redis ticket to to, uh, to reduce the our, uh, basically, API latency, we don't need to call the, uh, every time our database. Right? So we use Redis. Right? We use the, uh, basically, Docker also because, uh, 1 or 2 members, uh, are after, uh, we come in our project, so we use Docker and set up the Docker with the Kubernet. Right? And upload our, uh, Docker container with the our AWS server. Right? Okay. So we use 4 core processor in the, uh, website. Okay. So, uh, uh, what are the main, uh, basically, integration with our website? We also, uh, use the, uh, Google Analytics in our, uh, our website, right, to to trace the, uh, basically, customer behavior pattern. K. How much customer is onboarding in our website? How much customer is actively? Right? So this is how, uh, one more functionality, email triggering. Right? Suppose, uh, if someone is, uh, going in a participant in a review part, then we have to send a reminder message email to the customer. So we you we also implement the bull queue. Right? Uh, with the help of the bull queue, ticket. We manage the large scale of data. Right? We also optimize the large query, right, uh, for the different client as as I as I told you. So this is the major, uh, basically project I have worked on. Uh, there is a lot of feature like auto auto I'll I'll give you example of a one feature. Most of the, uh, most of the feature which I developed in will delete, that is the auto rating feature. Right? What is auto rating? I'll let you know. Or suppose you you check-in on your goal. Right? Suppose your goal, uh, your goal has the 70% of, uh, achievement in your goal. Right? And you would you want to participate in your appraisal review. Okay. So what is what is auto rating functionality do is auto run auto, uh, auto rating functionality will calculate your rating, right, based on your achievement and upload the database. So all the feature are automatically user don't need to, uh, don't need to go to the rate or to, uh, go to the their goals and do the invisal rating. Uh, user have to, but simply initiate the review. All the rating will be automatically filled. If you if user don't satisfy to particular rating, then, uh, it will change the rating and, uh, submit the review. Right? Similarly, as a similarly, manager will, uh, do the same. Right? After review after review your review will close, your final overall rating will calculate the systematic manner and display in a Excel report. So there this is how, uh, this website will work. That is.

Okay. So, uh, how we update the plug in, like, in a system system? Okay. So, actually, I have worked with the, uh, CMS platform, many, uh, many, uh, CMS platform like a Spotify and the WordPress. Right? I, uh, so I'll give you example with the WordPress so that it will better understanding. Okay. So how we maintain, uh, how we maintain our, uh, plug in? Right? Maintain our plug in and the update plug in. Right? So suppose we we, uh, I'll I'll give you example with the, basically, uh, starting method. Suppose we, uh, have, uh, we want to make a website simple. Right? So what we need to do, we analyze the, uh, our UI part and the UX part and design part. Right? And simply, uh, check how much, uh, plug in we need to, uh, be installed in our virtual CMS system. So first of all, we will we have to design the page. Okay? So we'll use the, uh, basically, Elementor plug in. Right? Elementor plug in, uh, our when we are, uh, install the Elementor plug in and put the, uh, basically, uh, plug in in the plug in section. Okay. So there will be a a loads of list. Right? We simply check the how much, uh, how much download rating, right, how much rating of the current latest plug in has. Right, and how much, uh, how what is the basically update last update in that particular plug in. Right? Then we use that plug in, like, first plug in. If we want to use, uh, another form type, right, we we want to use a, basically, uh, foam. Right? So what can we do? We can use a, basically, uh, custom form 7 plug in, right, for a WordPress. Right? We simply install the plug in. Okay. So so but we do so, uh, I'll give you example of contact form 7. So we will install the contact form 7, right, to manage manage the form type of the plug in. Right? Okay. So this is how, uh, basically, our form will work. Suppose, uh, we need to submit a application form, right, in our website or interest showing a website. Right? Like a blogging website. Right? So this is how we can, uh, basically use Pradhu. Alright. Or there is a many many plug in also, like a Tathastu plug in to design our website. Right? Or also there is a integration, uh, chatbot plug in also to integrate the WhatsApp WhatsApp chat with our application. Right? There is also the, uh, basically, analytic plug in, right, to maintain the our, uh, customer, uh, basically, behavioral pattern, how our customer will, uh, basically, uh, interact. So this is how we will maintain the problem part.

Okay. So I'll give you an example. How I contribute my code. Suppose I have created a website. Right? Our website is fine. But we we want to use, uh, a particular, uh, section or a particular functionality which which is not which is not attained by any plug ins. Right? So we we also there is also functionality in any CMS platform like a Buds Nest or the Storyblo. Right? We can import we can import or rewrite the code in a system also. So what is what is PS system, um, what is CMS done? Right? CMS basically, uh, read the code and make the feature with the with the, uh, with the, basically, with the, uh, basically, platform for the application level. Right? So how can we do our code simply? Okay. So, uh, contribution of code. Right? Okay. So first first, I have but I have to do I have to push I have to write my code and and push my code in a GitHub. Right? And we will see we will fix and check the code. Right? And, uh, what we can do more things. Right? If our if we use the small code, like, a small feature, then we simply put our code into the CMS panel. Right? If our code is large, right, we then we need to use the GitHub code, the Bitbucket. We simply push our code to Bitbucket and make a pipeline with the CMS panel. Right? So it will basically integrate with the GitHub also. Right? Okay. Okay. So so if you want to use a particular API data in our system means suppose we, uh, we have a API in a Node. Js for the, uh, basically, Java. Right? And we we have to use the API. Right? After after we use the API, that date we are getting the data from the API. Right? So so after the getting data from the API, but we will need to we we can use their data. Right? Means, let's see, we get the data of the product list. Right? So we simply, uh, store the, uh, all the product list in our, basically, website. Right? And this back end part will this back end part will, uh, contain in GitHub and execute the another server. Right? We will call the API in a basically, our WordPress. Basically, we use the WordPress as a content like a React. So this is how we are a customer. How? Okay. So we also we also, uh, basically use a post request also means suppose, uh, some API is a post request API. Right? So we will call the post API so, uh, so that our data of prod means, obviously, from the product data, we'll update the, uh, basically simultaneously. So this is how we can, uh, use the CMS code base, right, to integrate the another, uh, basically, language. What is the what is its advantage? I'll let you know what is its advantage. Okay. So suppose suppose you have 2 module. Right? Suppose you have a 2 module and, uh, some of the your team member are from the different technology like a Node. Js or like a Java. Right? They make a API in a Java or the Node. Js. Right? Or then you have to use their API to fetch the data. Okay. So but we can can you simply do you can simply use the API. Right? So but, uh, one more this are the more, uh, advantage in this application, Uh, you you are using a multiservice sorry. Micro service micro services. Right? So this is, uh, this is how you can use the basic use code.

Okay. So this is a typescript. Okay? Okay. So in a typist group, uh, user is the get the interface. Uh, the typist group. Okay? The edge Uh, give me the name. Okay. Alright. Give me the name. Please give me the page. Okay. So there is a mistake. Right? See, your age is defined the question mark number. Right? So it can it can be, uh, undefined. K. So it can be null because, uh, because we don't we, uh, it it it is not necessary to, uh, edge having the number. Right? It can be null or the undefined If user, uh, user dot age is undefined, right, your code will move to the, basically, else part. Right? And it will show the, uh, basically, hello means hello, Ravi. Your age is unknown. Right? So what we need what we need to simply be, uh, use we have to use user dot age, uh, user dot age is not equal to undefined. Right? That is how we have to write. Right? So, uh, this is code will work. So we need to change the, uh, basically, user dot age is not equal to end undefined in this code.

Okay. In a given dedicated setup, uh, how would you migrate content? How do you migrate content with the plug in to, um, the plug in to? Okay. Okay. Okay. Migrate. How would you migrate its content and plug in to the Storyblock? Okay. Insuring your content and not compatibility. K. Alright. So there is a way to migrate. Alright. Okay. Uh, migration. So there is a, uh, there is a, uh, one type. Uh, or sorry. There is a one way to migrate to migrate our, uh, to to migrate our, basically, phone 10 and okay. So, well, uh, to migrate the our content, uh, we have to also migrate the plug in content to the plug in. Okay. Okay. So, uh, migration we need to do some steps. Right? We need to follow some steps. Right? So first, we need to do, uh, but we but we will do, basically, uh, we need we need to check with we need to check the field. Right? A content type field, uh, like a, uh, like a, supposed, name field, right, age field, text, email field. There is, uh, any type of field. Right? We had to identify the content type field and the relation lesson relationship basically between their, uh, entities. Right? Then uh, we we create a, basically, map mapping document. Right? Obviously, we have to write a mapping document, right, uh, which having the types field name, right, and the relationship, right, of the, uh, basically, which present in the system, uh, basically. Right? After that after that, uh, after after that, we will export. Means, uh, there is a functionality of export, right, in a CMS, uh, system every format. Right? We can export the basically, their field. Right? Basically, their field and, uh, in any file, like a JSON or 3xml file or the TXT file or c s e CSV file. Uh, but but make sure we will export in a JSON file. Right? Uh, right. After the export, we have to import. Right? We have to import our, basically, uh, feature or the field, right, in the story block. Right? Okay. So we have to import our, uh, uh, this file in a story block. After the import, uh, we will have the, uh, this type of filter. Right? Like, any any field, means email, names, etcetera etcetera. Right? And the, uh, now we will move to the plug in part. Right? So plug in so for the plug in part, we we need to find the alternative plug in in a story block that we that we are used to another, basically, CMS part. So we have to find the, uh, basically, from, uh, plug in part. So this is after that, the front end integration, we will do

So detail how? Uh, okay. So timing up. Uh, what is stat it is a strategy you need to apply to optimize the web type, which is, uh, basically rely on any content. Okay. What is the strategy of okay. So and SEO strategy. Alright. So first, I'll explain what is the SEO. Right? After that, we will, uh, basically, uh, list down this strategy. SEO means the search engine optimization. Means, how, uh, how your website will rank in a Google. If someone is searching like, you have a website of clothing and someone is searching to best, uh, summer clothes for men. Right? So your website will rank in a, basically, Google. So that that is, uh, the main work of SEO. Right? So now I'll discuss about the, basically, strategy. Right? See how we can basically optimize the, uh, basically, SEO. So first of all, I'll optimize the, uh, basically, metadata. Right? Including their, uh, basically, title, tags, right, title description, and the relevant key, uh, keywords that is present in your content. Right? After that, we will, uh, we will, uh, make a SEO friendly URL. Right? Means your URL has the, uh, basic keyword, uh, rich keyword rich. Right? And the, uh, uh, it I'll make sure the your engine, uh, visibility, uh, will improve. Right? Okay. And the, uh, your content your content has the relevant part, which is search in the SEO. Okay. I'll implemented the, uh, basically, data structure. Right? Means how your data structure means JSON LD data structure you have or the another data structure we have. Right? Okay. So including your, basically, articles or the product and and the any content. Right? This is how, uh, the data structure will help to search engine understand, contest, and meaning of the content. Right? Uh, basically, this is lead to the enhanced search engine result. After that, I optimize the image also. Right. So image is very crucial to use the SEO part. Okay. So I'll I'll, uh, give, uh, give all the, uh, image to the, uh, caption and the file name as well. Right? Or also I I I also carry the comp sorry. Compressed image. Right? And resize to improve the page load. Right? Our page load will reduce. Right? So we will use the, uh, basically, uh, image optimization also. Right? So we can use the WebPMA WebPAA images also to reduce the loading. Okay. Enable we also enable the sitemap. Right? Uh, I'll generate a sitemap.xml file, right, to your website. If someone is submitting, uh, to the search engine, it will, uh, basically, uh, uh, crawl all the pages and discover, uh, your content. Right? I'll implement it also the, uh, I'll optimize the page speed also, right, by using the your, uh, page CSS JavaScript code and the caching.

Okay. So consider will you take take into account when integration of third party signing services in FGS application secured by TypeScript Intersection. But consider, we will take into account an integration third party and service in the next year's application? What kind of what consideration could you take to account? Okay. Then we are integrating to the signing service. Okay. So okay, in sub in some in, uh, man of the sorry. In many, uh, software, we need to, uh, integrate the sign in with the, like, Google, Facebook, Twitter, right, with our application. Right? So I'll consider a few things, uh, while do this. First is security. Security is the most important thing I I have to, uh, use. Uh, basically, what we will use we will use o auth o auth to front of, uh, authentication protocol. Okay. So, uh, this will, uh, protect our user credential and the sensitive data, right, which is getting from the another, uh, basically application. Okay. So I'll also use the typescript. I'm really oh, sorry. I also prefer the typescript interfaces. Right? K. To define okay. What is the typescript interfaces? It it helps to maintain the type of safety, right, uh, throughout the application throughout the our application and working, uh, with the user authentication data. Okay. After, uh, after using the OAuthO configuration, we are, uh, we are setting the 3rd, uh, basically, party sign in. Right? Like, uh, including our client ID, right, our client secret ID, redirect URL. Right? And the also the scope permission which I which we installed the, uh, setting and correctly configure to enable install authentication and authorization. Right? Authorization, uh, then we also use the middleware part. Sorry. We have to work on the middle middleware part also, uh, implementing the, uh, basically, middleware middleware, obviously, in a node, uh, Node. Js application, right, to integrate the 3rd party. Right? We use we use the token based, uh, system. Right? We will decode the data from our token and the, uh, check the control based permission. Right? Whether the user, uh, has been, uh, edit permission or create permission has or not. So this is how we will do. We install the, basically, the data mapping. Right? How our, uh, interface application means, obviously, we will define the interface, uh, type typescript interface defined in the application. We will extract the relevant user information, uh, like, uh, such as the name, email, profile image, and user ID. Right, from the token, which is stored in the, uh, basically, setting storage for the token. That's we also include the error handling part. Right? There is many scenario for the error handling. So we also ensure the, uh, troubleshooting part and the debugging process. We also, uh, we will consistently use the user experience part. Right? It should be paused. Right? Or the