I led the development of a set of new sites for the University of Pennsylvania. They needed a system that allowed for multiple sites to co-exist in the same Drupal installation without being in a Drupal multisite configuration. To accomplish this, I implemented a taxonomy-based sub-site system. Individual pages could be tagged with the appropriate taxonomy to include them in the desired sub-site.

Additionally, the new sites had considerable design overlap, so I implemented an inter-theme code sharing framework that allowed sub-sites to branch from a main theme. This system went on to be used in the future to quickly build new University of Pennsylvania websites with similar designs.

Some of the sites included in the framework:

• Penn Global
• International Student & Scholar Services
• Penn Abroad
• Global Support Services
• Finance & Administration
• Student Registration & FInancial Services

While working at Eastern Standard, I developed both Wordpress and Drupal frameworks to streamline development efforts across the team.

Some of the code-specific benefits of the frameworks are:

• Single-folder components
• Common template base components
• Pre-configured build tooling
• Commonly used utility functions
• Compatibility polyfills
• Custom plugins/modules
• Standardized code architecture
• Defined git workflow

The frameworks are more than code; they are integrated into Eastern Standard's project workflow. I led meetings where we brought together the leads from design, user experience, and development to discuss changes and improvements to the frameworks. I built an Airtable to organize our project requirements into one central location. I also wrote documentation for developers and non-developers explaining functionality and how they could use the frameworks in their roles.

Over the years, I witnessed other developers attempt to create frameworks that would increase efficiency through a shared system, but all failed to achieve adoption because they were not easy to implement or strayed too far from existing processes. Through these experiences I learned how important ease of adoption is. When I had the chance to implement a system of my own, I focused on the user experience for my colleagues. This was key to the success of my frameworks.

These frameworks have been in use for over three years and are the foundation of most projects at Eastern Standard. To this day, the team continues to gain efficiencies from their use.

Cornell Law School is one of many WordPress builds I worked on over the years at Eastern Standard. I worked with developers, designers, the project manager, and the QA team to develop this website as a custom WordPress theme.

Cooper Health is one of many Drupal builds I worked on during my time at Eastern Standard. The project involved building a two-site multisite. The sites shared many design elements and had slightly different sets of available components. Additionally, I implemented custom modules that integrated with third party API services. I worked with developers, designers, the project manager, and the QA team to help develop these custom Drupal websites. I also handled technical communications with the client stakeholder group.

I noticed that most methods for disabling scrolling had layout shift issues, so I built my own.

The script works by first calculating the width of the scrollbar. This is key to ensuring compatibility across devices with different scrollbar types. Then it displays a pseudo-element to occupy the space created when removing the scrollbar. The pseudo-element takes the appearance of a disabled scrollbar (when applicable). This prevents layout shift and makes the removal of the real scrollbar less jarring.

I have often found myself wanting to transition an element's dimensions to and from 'auto'. This comes up when opening an element with an unknown height, like an accordion or a navigation. I built this JavaScript utility to handle this use case.

Transition Auto works by first calculating what the dimension of the element would be at 'auto'. It then sets the element to that value, enabling CSS transitions. Then, it waits for the transition to complete before setting the element to 'auto'.