Skip to main content

NUOREACT - Nuomorphism in react simplified

Last month (i.e May of 2020), during the lockdown, I started wandering over the npm community and the ways to build an npm package, so that I have my signature on the open-source world.


I was working as a full stack developer then, and my front-end work was in reactjs.


Initially, I was frightened to develop something in react but then I fall in love with the idea of reactjs. 

My work became my hobby and loved the idea of reusable components with less amount of code.


The component re-usability and the ease of developing one ignited an idea of another npm package. But unlike last time (LNFC), I was not so set on building one npm package for react components.


So I started learning how to create one and then managed to do so.


The package is called nuoreact, simply an acronym for nuomorphism and reactjs.


Nuomorphism is a design concept, that is well explained in this blog post here


I was intrigued by the concept of nuomorphism, and the mediocre nuomorphism component packages in react, enlightened me towards my second npm package.



Nuoreact - helps in creating nuomorphism inspired common elements, such as a switch, button, card etc, into life using react components.


Take a look into nuoreact, and feel free to provide me with feedback and pull requests on Github.



Comments

Popular posts from this blog

AI. Will it replace us or...?

AI!! The buzzword is too hot in the market nowadays. Do you have a technical product or an idea? If it doesn't have AI in it, then chances are it's not going to be sold like hot cakes. That is how things have changed lately. It is no wonder why me and my colleagues at Gelato want to see what AI can do in a niche department like customer support and service. And that is exactly what we did. For a company like Gelato, which is in the market for production-on-demand, there are a lot of customer questions you need to answer. It can be related to products, queries about shipping and pricing, and so on and so forth. Thus, our customer support team is always happy to help with these recurring questions. Let's take one example. A customer asked us, "Do you ship to Norway?" Now that is an easy question to answer if you have the knowledge written somewhere where you could refer to it and say, "Yes! As a matter of fact, we do." Following the same thread, the next q

A smoooooth operation....

 Backward compatibility...   A word that I used to hear when I started my career. You design your APIs with backward compatibility in mind, don't break anything when you are upgrading, think about this, think about that etc. Well, those teachings from my previous mentors didn't go in vain, as I made a fundamental change in how we report problems @  Gelato .    You see recently @  Gelato , the CS (Customer Support) team moved from A ticketing management system to B ticketing management system, which is a monumental task for all the people involved in the CS team. Even though the fundamental concept remains the same the places, the attributes the concepts, and the naming of different attributes all change if you have this transition. And thus it was a big change for the whole company.    After the decision was taken, the first step was to create a well-written transition document, which the good folks at the CS team tackled. Special thanks to  Bartosz ,  Kyle  and  Anastasiia  fo

My experience with the Golden signals

In June 2022, I embarked on a quest for a new job opportunity. Fortunately, this endeavor began just before the global job market experienced a significant downturn. I must admit, I faced my fair share of rejections during this period, but I also had an epiphany. It became evident that there was so much more to learn and understand in the world of technology. Coming from a small service-based company, I had encountered limitations in terms of how much I could learn on the job. However, during interviews and conversations with senior developers, I gained valuable insights into the architectural and technical decisions made by teams in various companies. One such company that left a lasting impression on me was Delivery Hero. Their technical blog posts provided a wealth of information, especially for someone like me, transitioning from a smaller company where projects had minimal daily active users compared to the scale of Delivery Hero. One particular blog post that caught my attention