John Gordon
Web developer specializing in frontend and marketing.
New to Contra
John is ready for their next project!
Ongoing project at Healthy Hearing to update infrastructure. My role is to build the frontend views to use more modern templates for our CakePHP upgrade, and maintain or improve our Lighthouse scores.
Rebuilt all pages (including public facing and an entire admin only portion), side panels, navs, modals, badges, our content WYSIWYG, JS functionality, schema, and probably a whole plethora of other features that escape me at the moment.
This is the dev site, and my portion is 99% finished. Hoping to roll out soon!
0
7
One of my more grueling projects. The site had 2 large JavaScript files, mostly comprised of spaghetti code jQuery written by a PHP guy. I got rid of almost every single scrap of jQuery I could find, rewrote it as ES6+ JS, broke everything out into organized modules so each page got code that was actually relevant and not one giant bundle, and installed Node and Webpack so third party libraries didn't have to be manually downloaded and added to the directory anymore. All before AI was there to assist and make nitty gritty work like this easier. Just docs and Stack Overflow.
Man, I feel old.
6
38
My current work in progress (some elements censored per my contract stipulations), a React web app utilizing Tailwind and Vite for a restaurant review project. I've built out all the Figma views provided to me, including UI elements like a review drawer, three navs and a retracting search bar, added as much frontend functionality as I can, populated my local Postgres DB with mock data, and built several Jest test suites.
I've gotten so far ahead in my work I'm starting to contribute to the backend code 😂, currently building new endpoints and services in NestJs. It's outside the scope of my contract but dang it, it's fun to try something new, and I'm enjoying my work.
14
80
Test, test, test, and then keep testing. Leverage A/B testing to make your site more appealing to your users. The site I'm working on is a healthcare site catering to older users. I set up a test increasing default font size sitewide to see if there was an improvement in conversions and engagement.
Overall engagement increased 13%, simply from increasing font size from 16px to 20px. KPIs saw improvements ranging from 6% to 10%, with one high value KPI increasing by almost 60%.
The font increase also has the added benefit of making accessibility requirements easier to meet, as font color and background color won't need as high of a contrast ratio with larger fonts.
I'd recommend larger fonts for any site with an older audience, or at the very least designing your site to account for users who may have their browsers zoomed in.
1
11