I took over an existing Gatsby and WordPress website, rebuilt much of its interface, separated shared CSS from component JavaScript, and created contact and product-support journeys. The changes were released to production.
Main developer responsible for ongoing support and development.
Take over an existing Gatsby and WordPress website, restore unreliable parts, and continue developing it. The original architecture had been designed by another developer. My work was to understand that system and improve it rather than claim its initial design.
I reworked the build and delivery of shared styles. SCSS was built separately through Webpack before the Gatsby build, and production pages loaded the resulting stylesheet through a regular link element. This removed the dependency between loading shared CSS and loading component JavaScript.
The changes were released to production and used by the company. My contribution combined recovery of an inherited website with new support journeys and ongoing maintenance. No numerical performance improvement is claimed for this project.
I reworked the build and delivery of shared styles. SCSS was built separately through Webpack before the Gatsby build, and production pages loaded the resulting stylesheet through a regular link element. This removed the dependency between loading shared CSS and loading component JavaScript.
I built a contact page for new development enquiries and product-support requests. Links from products could open the relevant tab and preselect the product type and product, so customers did not have to find them again. I implemented dependent fields, submission states, errors and completion feedback, sending the forms to Contact Form 7.
I substantially reworked the shared metadata component, including titles, descriptions, fallback values, Open Graph, canonical links and page-specific structured data. I also addressed scroll jumps around the support widget and built release notifications using WordPress content, with rules for when to display them and cookies limiting repeated appearances.
The changes were released to production and used by the company. My contribution combined recovery of an inherited website with new support journeys and ongoing maintenance. No numerical performance improvement is claimed for this project.
Main developer responsible for ongoing support and development.
Have a project, a technical challenge, or a collaboration in mind? Send me a message.
