If you’ve followed me for any length of time on Twitter, you’ve probably seen multiple professions of love for Gatsby. When I saw they were hosting a one-day, single-track conference about 20 miles (only 2 hours in LA traffic!) from my house, I couldn’t not attend.
Liferay.Design has been running on Gatsby since early 2018, and despite not having a “real” dedicated web developer, we’ve managed to build a fairly large site including (but not limited to):
The Liferay Design team made regular use of Liferay’s developer-centric deployment platform, WeDeploy. Static sites like our primary domain and Lexicon, as well as standalone apps like our NA team dashboard and our Career Path tool (a work in progress), and small pages like our web assets repo page (very much a #wip) were hosted and managed there. It was great to have a single place to handle these projects, which were all built with different tech stacks.
When the WeDeploy team announced that they were shuttering the service, we were at a loss for where to move everything. We did a little research, compared a few services, and thought that it might help other teams who were using WeDeploy (and even people who are just trying to decide between existing services) choose from one of the many options available. …
If you’re as lazy as I am, you’ll definitely want to read this to learn how to set yourself up for hyper-efficient changes and updates to your Figma components. With all the time you save, you can do what I do and browse Unsplash’s cat photos for hours on end.
Look at all these buttons!
If you’re new to Figma, or the atomic model, you might be thinking…okay 1 button x 4 states x 4 levels x 3 configurations…carry the 3…for those of you keeping score at home, that’s 48 components per size!
If you need to change the padding, and it takes you 15 seconds to do it per element…you need to budget 12 minutes for that. Okay thats not so bad…but how many of you only have buttons in your mockups (not looking at you, landing page marketers)? …