Articles
-
Art Direction with Gatsby Image & the Aspect Ratio Bug
9 min. readI'll be real; when I first entered the Gatsby ecosystem and tried to load my first image, I was like 'whaaaaaaat?'. And if I was that befuddled trying to load a single picture, how in the world was I going to wrangle Gatsby Image into handling fluid art-directed images, compression, and formatting with broad support?
-
Fluid Typography with CSS Clamp() is My New Favorite Thing
2 min. readAccording to Twitter, which is definitely an accurate representation of real life, I’m in the extreme minority of developers who actually enjoy CSS. I got into development (*all those years ago*) by way of design and as a designer first, working in CSS unlocked so much creative potential.
-
Translating Placeholder, Alt & Title Text with React-Intl
6 min. readI'll be real; when I first entered the Gatsby ecosystem and tried to load my first image, I was like 'whaaaaaaat?'. And if I was that befuddled trying to load a single picture, how in the world was I going to wrangle Gatsby Image into handling fluid art-directed images, compression, and formatting with broad support?
-
Building Custom & Localised Error Messages with Joi
11 min. readIn my previous article, 'What I've Learned Validating with Joi', I detailed general form validation that plays to the strengths of Joi in my latest project. But an area of weakness in the library is one I had set out to tackle since - displaying custom internationalisation (i18n) error messages.
-
What I've Learned Validating with Joi
11 min. readI'll be honest, despite all of my experience as a front-end developer I haven't had a lot of projects that dealt heavily with forms and data. Form validation was just something I never really had to work with much. My most recent project, however, is entirely form- and data-driven and I needed a way to easily handle front-end validation. For this, I turned to Joi.
-
Accessible Web Apps w/ React, TypeScript & AllyJS
29 min. readAccessibility is an aspect of web development that is often overlooked. I would argue that it is as vital as overall performance and code reusability. We justify our endless pursuit of better performance and responsive design by citing the users, but ultimately these pursuits are done with the user's device in mind, not the user themselves and their potential disabilities or restrictions.