From CMS to Collection Manager: An Interview with Toby Dodds on Orchard Core at Smithsonian Folkways

“Our CMS is not just a web-publishing platform — it’s evolved to become our collection manager.” Smithsonian Folkways runs a 75,000-track archive on Orchard Core. Director of Technology Toby Dodds shares how they moved from Orchard 1.x to Core, and turned their CMS into a mission-critical platform.

How do you manage a musical archive with 75,000+ tracks, complex metadata, and a mission to keep every recording available forever? For Smithsonian Folkways, the answer began over a decade ago with Orchard 1.x, and today runs on a fully customized Orchard Core platform.

Smithsonian Folkways is the nonprofit record label of the U.S. national museum system — a digital home for musical traditions from across the globe. When their team first needed a scalable, flexible platform, Toby Dodds, Director of Technology, was referred to Lombiq by a fellow Orchard community member to help build it.

We talked to Toby about how their platform evolved over the years, what made Orchard the right long-term choice, and what others might learn from building and running something this complex and essential.


– Toby, can you give us a quick overview of what Folkways does, and why managing the platform is such a complex technical challenge?

Toby: Smithsonian Folkways Recordings is a record label based within the Smithsonian Institution in Washington, D.C.

It was founded in 1987 when the Smithsonian acquired Folkways Records, with a promise to keep the entire catalog in print in perpetuity. It had over 2,000 titles back then.

Today, it features closer to 4,000 releases with around 75,000 tracks of audio. The recordings in the collection are historic and diverse, with a strong emphasis on musical traditions from around the world.

Keeping this catalog of high-value material in print — both physically and digitally — requires a powerful website and a capable CMS to support it.

– So back when you were first planning the site, what made you go with Orchard? What were you looking for that led you there?

Toby: To meet our mission of keeping our catalog in print, we knew we needed a website capable of giving users access to our catalog with working search and many thousands of pages that feature rich media.

We also knew we would have to store complex metadata to make the website and our operation function.

When CMS technologies were emerging, we reviewed many projects but concluded that the Orchard CMS would best fit our needs.

Building on ASP.NET has always felt like a steady and reliable option for us — it allowed us to do powerful things without too much cost and on a reasonable upgrade path.

We liked the transparency and size of the Orchard community because it gave us easy access to it. Fundamentally though, Orchard was best because we would be able to design our own architecture within it without painful compromises.

– You’ve been on Orchard for a long time now. What made you stick with it when moving to Orchard Core, instead of switching to something else?

Toby: Preserving control over our collection, and executing our mission, superseded any other concerns about platform selections we’ve faced.

Our website is unique in its requirements, and we couldn’t be happier with our choice of Orchard Core.

Our CMS is not just a web-publishing platform — it’s evolved to become our collection manager. From content management to collection management — which for a museum-based organization is an important distinction.

Our ability to house collection records securely within Orchard and immediately make them available to the public via our website hits a very sweet spot for us.

– What were the biggest improvements or benefits you noticed after moving to Orchard Core?

Toby: Speed was the biggest upgrade we felt in transition to Core.

But along the way we solved a slew of big problems and were able to roll out new capabilities — including offering streaming of our catalog directly to our users.

We were also able to massively improve our search and browsing interfaces by leveraging the indexing architecture at the core of Core.

– And how did the new system change the way your team works day to day?

Toby: Working step-by-step, we have continued to add new capabilities to our Orchard Core implementation and are strengthening the role it plays in our organization.

Recently we added Audit Trail capabilities, for example, to make it possible to safely share the collection management project with a wider group.

– Sounds like it’s really grown into more than just a CMS. What kind of role does it play today?

Toby: We have branded our Orchard Core implementation with the name FCM, which stands for Folkways Collection Manager, and it is our system of truth for our collection.

It is at the center of nearly everything we do related to maintaining our catalog as a business and as an educational archival project.

We interact with it in too many ways to list, but there is no limit to the powerful things we feel we can do through programming in ASP.NET and Orchard.

– So where do you feel Orchard Core really shines? What makes it stand out for you after all these years?

Toby: We see Orchard Core as highly flexible, powerful, affordable, and fast.

We feel that extending its features through custom module development in ASP.NET allows us to do anything we can dream up.

We also like the fact that version changes are easier to accommodate, as Microsoft tends to respect the need to support legacy technologies for a longer period than the alternative PHP-centric projects.

We hope to be using Orchard Core as our platform for a good five to ten years — maybe more!

– If you could change or improve one thing in Orchard Core based on your experience, what would it be?

Toby: Getting the development environment up and running is tricky at times, and I’ve gotten quite stuck just getting going.

There’s a learning curve — but that’s true for any platform — and Orchard concepts align closely to ASP.NET ones, so finding help is never difficult.

Thankfully, Lombiq has been there to hold our hands for years now.

There’s no question that to use Orchard Core you need to have a good amount of experience with ASP.NET and/or access to developers like Lombiq to help you — ideally both.

– You’ve been part of the Orchard Core community for a while now. What’s your experience been like with it over the years?

I honestly feel guilty that I haven’t made more of the regular meetings. I’d like to feel more connected to it.

I appreciate Lombiq’s help organizing and connecting people within the community as well. It’s such amazing technology — it sells itself really — but I get the sense it could use more evangelists.

– You’ve worked with Lombiq for quite a while now. What made us the right fit back then — and what’s kept you coming back all these years?

Toby: Lombiq has for some time now been the strongest vendor in the Orchard space.

We are loyal to the quality of the work they do and happily recommend them to others.

They are very passionate and kind people — a pleasure to work with.

– What would you tell other organizations that are considering Orchard Core or thinking about working with Lombiq?

Toby: If you are passionate about your work and determined to deploy technologies that cater specifically to your vision without compromise, then you must invest in design and technologies that are flexible and robust.

Orchard Core development on the ASP.NET platform is a safe and sound investment that aims you in the direction of success at a manageable cost and with the promise of nothing being impossible.

Smithsonian Folkways is considered one of the great folk music record labels, and that success is driven by our ability to share our recordings in our own unique way.

Orchard Core empowers us to achieve our goals — supporting our website while providing the backend capabilities we need to succeed in our business.


Thanks to Toby for sharing this behind-the-scenes look at how Smithsonian Folkways built and evolved a platform that does so much more than power a website.


His story is a reminder that with the right tools — and the right team — Orchard Core can become a core part of how organizations work, grow, and deliver on their mission.


Want to build something like this? Contact us to talk through how we can help.

mark.bartha Case study Smithsonian Institution Orchard Core Government CMS Interview Education Music Smithsonian Folkways Recordings USA

Other recent posts

Rebuilding DotNest.com: Orchard Core, Tailwind 4, and a more maintainable workflow
DotNest is Lombiq’s managed Orchard Core hosting platform where users can create and run Orchard Core sites without handling infrastructure, updates, or maintenance themselves. We recently rebuilt the site to give DotNest a clearer presentation and a more modern user experience. By looking behind the scenes of the DotNest site rebuild, you’ll see how a website redesign can become a broader modernization project: improving how landing pages are structured, introducing Tailwind 4 into an Orchard Core front-end workflow, simplifying asset handling, and using AI-assisted tools in a practical way while keeping developers in control. Why the rebuild mattered The previous site served its purpose, but it no longer matched what we envisioned for DotNest. Beyond a more modern design, we needed clearer messaging, and a content management structure that would be easier to maintain as the site evolved. This was especially important because DotNest is more than a marketing website. It also reflects how we approach building maintainable Orchard Core platforms. If the site itself is hard to update, every future improvement becomes slower and more expensive than it should be. So we treated the rebuild as more than a visual refresh. It became a chance to rethink the site’s structure, front-end workflow, and development process in a way we can reuse on future Orchard Core projects. Building landing pages around reusable sections One of the main changes was how landing pages are structured in Orchard Core. Previously, the DotNest pages used simple Liquid widgets for page sections. This was quick and flexible while most changes were made directly by developers, but it also meant that the page structure was less explicit and harder to evolve consistently over time. Around the same time, the Orchard Core community was also moving toward more reusable “Blocks”-style page structures, which aligned closely with the direction we already wanted to take for DotNest. The rebuild became a good opportunity to apply a similar pattern in practice. For the new site, each landing page section now has its own content type, and the sections are composed on the landing page through Orchard Core’s BagPart. This keeps the flexibility of section-based pages while giving each section a clearer structure and purpose. The result is a landing page system that is easier to understand, easier to extend, and less dependent on ad-hoc template changes. At the same time, the reusable section-based approach gives content editors flexibility within clear guardrails, making it much harder to accidentally break layouts or page structure. For a marketing site that will keep evolving, that maintainability matters as much as the initial design. Modernizing the front-end workflow The rebuild was also the point where we introduced Tailwind 4 into our internal front-end workflow for Orchard Core projects. Previously, we used a BEM-style approach with custom CSS files. While this worked well for years, it also created more manual structure and coordination as the site evolved. With Tailwind 4, we could build UI components faster, keep styling closer to the markup, and work more consistently with our design system. As part of the rebuild, we removed the old Node.js-based asset pipeline and integrated Tailwind directly into the .NET build workflow. That led to Lombiq Tailwind Targets, our open-source MSBuild integration for Tailwind CSS. With Lombiq Tailwind Targets, Tailwind compilation runs as part of the .NET build process, making the front-end workflow feel like a natural part of the Orchard Core application instead of a separate toolchain to maintain. This also aligned with a broader direction we had already started exploring at Lombiq: simplifying front-end tooling and moving away from Node.js-based workflows where they add unnecessary maintenance overhead. We wrote earlier about this approach in Step away from that Node.js. Using AI where it helps, with developers still in control AI-assisted tools became part of the rebuild mainly in the UI and front-end workflow. We used Magic Patterns to explore UI directions and generate Tailwind-based starting points from our design system. Since the generated code was not always aligned with Tailwind 4 or the final Orchard Core implementation, we still reviewed and refactored it before integrating it into the site. To support this workflow, we also created two open-source repositories: Tailwind Agent Skills and Orchard Core Agent Skills. These agent skill collections give AI tools more project-specific context around Tailwind 4, Orchard Core theming, content modeling, shapes, and recipes, making the output far more useful than generic prompting alone. The goal was not to automate development away, but to make AI-assisted work more practical and reviewable for real Orchard Core projects. AI helped speed up repetitive and exploratory tasks, while developers still made the architectural and implementation decisions needed to keep the final result maintainable. What we gained from the project One of the biggest takeaways was how much easier Orchard Core landing pages become to manage once reusable sections and clearer content structures are introduced. The previous setup had gradually accumulated friction over time, while the new approach already feels easier to extend and work with. The rebuild was also our first larger Tailwind 4 project, and it significantly changed how quickly we can build and adjust UI components. That experience directly led to Lombiq Tailwind Targets and helped shape how we want to handle front-end workflows in future Orchard Core projects. We also learned a lot about practical AI-assisted development. Working on a real-world project made it much clearer where AI tools actually help and where developer oversight still matters. That experience ultimately led to the Tailwind Agent Skills and Orchard Core Agent Skills repositories. Most importantly, we validated different development approaches for future Orchard Core websites. If you’re planning an Orchard Core website, a redesign, or a modernization project, reach out to us. We’re always happy to help teams build Orchard Core solutions that remain easy to evolve as requirements grow over time.

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!