Do you know how to code, Reader?
I know, I know: we're past the "should designers learn to code" debate by now (or at least, I hope we are). But here's the undeniable truth:
Understanding the materials your designs are built with can make you a better designer.
When we're designing for the web, code IS the materials that our designs are built with. HTML and CSS are our bricks and mortar.
When you understand how the materials work, you can better understand their constraints. What do they do naturally? What requires special care and attention to create the form you want?
And when you understand constraints, you can make more informed design decisions about complexity.
Like, is the experience that custom carousel will give worth the added time it will take to build? Or, could this image have the drop shadow and border radius applied with code rather than exporting it as a PNG to save some kb's and make the page faster?
These small things go a long way in improving your effectiveness as a designer. They also go a long way in improving your workflow with a developer.
If you've found code intimidating, I have some good news for you: you don't need to know how to write code from scratch to gain some of these benefits.
If you learn to read code, you'll be learning how it functions and be able to make decisions around constraints, and also give better feedback to a developer when you review a build of a landing page or site. So don't let the intimidation of learning to code from scratch hold you back from getting a basic understanding of how it all works.
Let me help you get there.
I've made a video called HTML & CSS 101 for designers that breaks down the basics for you from a design perspective. Watch it, and you'll be on your way to knowing how to read code.
Want to move past 101 level understanding and dig deeper? Check out the courses that SuperHi has to offer!
FigJam > Google docs: do you agree?
"This Google doc should have been a FigJam" is something I've found myself thinking a lot recently. So I made it into a meme 😅
"This Google doc should have been a FigJam" is my new "this meeting should have been an email". pic.twitter.com/Hs0KMbv6zB
March 13th 2023
Seriously though, the collaborative enviornment of FigJam's digital whiteboard makes for a much more engaging way to take notes during meetings, or to share an idea. What do you think? When you start to brainstorm a new project do you open a Google doc for everyone to collaborate in, or a new FigJam file?
Speaking of FigJam, you know I made a product to help bring life to your brainstorms, right?
400+ hand-drawn vectors set up as components (with variants!) in Figma for easy access in your design process.
(or if you want to use it outside of Figma, grab it here)
I've spent the past week in the countryside, having escaped the noise and influx of people to the city that happens during Fallas in Valencia. It's been fun to start my days with outdoor workouts and a dip in the pool!
Hope you have a good week,