We've all been there: you open Google looking for "web 3" for the first time. You open the first credible article and read the first paragraph — you find the word “blockchain.” And you think, “What is that? Oh, it has a link!”

When choosing the tech stack for a project, we often ask ourselves what kind of website we'll be building to better assess the right options for the project.

And that's why Design Systems are part of our core strategy to build top-digital products. They work as a framework with a high impact on increasing the consistency and speed of software development. Let's see why and how Pixelmatters uses it.

Writing is an inherent habit in our processes, and one of our oldest practices is the Asynchronous Design Presentation. There are several ways to present your designs to your client, but this one is undoubtedly one of the most powerful and effective. I will talk about Pixelmatters’ writing processes, focusing on the Design subject.

During the execution of our Organizational Model project, we felt the need to write down the desired Pixelmatters' team cultural profile key traits. And here they are.

Have you ever wondered how to develop a front-end project without relying on the API being ready and available to fetch data from? In this tutorial, I’ll share different approaches to how you can do just that, starting by setting up a mock server and then showing how to integrate the mock server into multiple front-end environments — development, test, and component development environments. Here we go!