Lombiq’s Journey with WTW’s Client Portal

WTW is a multinational company that provides businesses with various services such as insurance brokerage, risk management, and human resources consulting to help them manage risks and optimize their operations. Recently we had the opportunity to implement a specialized Orchard Core-based Client Portal for them.

This portal, targeted towards insurance companies, was intended to be a replacement for an old portal used to download on-premises software & license keys, raise support tickets, and read knowledge base articles. WTW chose us to be partners on this project because we are large contributors to the open-source community, and found us to be knowledgeable and experienced based on our previous work. Our flexibility during the initial conversations was also a huge factor in their decision. With this opportunity, we got the chance to improve our experience in developing a user-friendly portal with a modern front-end framework and how it can be integrated into Orchard Core’s content management capabilities.

The Client Portal, which was designed to be used by the customers, is just one crucial component of an overarching system architecture. The rest of the systems were responsible for managing software and license keys by administrator users. WTW specifically chose Orchard Core for this portal because of its robust content management capabilities. Content manager users now create announcements, external training materials, manage the product and services catalog, and arrange different widgets throughout the webpages using the Admin UI. Other components on the platform pull in information like product download links or license keys from other parts of the WTW system using web APIs.

Given that it's a customer-facing portal, user experience was a priority. While it’s always a good idea to rely on Orchard Core’s display management the only way to use that is with page reloads during navigation between pages or filtering. Paginations are filters on the pages that should always be asynchronous, so we had to come up with a solution that uses modern front-end technology along with Orchard Core’s great features. During the course of this project, we’ve developed an open-source Vue.js module for Orchard Core to make user interactions smoother while still maintaining the built-in display management capabilities, such as widget and menu functionality. For quality code and maintainability, we utilized Lombiq's .NET Analyzers, Gulp Extensions, Helpful Libraries, Helpful Extensions, and NPM MSBuild Targets. Stability was critical, so we implemented several UI tests using the UI Testing Toolbox, ensuring they were executed before introducing a new feature using our reusable GitHub Actions.

It was an exciting project and we delivered it on time. While the final steps on the rest of the architecture are being completed the whole portal is gradually being rolled out to users during the summer of 2023.

If you're thinking about integrating a powerful CMS like Orchard Core into your architecture, we're here to help. We can either do the work for you or guide you through it in our consulting calls, just get in touch with us!

zoltan.lehoczky Case study Development Orchard Core WTW Insurance Willis Towers Watson United Kingdom

Other recent posts

Clear Specs Go a Long Way: Inside Our Three-Year Orchard Core Collaboration with Fieldman

What happens when your application needs both stability improvements and new features at the same time?

That was the situation when Lombiq joined the Fieldman project. Their Orchard Core-based web application already had established business logic, but it required bug fixes, upgrades, and further development.

Fieldman is an American software company that helps local governments and utility vendors manage all types of assets, jobs, and field projects.

Your analytics isn’t broken. It’s incomplete.

Web analytics is the foundation of modern marketing decisions. But today, a growing portion of user behavior simply doesn’t show up in your reports.

Ad blockers, browser extensions, and privacy tools can strip tracking parameters or block analytics scripts entirely. The result is incomplete campaign data, misleading attribution, and decisions based on partial visibility.

For marketing and product teams, this is not just a technical inconvenience. It is a business risk. Campaign performance becomes harder to evaluate, budgets are harder to justify, and growth decisions rely on guesswork instead of evidence.

Bringing Orchard Core into the classroom at Óbuda University
Since 2013, we’ve been working with Óbuda University on a hands-on way to teach web development. What began as a course built around Orchard CMS later evolved into an Orchard Core-based subject, giving students a chance to learn by building something that could actually work in the real world, not just completing classroom exercises.We asked our colleague Gábor Domonkos, who has led the collaboration for years, to walk us through how the course started, how it works today, and what students usually take away from it.– How did this collaboration start?At first, the university had a Hungarian, non-developer course focused on Orchard CMS and DotNest, Lombiq’s hosted Orchard platform. Students built sites through the admin UI, which was a good introduction to content management. But once Orchard Core arrived, we saw a chance to create something more ambitious: a developer-focused subject where students could also write code and go beyond the basics.– What changed with Orchard Core?Orchard Core made the course much more flexible. Students can now learn not just how to use a CMS, but how to extend it, customize it, and build on top of it. That meant more room for customization and coding. It also gives them a much more realistic picture of what it means to develop with a modern CMS on ASP.NET Core.– How is the course structured?The semester is built around a few milestones. Early on, students choose their project topic and define the basic idea. Midway through the semester, they should already have a working site with real content. By the end, the project should be close to final, both in structure and content.The later stages are mostly about making sure students stay on track. If they need help, they can share a short update so we can spot problems early and steer them in the right direction. Some students also choose to demo their project before the official deadline.– What do students usually build? Any favorites?That depends on which version of the course they take. In the non-developer version, students often build sites with forms, search, taxonomies, and content workflows. In the developer-focused version, they go further and build custom modules, themes, and more advanced functionality.One project that stands out was a volunteer platform. Organizations could publish volunteer opportunities, and users could browse, apply, and track their enrollments. It was a nice example of how Orchard Core can support a real, practical use case without adding unnecessary complexity.– Has this led to anything beyond the course?Yes, some students later became our colleagues at Lombiq. By the time they finish the course, they already know the basics of Orchard Core and have built something real with it. More importantly, they have seen what it’s like to work with a real open-source ecosystem, not just with a classroom demo.– Where should someone start if they want to learn Orchard Core today?If someone wants to learn Orchard Core today, Lombiq has a few good starting points. Dojo Course 3 is a full video course on YouTube that walks through Orchard Core for both users and developers. We also maintain the Lombiq Training Demo for Orchard Core on GitHub, which is a functional module with heavily commented code to help developers understand how Orchard Core works in practice. And beyond that, Orchard Dojo regularly publishes tutorials, tips, and other learning resources for the Orchard community. For us, that is the best proof that the collaboration works. Students gain practical experience, the university gets a more hands-on subject, and the industry gets people who are better prepared for real projects. We believe more universities could benefit from this kind of collaboration, whether with Orchard Core or other open-source technologies. And if you are exploring something similar, we are always happy to share what has worked for us so far.

Event management backend for one of the largest retailers
Avastec, a UK company, approached us to continue the development of their existing Orchard Core-based headless backend utilized by the event management site of one of the world's largest retailers. It was already in use with a publicly accessible Node.js-based frontend. The end client urgently wanted some new features, with follow-up tasks to optimize the system's performance, and keep the app up-to-date while maintaining the integrity of the user interface. Our initial task involved the transformation of data migrations from the simpler recipe-based paradigm to a more structured code-based approach. This transition aimed to enhance the traceability of modifications the development team applied. Simultaneously, a suite of UI tests was integrated into the workflow to uphold continuous code quality assurance. Leveraging the flexibility of Orchard Core's migration API, we executed this pivotal migration process without it negatively affecting users. Since then, we've delivered a lot to meet various user requirements, including event ticketing, integrating with a GDPR compliance API, and launching the site for another brand of the end client. One particularly interesting task was the implementation of QR code-based entry management, which we also supplemented with UI tests using the Lombiq UI Testing Toolbox. We've also implemented a feature to let the app use a fake video feed during tests, what we also demoed during the weekly Orchard Core podcast. From our other open-source projects, we also utilized Lombiq Helpful Extensions, as well as Lombiq Hosting - Azure Application Insights, since the app is hosted in Azure. This is what Steve Taylor, CTO and Founder of Avastec says about our joint work: Working with this team has been a genuinely positive experience from day one. They quickly understood the complexities of our existing Orchard Core setup and delivered improvements without disrupting a live, high-traffic platform. Their ability to balance rapid feature delivery with long-term maintainability and performance has been particularly valuable. The introduction of structured migrations, robust UI testing, and innovative solutions like QR-based entry management significantly elevated the quality of the system. They’ve consistently demonstrated technical expertise, reliability, and a proactive mindset, making them a trusted partner in the ongoing evolution of our platform. Thanks to Orchard Core, UI testing, and innovative feature implementations, we effectively addressed Avastec’s challenges and delivered a significantly improved event management backend. It continues to serve the end client, with us working on improvements to this day. Do you want to launch and event management platform on Orchard Core? We have actually built several more too, get in touch with us!