Smithsonian Folkways Recordings now upgraded to Orchard Core

If you like music – and, truthfully, who doesn't? –, we have some good news for you: you can now browse and license music on an Orchard Core-based platform! This is brought to you by the long-standing collaboration between Lombiq and the Smithsonian Institution, which has been engaged in a working relationship with us for several years now. The sites of the Smithsonian Center for Folklife and Cultural Heritage were made using Orchard 1, which we had a hand in creating all the way back in 2017. These Orchard-powered sites also include the home of the Smithsonian Folkways Recordings, which is now running on Orchard Core instead!

Smithsonian Folkways Recordings homepage

Folkways, with music and Orchard at its core

With Orchard Core offering an ever-growing number of benefits over its predecessor, including various performance improvements and a more user-friendly UI, the time to upgrade from Orchard 1 drew near by the end of 2021. Due to our long history with the Institution, we had the opportunity to participate in this project too.

Lombiq took a major part in the migration process that was ongoing earlier this year. This included updating the existing codebase to modern standards using the latest C# language features, re-implementing our Content Editors module to make it Orchard Core compatible, as well as adding UI testing to easily spot regressions. The application also makes use of several of our open-source projects such as Helpful Libraries, Helpful Extensions, Gulp Extensions, and NPM MSBuild Targets.

The new Folkways site launched in July and can be found on our showcase website Show Orchard as well.

This is what Toby Dodds, Technology Director at Smithsonian Folkways Recordings, had to say regarding our collaboration:

During the past year we’ve had the pleasure of working collaboratively with Lombiq to upgrade our backend CMS from Orchard’s 1.x to its more modern 2.x version Orchard Core – based on Microsoft’s Dot.Net Core. This was a complex and difficult project, but essential as well, and once again we feel lucky to have been able to work through it with Lombiq. Anyone who works around Web or IT systems knows that they are not static and always grow and expand in complexity. Collections of data grow as do the number of fields. Our collection database, which is now 20 years old is at the core of our whole enterprise and represents millions of pieces of information. Years ago, we determined that we could leverage Microsoft technologies and Orchard’s CMS to manage that data while simultaneously supporting our website. This strategy has paid off and we have been able to thrive as a business, generating revenue through sales on our website, licensing opportunities, in-kind donations, and through the distribution of our catalog to outside digital music services. All this business is data-centric and working with Orchard has given us total control of our data landscape.

A big challenge, and a breakthrough, of Orchard Core is that data is accessed in a code-based way which results in better performance but required us to complete a complex migration of our data from our 1.x database held in MS SQL Server. Thankfully Lombiq was ready to take this on, helping us build a data migration process that worked like a charm and was a bridge between the old and the new. We were also able to retain access to our data in SQL, allowing us to keep our existing integrations, and the ability to query our data directly when necessary. Because data is managed within the application layer now, we have also leaned on Lombiq to develop a set of tools to Import, Export, and Update our collection using Excel spreadsheets. Our data life has gotten easier as a result and we are now better prepared to acquire, process, and distribute recordings and collections moving forward. Orchard Core represents not only a step forward for our website but also for our collection management work as well.

Specifically on the website we have also been able to take advantage of Orchard Core’s improved speed to produce new tools for browsing the collection.  Being able to browse and filter thousands of releases in a nanosecond is cool, no matter how you slice it. Additionally, this new speed on our website is opening a door for us to introduce a streaming audio player that depends on AJAX to maintain a persistent audio listening experience while browsing the site. This only works well if pages load quickly and do they ever! Getting to streaming is a key priority for us and now we expect to make that available to the public next year.

In summary, this has been an innovative and productive period for Folkways and now that we are in Orchard Core, we are looking forward to all the benefits that will come from this hard-fought upgrade. Our success here is thanks to Lombiq who’ve had the skill, vision, and patience to work with us to overcome big challenges and get the job done.

You can also check out a demo video of the app and our experiences developing it here.

As Orchard Core grows in popularity, so does our experience with it. If you too would like to enjoy the various improvements the platform offers, don't hesitate to reach out to us here.

gabor.por Orchard Case study Migration Development Smithsonian Institution Orchard Core Orchard Core Migration

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.

Municipal government permit management run on Orchard Core - GovTech company case study
Governments use Orchard Core too! Even in this blog, we've seen how Lombiq worked with the municipal government of Santa Monica and with the Smithsonian Folkways Recordings, which is an agency of the US federal government. But did you know that apart from flashy websites, Orchard can also provide important services for citizens behind the scenes? The multi-tenant case management platform of a GovTech company we worked with does exactly that: If you live in a US city, you may have dealt with your permit or other license via the platform! And as you may have guessed, we're working with the company as Orchard Core experts.We've been helping the company since late 2022 with a variety of Orchard Core consulting, troubleshooting, and development tasks. This started with a general review of the GovTech app, and how it's hosted in Azure, to find areas of improvement or potential issues. Since Lombiq has run Orchard, then Orchard Core projects, and hosted apps in Azure for a decade now, we can always pinpoint things we recommend changing.They also asked us to deliver some specific development tasks that improve the UX of the permit management platform or help the development team. Here's a quick overview of some of these: Setting up automated QA tools. For these, we utilized our Orchard Core-optimized projects: Lombiq UI Testing Toolbox for automated UI testing, Lombiq .NET Analyzers for checking the code for any possible issues, and Lombiq GitHub Actions to provide full-featured CI builds and Azure deployments. These all help keep the platform working well, improving the development team's productivity. A WYSIWYG editor for the Orchard Core admin area, utilizing the user-friendly Froala editor. Users of the platform weren't fully satisfied with Orchard's built-in editor, so this was a welcome improvement. Chunked file uploads: Hosting environments commonly have some restrictions on the size of an HTTP request. So, if you want to allow users to upload larger files, the app needs to upload them in multiple chunks (parts). This was important for them since files related to permit management can routinely grow beyond the usual size limits. So, we've implemented chunked file uploads both in the platform and as a contribution to Orchard Core. Since we at Lombiq are really focused on open-source, it's always great to work with clients who understand how the open-source ecosystem works and that you also have to contribute back. This is what their CTO & Co-founder says about us working together:Lombiq excels in SaaS technology development, particularly in the context of Orchard Core. Their distinctive expertise and capabilities enabled us to expedite the expansion of our platform. They were consistently responsive, delivered high-quality code, smoothly transitioned each project to our development team, and assumed full responsibility for their tasks. I highly recommend collaborating with them for any SaaS related project.Do you also work with government clients and want to make sure your Orchard Core app runs smoothly? Get in touch with us and let the Orchard Core experts help you!