Ayush Kumar Papnai

Hi. Uh, my name is Ayush, and I am currently working as a senior front end developer at, uh, Zoper, and my current experience is, like, around 5 plus years. And I have currently been working at Zoper, uh, for around, like, 6 to 5, uh, projects, which 5 to 6 projects, um, which includes a drag and drop, uh, form builder, um, that, uh, provides, uh, product managers and the business team to create the flows and new UIs, um, by drag dragging and dropping immediately. And that also, uh, helps the business team to create these flows really quick, and they can even create dashboards from it, uh, form, uh, are, uh, well equipped with, um, well equipped with validations and all. We are internally using React JS and no other library is being used, uh, other than that. Um, for React with React, we are using Formic, uh, that provide React Hook form, sorry, uh, that provides validations and basic upload functionalities and all. Thanks.

How can CSS grid system only integrate into a complex application to ensure consistency and maintainability across various modules? Okay. So, uh, CSS grid systems can be, like, uh, basically, we can create, uh, different classes, uh, for, um, CSS grid maintaining it cons consistently across the project. And the basic thing that we can do is we can create, um, just imagine the grid, uh, as a 12 column, um, grid, and rows can be a number of rows. And we can, uh, create classes from, uh, ranging from column 1 to column 12. And, uh, then immediately, um, like, we can reuse them for, um, like, across the projects, um, just defining a grid, um, a class, and then adding up the columns. Like, uh, one element can flex to how many columns, like, uh, can be displayed on into how many columns. So that's how we can create a grid system that, uh, most of the designers use are using Figma.

Uh, so for our to automate, uh, the deployment process of any single page application, uh, using Amazon Web Services, like, we can basically, um, go we can use a workflow, uh, that gate or Bitbucket, uh, provides us, and, uh, we can continuously vouch for new updates. And, uh, if you want to, um, like, upload the new development, like, deploy the new deployment immediately, we can create the whole workflow like that. Or even we can use Jenkins as well, uh, for the same thing or, like, any CICD pipeline software like Jenkins. Yeah. And, um, also, if we are using Bitbucket or GitHub, uh, like, that we always use, so we can directly create workflows. That's a better way to, like, streamline the process of, um, uploading a new deployment to AWS servers. And, uh, yeah, that will, like, uh, almost remove all the, uh, dependency on developers or DevOps to deploy a certain project to production or any stage, like dev staging or production. But, um, the one thing that we can do here is, like, we can also optimize this. We can, uh, depending on the scenario use cases. If it's a marketing website, we can we can, like, uh, use a time that could be, like, um, a day half. The changes would deploy on a half day basis or a time would be there, uh, because marketing websites require frequent updates on, uh, in like, to be deployed with changes for AB testing and all. But, uh, a better way for other applications like dashboards and, uh, other user facing websites, we can add test cases as well, uh, uh, into our workflows and pipelines and then deploy them at nighttime or any convenient time that we think, like, our users are user count is really low. And, uh, that will help, like, very perfectly for any, uh, big, uh, like, we can that that's how we can, uh, ignore the downtimes and all. And for monitoring purposes, we can definitely use some monitoring softwares that are available in the market. Uh, though, currently, I haven't used any, but, yeah, we can use, uh, these as well.

Can't find some of the final condition which is returning based on user roles. Now we have to issue that. So

What what my third model used to test? Does Calabrio react? It is application that accepts only using AWS backend services. What would be?

Describe how you would implement that. How you would do a multi tenant content architecture. Yeah. So, uh, like, for, uh, implementing a highly configurable multi tenant, uh, front end architecture, what we can do is we can, uh, definitely create modular, uh, like, we can use modularity here. So, uh, the very basic thing is, like, there are multi, uh, like, there are multiple people that would be using, uh, a particular application. So first, we can what we can do is we can divide the, uh, front end, um, base it based on the, uh, users that are there. So we can use the role based authentication system here. So, uh, what we can do is we can, um, create, uh, permissions. Uh, like, every role would get um, access to some particular route. So we will have to, um, bifurcate those routes, um, and add protected and, uh, protected routes and or or routes, uh, for those particular roles. And as well as, uh, once the user enters the application, let's say we have an application that would, um, be managed by, uh, let's say, it's a car, uh, Uber like thing. So if there is a guy who is managing all these Ubers, then, um, the Uber application user would be, um, one front and the other, um, back on the back end, there would be an admin that would be handling all these, uh, Uber Riders. So let's say those, uh, these are 2 roles we are, um, having. So once, uh, any of them, uh, logins to the particular role, particular, uh, dashboard or the application, First, we would, uh, check if the user is that's, um, role based authentication system. Uh, it's called, uh, yeah, the role based authentication system. So, uh, what we can do is we can just, um, on the login API, the response where we can send a business rule that the particular, uh, the entity would be using. And then according to that, after login, we can bifurcate, um, the protected routes, like the, uh, authorized ticket routes that, uh, this user will only be, uh, authenticate, uh, this authenticated user would only be able to access those particular routes that, uh, he or she, uh, is to be assigned, uh, has has been assigned. And other than that, for implementing multiple and front end architecture. And, uh, then if those, um, we can use lazy loading for components that are not being loaded for that particular, uh, role, and that would, uh, like, significantly decrease the amount of load that application takes, uh, on the load time. The time would be decreased, and that's how we can definitely check, uh, if the we can, like, make it highly configurable. And, also, for permission, we can add permission page wise permissioning or, like, feature wise permissions. Um, so we can create a knob, like, map of each, uh, feature, and that feature is allowed to which role. So on the time of creating that particular role, we can just, um, like, if the screen is shared between 2 users, then other than that, it's not required.

And the CSS code went for a response from the out. Use the CSS grid system. Uh, identify the possible issues with the grid template column definition. Okay?

Techniques would you apply to optimize server handling? Warrior applications for enhanced SEO and performance. And so for, uh, the server side handling technique, we can

Yeah. For, uh, accessibilities, um, I have been, like, working with banks, uh, so very closely. And for with the bank, uh, what we, uh, face mostly is the user, uh, coming to the website and really struggling with the, uh, basic key key presses and other things, like, if they're, um, doing it, um, like, if any user is coming there. Now what happens is when a user tries to enter a website, then

I am just completed.