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!

mark.bartha Case study Development Orchard Core WTW

Other recent posts

The European Accessibility Act came into effect today. Should you care?

With the European Accessibility Act coming effect into today (June 28th, 2025), we've reached an important milestone in (web) accessibility. As the official announcement states:

"The Act mandates that a range of products and services such as consumer electronics (TVs, smartphones, computers, gaming consoles, etc.), ticketing and vending machines, websites and mobile acts, among others, comply with accessibility requirements for persons with disabilities."

An important clarification here is that the EEA "applies to businesses operating in key sectors such as banking, transport, telecommunications, e-commerce, and consumer electronics [...] for new products and services introduced after 2025."

Now, you might think that "OK, but my service has been running for years and I know my customers, do I really need to worry about this?". Of course, you should! New products/services launching under the effect of the EEA have a competitive advantage of catering to a wider audience, including those not directly affected, but caring about (or taking care of) those who are.

Since Lombiq is a web software/services agency, we'll focus on one particular aspect of accessibility: web content accessibility. We started rewriting all our websites 2 years ago and web content accessibility has been a guiding principle of our UI/UX design from the very beginning (you can also check our case studies). We can't really put any metrics behind its usefulness and we didn't care about the ROI; our open-source DNA compelled us to do so to make sure that the knowledge we share is as widely available as possible.

But: Making your website accessible is not a one-off effort - you also need to make sure that your website remains compliant. Fortunately, neither did we or you have to start from scratch with all this: Compliance with EEA is covered by compliance with WCAG 2.1 Level AA (at the time of writing this article) and there are a multitudes of tools to help you in this effort.

That's why we developed a component of our UI Testing Toolbox library to easily integrate automated UI tests into any ASP.NET Core application that allows you to verify WCAG-compliance. Check out our sample UI test - it really is this simple! We continuously run such tests in our own CI workflows, as well as in our clients' projects.
Let us help you help us all!

Happy complying and compiling!

Migrating the homepage of the Orchard Core SaaS DotNest to Orchard Core

Following the migration of lombiq.com, Git-hg Mirror, Hastlayer, and Orchard Dojo from Orchard 1 to Orchard Core (and also the redesign of lombiq.com and Orchard Dojo), we had only one site remaining that was still running on Orchard 1: DotNest.com. While you could create Orchard Core sites on DotNest for years, until now, the DotNest website itself still ran on Orchard 1.This marks the end of an era. Now all of our sites are running on Orchard Core, which offers better performance, modularity, and development experience than Orchard 1.Furthermore, we fixed some web accessibility problems on the site and added UI tests to make sure nothing breaks and affects you as a user.We utilized many of our open-source modules, including Lombiq Privacy, Lombiq Helpful Extensions, and utility modules like Lombiq NodeJs Extensions. For the themes, we built upon the Lombiq Base Theme. Lombiq Helpful Extensions played a crucial role in this project (and in the other ones too), as there was a significant amount of content to migrate. Leveraging the Orchard 1 Recipe Migration feature, we transferred Orchard 1 content items—such as blog posts, pages, and even users—to Orchard Core. Additionally, we retained the search functionality on the Knowledge Base page, now powered by Elasticsearch and the commenting on blog posts with Giscus. Of course, while working with these modules we always make sure that any enhancement that comes to mind is added to them and any bug that we find is patched. So, the wider Orchard Core community benefits from each of these projects too.This is a migration, where if you notice nothing it’s great because we migrated a lot of backend code and the goal was to keep the functionalities of DotNest, without breaking or changing anything.Migrating to Orchard Core not only brought performance increases but also added quality of life and security features, like two-factor authentication. The new foundation of the site opened new possibilities for us to bring you a better version of DotNest.With DotNest now running on Orchard Core, we’ve completed our journey of modernizing all our sites. This migration wasn’t just about keeping up with technology—it was about ensuring a smoother, more secure, and future-proof experience for our users. Although most of the changes were behind the scenes, the result is a faster, more reliable DotNest that preserves all the features you rely on while setting the stage for future enhancements.Are you still running Orchard 1 apps? Contact us to see how we can help you migrate it to Orchard Core too.