I worked on a website delivery process for regional financial association websites where each site needed to reflect its own content, brand, culture, regional needs, and client relationship. These were not simple template swaps. Each association had its own identity, and each project involved coordination across design, content, development, and client relationship management.
Before I joined the team, the delivery process was slow because the organization did not have enough Kentico development knowledge in-house. Most development work had to be sent offshore to an external team, which created handoff delays and slowed iteration. The design and content teams were doing what they could with the tools and templates available to them, but they were limited by how quickly technical changes could be made, reviewed, adjusted, and brought back into the site process.
When I stepped into the work, I got up to speed on Kentico quickly and learned how to handle JavaScript integrations in-house. That changed the shape of the process. Instead of waiting on an offshore development queue for every technical adjustment, the in-house team could move faster, test ideas sooner, and support the custom needs of each association website more directly.
I built a wide range of frontend and CMS integrations inside Kentico, including interactive components, page behavior, forms, content modules, calculators, accordions, tabs, custom layouts, reusable snippets, and other pieces that helped design and content move with more flexibility.
But the bigger shift was not just that I could do the work myself. I helped move that capability into the team.
I started teaching the design and content team in a workshop style so they could better understand what was possible, how to work with the system, and how to iterate more effectively. Over time, those workshops evolved into onboarding and training materials. I also trained two additional developers to work with the Kentico system in-house, reducing the dependency on one person and making the process easier to sustain.
For comparable association-site work in this program, timelines moved from roughly 22 months to 2–3 months after key Kentico and JavaScript capability moved in-house. The change depended on reduced queue delays, faster design and content feedback, reusable technical patterns, and training for the people closest to the work; it is not a universal website timeline.
The process also supported closer collaboration with client relationship managers, more design flexibility, easier maintenance, and smoother onboarding for people joining the work.
A separate example of that growing in-house capability was a national association locator. I built the JavaScript functionality that helped users find the regional association closest to them, turning location-based discovery into a more useful digital experience.
This project is one of my favorite examples of repeatability without making the work generic. The association websites were still distinct. They still needed their own content, branding, culture, and client context. What became repeatable was the delivery capability: the technical patterns, training, shared understanding, and in-house process that helped the team move custom work forward faster.
