TL;DRYou may have started noticing more updates in the UI recently. And we have just updated the header!
We’ve been working pretty hard on building new awesome features and improvements. Some of them are meant to be invisible yet super helpful: feed improvements or upgrading some of our infra. But we’ve also made some changes that affected visuals.
Like in many projects, the front-end part of a codebase is… well… not ideal. We have tons of CSS files, lots of spaghetti code, duplicated styles, and much, much, more…
It’s a classic scenario: the feature or view needs to be built. The Dev or Designer decides to write super short and simple front-end code to ship a feature fast. And 2000 lines of code later you just can’t go back :)
Taking a more holistic approach is actually what we’ve been trying to do. We’ve started building our own Design System. It includes not only design guidelines, but also front-end documentation of how to use the styles and components.
Overall, this is our approach (I will write more about our Design System in the future):
- We now have real components and views built in SCSS (well, just a few of them, but that’s a good start!).
- We also have utility-first classes ( TailwindCSS – does that ring a bell?) ready to be used anywhere in the markup.
- At the same time 95% of our code is legacy code, not following any rules or guidelines. We will be slowly updating that alongside releasing new style.
Which is a good segue to…
One of the very first elements that we’ve decided to update is our header. You may notice it looks slightly different than couple days ago (if not, hit the hard refresh… If still nothing, I could have broken something and we had to roll it back :D). It’s just a refresh, not complete redesign or anything. But we hope you’ll like it! There’s much more coming and this header update is just a teaser.