Image for post
Image for post
Make Gatsby usable by everyone — an exciting future.

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):

  1. Multiple “post” types — blogs (with tagging functionality), event listings and recaps, job listings, team profiles
  2. Multiple documentation-style sites — Lexicon (our design system), Blueprints (our brand style guidelines — with basic auth capability), and our department…

Image for post
Image for post

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.

Image for post
Image for post
Special thanks to Jamie Street, Jimmy Musto, Jens Johnsson, Sergi Viladesau, Princess Buttercup, and all the fine folks at Unsplash for the photos.

Look at all these buttons!

Image for post
Image for post
What about ‘Buttons Large’??

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)? …

One person’s adventures in bringing people together.

Image for post
Image for post
Get it? I’m sorry.

The beginning of November marked my first year as Liferay’s UX Design Manager for North America. As Design organizations are wont to do, we restructured and consolidated some designers from marketing and engineering into a fledgling User Experience team based out of our office in ̶D̶i̶a̶m̶o̶n̶d̶ ̶B̶a̶r̶ Los Angeles.

Spoiler alert: I made a lot of mistakes, but also learned a lot and thought it might be helpful to share some of these things.

Mergers & Acquisitions

(If you read that heading in Christian Bale’s voice — that’s interesting, please continue — this will be my last film reference. Yes, I said film.)

Let me preface this by repeating — I made a lot of mistakes — it took about eight months for our team to get healthy enough to jog. …


paul hanaoka

a short bio

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store