Blog post series overview

This post is part of our series about hosting Orchard Core at European cloud providers. Orchard Core has built-in support for a lot of Azure services, including Media storage, secret storage, e-mail delivery and sending SMS, AI search, and even observability with Azure Application Insights with the Lombiq module. AWS also has support for Media storage. For cloud-hosted full-text search we can use Elasticsearch, and Redis to aid with horizontal scaling. How does using a smaller cloud provider, without specific support from Orchard Core, compare?

We've looked into hosting a vanilla Orchard Core app as a proof of concept, and are sharing our experiences here. The goal was to run Orchard Core with a minimal hosting environment, but with a stateless web server (so, keeping the database and Media storage separate). This could've been simplified to only use a web server (and keep the database in a local SQLite file, as well as use local Media files), but we wanted to go a bit more realistic than that. To be able to play around with the web server from the GUI too, we've chosen Windows as the OS if available. Additionally, we also checked if the platform helps with any of the other common infrastructure requirements, like sending e-mails or observability.

Note that while we usually received some credits from the cloud providers for testing, they are not paying for these reviews, and any endorsement or critique is our own.

What's Exoscale?

Exoscale is a cloud provider from Switzerland, with hosting locations back at home, as well as in Germany, Austria, Bulgaria, and since July also in Croatia.

As far as services interesting for Orchard Core hosting go, they offer VMs with load balancing, AWS S3-compatible object storage, and databases as a service. Managed Kubernetes is also available, but for the sake of this post, trying to host a simple app, we won't create a cluster. Instead of Redis, you can create Valkey instances (Valkey is an open-source fork of Redis), which, for now, should just work with Orchard Core's Redis support. While OpenSearch is also available, that's incompatible with Orchard's Elasticsearch integration. DNS management is also available, though that's something I'd keep at Cloudflare for a real-life app. I'd also use Cloudflare as a CDN, despite Exoscale offering a CDN layer (with Akamai) on top of their object storage; but since in Orchard Core we don't serve Media files from storage directly, that wouldn't help anyway.

If you want to send e-mails, implement observability, or add search and indexing other than with Lucene on the web server, you're on your own.

Creating an Orchard Core hosting environment

You surely already guessed, but we'll need three Exoscale services:

• A Compute Instance, i.e. a VM, for the web server.
• A DBaaS database; we'll use PostgreSQL. We could also create SQL Server instances, but not only would the minimum 2-core VM be an overkill for our purposes, it's also much more expensive, starting at about EUR 247/month (vs a Postgres DBaaS starting at EUR 42/month).
• Object Storage for Media.

Let's start with the server! I went with the Swiss zone, since there's no place like home, and opted with a 2-CPU plan with 2 GB of RAM. For this site, 1 CPU would also be more than enough (while to cater for Windows, I'm more comfortable with 2 GB of RAM instead of 1), but there's no 1-CPU 2 GB RAM instance type.

You may notice two things here:

• On the right, there's a warning about having to create Security Groups for ingress rules first. (Somewhat confusingly the ADD button below it actually creates the compute instance, not a Security Group.) To be able to actually connect to the VM, we also need to edit the default Security Group (or perhaps more diligently, create a new one), then open up the ingress port 80 with TCP (for HTTP), as well as add a rule for RDP. As a last step, you'll also need to add 0.0.0.0/0 (i.e. all IPs) under External Sources, allowing anyone to connect to our web server.
• Those ENABLE buttons for instances Mega and up mean that you need to ask Exoscale support to allow them "after a manual screening process". This I find a bit strange.

Until the server started, so in the meantime, I created an Object Storage bucket in the same zone (to minimize latency, these resources should all be in the same zone):

It seems that unlike with other cloud providers where you create a storage account, then a bucket under it, here everyone shares the same storage account. Thus, bucket names should be globally unique. This doesn't seem appealing at a first glance, but apart from the naming issue, I didn't find any practical problem with it.

Somewhat counterintuitively, the storage access and secret keys are API keys. You can create these following the docs; for the sake of simplicity, I created a key for the Owner role, but for a production app, you should follow the docs' recommendations and create a restricted role just to access this bucket.

Finally, we also need a single-node Postgres database server:

Note that this runs on its own VM. The IP filter is necessary for the web server to access the DB server; the provided CIDR matches the exact IP of it.

This is everything we need, so now we can continue with setting up Orchard Core in this environment.

Deploying Orchard Core to the web server

You can deploy an ASP.NET Core app, including an Orchard Core-using one, with Web Deploy to IIS, using automated deployment from a GitHub Actions workflow, or just by copying its publish outputs to the server. Here, I opted with the simplest option: I published the web app to a folder from Visual Studio (but running dotnet publish from the CLI would be equally suitable), and copied the resulting files to the server via Remote Desktop. Then I could simply run the web app:

The app listens to port 80 because I added an appsettings.Production.json file configuring it:

{
  "Kestrel": {
    "Endpoints": {
      "HttpEndpoint": {
        "Url": "http://*:80"
      }
    }
  }
}

This allows you to simply open the IP of the server in a browser, or point a DNS A record to it. Our site is now available on the internet! ...after we allowed the exe of our web app through the Windows Firewall, that is.

You may notice that this is a really barebones approach: There's no IIS, no HTTPS, no proper deployment. And you're right! This is a focused example of getting Orchard Core running, but we'll return to the missing pieces later.

Setting up Orchard Core

Running the Orchard Core setup is standard: Just fill out the usual settings on the setup screen, and point the app to the Postgres DB. For the latter, you can copy the Postgres connection string from the Exoscale Console, take the password of the default user from the DB's Users menu, and ask your favorite AI tool to turn them into an Npgsql connection string that .NET uses.

Once setup finishes, you can configure Media storage too. I've elaborated above how to set up a bucket; the service URL for it will be in the format https://sos-{zone}.exo.io, with our Switzerland zone being ch-dk-2.

Now it's time to configure the connection for the app. Again, you can use the appsettings.Production.json file to add something like below, resulting in the following full file:

{
  "Kestrel": {
    "Endpoints": {
      "HttpEndpoint": {
        "Url": "http://*:80"
      }
    }
  },
  "OrchardCore": {
    "OrchardCore_Media_AmazonS3": {
      "ServiceURL": "https://sos-ch-dk-2.exo.io",
      "Credentials": {
        "SecretKey": "add the secret of the user you created",
        "AccessKey": "add the access key of the user you created"
      },
      "CreateBucket": true,
      "RemoveBucket": true,
      "BucketName": "oc-media"
    }
  }
}

Be sure to change the ServiceURL value to that of your instance, as indicated on its Overview page (under "S3 endpoint"). That's actually an undocumented configuration key that comes very handy when, as we do here, you connect to an S3 account outside of AWS.

Now restart the app (so it reads the updated configuration file) and enable the Amazon Media Storage feature from the Orchard Core admin. It'll work, despite it not running in Amazon. Magic!

And with this, our app fully works!

Why would you (not) use Exoscale?

OK, so we've seen that running Orchard Core under Exoscale works. This is not a huge surprise, but it's nice to get it verified and have the basics figured out. Why would we do this, though, instead of choosing the beaten path with Azure or AWS, for example?

European

Exoscale is not just hosting in Europe, but the company itself is also based in a European country. If that matters for you, either for sentimental reasons or as a matter of company policy (like using a provider that's not under the US CLOUD Act), it can be a big plus. Note though, that while Switzerland is highly aligned with the EU legally, it's not an EU member state, nor part of the European Economic Area.

Costs

Exoscale can be a lot cheaper. At €17/month, the Exoscale server provides roughly the same as an A1_v2 Azure VM, which costs €45/month.

However, the smallest managed Postgres instance at €42/month is way above what we'd use on Azure for an entry-level app, where an S0 Azure SQL DB would be around €13/month.

So, in the end, Exoscale costs around EUR 60/month, while the roughly equivalent service in Azure would be basically the same. We do get more with Exoscale (a dedicated VM for the DB, and I think the web server is faster too), a lot more room to grow, but the cost advantage, in itself, disappears, at least in the beginning. 

For an entry-level app the storage is cents in both cases, but if you increase your usage, Exoscale's storage costs can be dramatically lower (EUR 0,00002750/GB vs Azure's Standard Hot tier at EUR 0,0185/GB). Network costs at Exoscale (EUR 0,02/GB for egress) and per-operation costs at Azure (there's no simple number for this) complicate things, though, so be sure to calculate what's applicable for your app.

All this being said, at Azure, we'd rather use App Services: This is a higher-level "websites as a service", offering a bunch of convenience features like automated deployment, staged publishing, and configuration management. The smallest proper App Services-based infrastructure (with a staging slot and separate staging and production DBs) comes at around €90/month, though, but that also contains a lot of features lacking from VMs.

Simplicity

Without consulting any resource, just by playing with the Console, I could fully understand the Exoscale offering (I think...) within like half an hour. Getting the full Orchard Core environment running wouldn't have been much more, have I not written this post at the same time (plus getting stuck on the mentioned storage configuration).

The cons

Coming from frequently using the cushy but extremely complex ecosystem of Azure, using a more basic provider like Exoscale is certainly an interesting change. It seems to me that ultimately, there's a lot of work to do if you want to have a full-blown, highly automated hosting environment for Orchard Core, with an option for horizontal scaling. Below are the features that I'd consider necessary, and while these are given with Azure, you need to roll your own solutions with Exoscale:

• Staged publishing (blue-green deployment): You'd need to set up multiple VMs or multiple sites, and manage swapping staging with production somehow on your own.
• Automated deployments: I think under a Windows server, the easiest would be to set up Web Deploy and use it from an automation platform like GitHub Actions.
• Observability: You'd either need to host an observability platform yourself, or use an external service.
• The lack of a search/indexing service is less of an issue, because you can just use the Elastic Cloud (what's the option in Azure and AWS too), and I'd consider the lack of an e-mail service not a huge issue either (you can just use something like SendGrid). Managed Valkey is good, but starting at €43/month, it's not priced for an easy entry (just as Postgres), although it also provides a lot more resources than the lowest tiers of Azure Cache for Redis do (for a lower price).

Yes, you could build an all-in-one infrastructure with Kubernetes, and have containers with services for all the above features (and a DB and storage as well), but that's a large complexity you need to manage. Using Terraform, supported by Exoscale, to ramp up your infrastructure can cut down on manual repetition (and aid portability to other providers to an extent), but is also work that you have to invest. And at the entry level, managed solutions for services like SQL and Redis (instead of hosting your own VMs/containers) can be more cost-efficient too (but that flips if your app's demand increases).

There are also three notable things I very much didn't like about Exoscale's pricing: 

• All prices on the pricing page are shown for usage hours only. That's necessary, but a metric frequently a lot more useful is the monthly cost. While I can always multiply by 730 to get an approximation of a month, it would be much clearer to have it indicated in the pricing table already. Also, I'd welcome seeing these hourly and monthly costs indicated in the Exoscale Console, when creating resources, too. The Pricing Calculator helps, and it does show monthly costs too, but it's better to show this information everywhere.
• The prices in EUR, CHF, and USD are exactly the same. Given that 1 CHF is 1,07 EUR, and 1 EUR is 1,16 USD as of writing this, there's a significant difference in your costs depending on what you pay with (you pay almost 25% more in CHF than USD). According to the website, "Your account can be setup in either CHF, EUR or USD, depending on your initial legal residence." This seems like an arbitrary disadvantage for Swiss users, and an advantage to non-EU ones. The latter is a surprising policy for a company primarily targeting EU customers. I'd welcome the price differences to disappear.
• You can only pay in advance, at least as a new customer. This requires you to either be ready to top up your balance any time you get a low credit notification, or you need to park an excessive amount at Exoscale. In either case, it's also a manual process. It would be better if they would just charge my card after each month's usage.

So, what should I do?

Based on the feature set, Exoscale can be a good choice to host your Orchard Core app if you don't need anything beyond what's easily possible with the existing offering, or if you already invested into a portable Kubernetes-based infrastructure. However, I think the particularities of Exoscale's pricing are not for everyone.

And if you need help hosting Orchard Core at Exoscale, Azure, or onboard of a satellite (not kidding), drop us a line!

New Allow Remember Me Login Setting

This feature by Mike Alhayek adds a new AllowRememberMe setting in LoginSettings, so administrators can control whether the Remember Me option is available on the login form at all. When it's off, the checkbox is neither shown nor respected, so the option is a real security policy control, not just a UI toggle.

To try it out, head to Settings -> Security -> User Login, where you will find the new Allow user to be remembered during login checkbox, defaulting to true. Turn it off, and the Remember me checkbox disappears from the login screen entirely.

How to use Orchard Core Agent Skills?

Orchard Core has had several agent skills for a while, but no documentation on how to use or contribute to them, until now. Thanks to Antoine Griffard, there is a new documentation page that covers where the skills live, which ones are available, and how to use them. For teams onboarding new developers (or new AI agents) onto Orchard Core, that's one less thing to figure out by trial and error.

Antoine also added a new skill, Orchard Core Setup Recipe Creator, which creates Orchard Core setup recipes (.recipe.json) that provision a tenant on setup: enabling features, setting themes, defining content types, importing content, roles, and settings. Use it when you need a setup recipe, a starter recipe, or automated tenant configuration.

Sébastien Ros improved the orchardcore-tester skill, so an agent can reliably stand up an Orchard Core site for browser-based functional testing. Find the updated skill, which tests Orchard Core features through browser automation: admin features, content management, media library, and module testing.

Demos

Catch Slow SQL Before Production - Lombiq's Query Monitoring Explained

This week, you can see a new feature in the Lombiq UI Testing Toolbox for Orchard Core: automated SQL query monitoring for UI tests. It flags three common performance problems as tests run:

• duplicate SQL queries (the classic SELECT N+1 signal)
• duplicate queries with identical parameters (usually a missing cache)
• and oversized result sets (usually a missing filter or paging).

It's disabled by default since it adds overhead, so you enable it for the tests where it matters, either as manual assertions after specific page changes or automatically on every page load, with configurable thresholds and execution filters. When a check fails, you get the URL, failure category, threshold, and full SQL call stack, so you can tell right away whether it's a real regression or just needs tuning.

The easiest way to try it out is to clone Lombiq's Open-Source Orchard Core Extensions solution. This Orchard Core Visual Studio solution contains most of Lombiq's open-source Orchard modules and themes, as well as related utilities and libraries, including our UI Testing Toolbox for Orchard Core with several samples and documentation.

You will find a class called SqlQueryMonitoringTests in the Lombiq.Tests.UI.Samples project that contains several well-documented tests. We will run the first one, called SqlQueryMonitoringExplicitAssertions. But before doing that, we added a for loop to our code that will query all of our published content items a hundred times, so we have something for the monitor to catch.

If we run our test and check the Test Detail Summary, we will see two failure categories:

• DuplicateCommandText
• DuplicateCommandWithParameters

Below the categories, you can see guides, threshold configuration values, and call stacks to help you identify and fix the errors raised by our feature.

For teams maintaining a codebase long-term, this is the kind of check that catches performance regressions in code review instead of in production, backed by the same open-source toolkit (Selenium, Atata, xUnit, cross-browser, CI-ready) Lombiq uses on its own client projects. Watch the demo on YouTube for more, or check the docs for setup details.

News from the community

Orchard Harvest 2026 Program

The Orchard Harvest 2026 conference will be held in Vancouver, and we look forward to seeing you all this autumn in Canada. Our confirmed dates for this year are September 10th and 11th.

Don't miss this limited-time offer: just $280 for two days of all-access learning and networking. Secure your early-bird tickets to the conference now!

The full Orchard Harvest 2026 program is live! Be sure to check out the conference's updated official website for the program!

As we move forward, we will keep community members informed of the details, and you will find every detail in this newsletter, too!

Don't miss the biggest Orchard Core event of the year!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 411 subscribers! We have started this newsletter to keep the Orchard community informed about the latest platform news. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Content Version Pruning Feature

The new Content Version Pruning feature provides a background task that periodically deletes old archived content item versions; versions that are neither the latest nor the published one. On sites that are edited often, every save or publish leaves the previous version behind in the database. Over time, these accumulate, growing the storage footprint and slowing version-history queries. Pruning keeps that history bounded. The latest draft and the published version of an item are never deleted; only superseded (archived) versions are eligible.

To try it out, head to Tools -> Features and enable the Content Version Pruning feature. After that, you will find a new settings page under Settings -> Content Version Pruning, where you can configure its behavior. As you can see, you can configure the retention days for content item versions, automatically pruning old, non-latest, and non-published versions while keeping at least one version per item, with options to specify which content types to prune.

Here we said to prune the non-latest, non-published versions of the Blog Post content items that are older than 30 days, while keeping one version of the most recent archived versions, regardless of age.

Deletions are flushed in batches to keep the unit of work bounded, and a failure to delete one version is logged and skipped without aborting the run.

Note that pruned versions are permanently removed from the database and cannot be restored. Choose a retention period and version-keep count that match your audit and rollback needs before enabling the task.

Thanks, PUXVSE, for your first contribution, and Antoine Griffard for the documentation!

New "Add & Configure" and "Save & Configure" buttons in the content editor UI

This change by Mike Alhayek lets you add a content part or a content field and configure it in one step, instead of adding it first and then hunting for it again to set it up. It introduces new Add & Configure and Save & Configure buttons to the content editor, with more dynamic controls and clearer feedback, and updated backend logic to support the new flows. The Add Selected Parts button in AddPartsTo.cshtml is now only visible when at least one part is selected, with dynamic show/hide logic via JavaScript.

Here we have a site set up with the Blog recipe, and we want to add a new Text Field called Quote to the predefined Blog Post content type. To do that, we need to navigate to Design -> Content Definition -> Content Types and hit Edit near the Blog Post content type. Then hit the Add Field button, select the Text Field, and click the Save & Configure button to immediately configure the newly added field.

Demos

Orchard Core Just Got a New Home

Over the past two weeks, you could see demos of how the community shaped the Orchard Core website, including the page that promotes Orchard Harvest.

The new Orchard Core website is live! Nick Jackson demoed the final version, walking through the technical build and the content updates.

The site is built on vanilla Orchard Core (upgraded to Orchard Core 3), with only the Tailwind module added for styling; external modules were intentionally left out to keep the implementation clean. Highlights include automated daily NuGet download stats via workflows, clickable speaker bios, historical Orchard Harvest event pages, and a "stay up to date" section. The site also hits double-A accessibility standards with strong Google Lighthouse scores on both mobile and desktop.

Thanks again to Nick Jackson for the build, and to the whole team for the feedback that shaped it!

Check out the recording and let us know what you think!

News from the community

Sign in with Microsoft: SSO for Orchard Core

Tired of making users juggle yet another username and password? Our article shows how to plug Microsoft sign-in (personal accounts or Entra ID/Microsoft 365) straight into your ASP.NET Core or Orchard Core app, so people log in with credentials they already trust, while Orchard Core keeps full control over roles and permissions behind the scenes.

You can test-drive the whole flow on DotNest without writing a line of custom code. Check out the official documentation, or contact us if you want help wiring Microsoft SSO into your app or portal.

Orchard Harvest 2026 Program

The Orchard Harvest 2026 conference will be held in Vancouver, and we look forward to seeing you all this autumn in Canada. Our confirmed dates for this year are September 10th and 11th.

Don't miss this limited-time offer: just $280 for two days of all-access learning and networking. Secure your early-bird tickets to the conference now!

The full Orchard Harvest 2026 program is live! Be sure to check out the conference's updated official website for the program!

As we move forward, we will keep community members informed of the details, and you will find every detail in this newsletter, too!

Don't miss the biggest Orchard Core event of the year!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 413 subscribers! We have started this newsletter to keep the Orchard community informed about the latest platform news. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Hisham: My journey with Orchard started before Orchard Core, when Orchard CMS was hosted on CodePlex and simply called Orchard. To be honest, I didn't use Orchard 1 for production, just exploring what was there. I have been following Orchard Core since the beginning, when it was called Orchard vNext. It was a prototype, if I recall, and I started my first contribution on May 25, 2017.

Gábor: Right, the very first commits to the Orchard Core repo were made by Nicholas Mayne in November of 2014. That was more than 10 years ago! And why do you like contributing to Orchard?

Hisham: For me, Orchard Core is not the first project I contributed to. Open-source software is close to my heart. I had already contributed to many projects before Orchard Core. After dedicating a lot of time to Orchard Core, I found it helped me understand many aspects of the ecosystem.

This has helped me use Orchard Core in my daily development and in production websites, as well as help the community as much as I can.

Gábor: What do you like most about Orchard?

Hisham: Flexibility, Extensibility, and Community.

Gábor: Have you tried other CMSs too?

Hisham: Sure, I tried many CMSs and frameworks, including DotNetNuke (DNN), Umbraco, Oqtane Framework, and Kentico CMS in the ASP.NET Core space. I also tried many PHP CMSs, including Drupal and Joomla.

For me, Orchard Core is one of the top 3 I have ever seen, but it has a steep learning curve; there are specialized terms, such as drivers and shapes.

Gábor: And what do you think is the difference between Orchard and the other CMSs?

Hisham: Orchard Core is not just a CMS; it's a web application framework with a CMS built on top of it, which is unique compared to other OSS projects.

It contains many modules, more than enough to start building your websites and web applications without worrying about the framework and cross-cutting concerns such as multitenancy, modularity, localization, logging, and much more.

I'd like to mention that Orchard Core is very flexible and extensible, and you can do many things even if you don't own the source code. It is the only product I have ever seen that provides such flexibility, in my opinion, but it also introduces some complexity.

Gábor: You mentioned that you are contributing to other open-source projects too. What are these projects? Are you contributing to the ones you mentioned?

Hisham: Yes, of course. I also contributed to many open-source software projects before Orchard Core, including the Oqtane Framework. I contributed to SimplCommerce, as well as to ASP.NET Core in its early days, when it was called DNX (Dot Net eXecution environment).

I'm running and maintaining a few libraries, such as JSON Localizer, which has over 700K downloads on NuGet.

I'm also helping with many projects, especially in localization. For more details, you can check out my GitHub profile.

Gábor: Congratulations on reaching more than 700K downloads! And you also have a repository on GitHub called Orchard Core Contrib Modules. Could you tell us more about it?

Hisham: Yes, I started a GitHub organization named "Orchard Core Contrib (OCC)", which is from the community to the community. It contains several repositories, including APIs, modules, and themes, that are not included by default in the official Orchard Core release. There were features that started there and were later moved to Orchard Core, which is impressive.

However, I faced many challenges maintaining these 59 packages, and the number is increasing over time, which requires significant time and support to keep these projects running.

But I will not forget the very useful feedback and contributions I received from the community. On that note, I invite any Orchard developer to contribute to this great project, which is community-to-community, as I mentioned before.

Gábor: I'm glad to hear that you receive useful feedback from the community. It's always a good feeling when others use and care about a project.

Hisham: I agree. The community is one of the most important things that made this project a success story. Many OSS projects have lost traction when there was no community around them.

Finally, I can't find the words to express my gratitude to Lombiq for their financial support for my contributions.

Gábor: It's our pleasure to support the developers who power open source. One last question: are you planning to join this year's Harvest?

Hisham: Unfortunately, no, due to the difficulties in reaching Canada and the US.

Gábor: I'm sad that you can't make it. Thank you for the interview, and I hope to see you at Harvest next year!

Stay tuned for the upcoming parts of the Sponsorship Spotlight series! And if you missed the previous part, you can check it out here, where we talked with Antoine Griffard, one of the main developers of Orchard Core. If you don't want to miss our upcoming Sponsorship Spotlight series, sign up for the Lombiq Technologies Newsletter and stay up to date with what's new, insightful, and happening at Lombiq.

Check out our Orchard Dojo newsletter too for news about Orchard!

Improve Features Management UI

Mike Alhayek reworked the Features page in the admin UI:

• Removed the jQuery dependency in favor of vanilla JavaScript.
• Search now matches on both feature description and feature ID.
• New filters hide On Demand and Always Enabled features by default, with an option to show them.
• You can now select all features within a category at once.
• Dependency badges switched to the lighter badge style, matching the pattern used elsewhere in the UI, including the Content Management screens.

The GIF below shows the Visibility filter hiding features by default, then selecting every feature under one category in a single click.

Shape Debugging Site Settings

Mike Alhayek introduced a new site-level "Debugging" settings group that lets site owners turn shape debugging (HTML comments around rendered shapes) on or off directly from the admin UI, instead of requiring code changes.

To enable it, go to Settings -> Debugging and tick Write shape debug information. When enabled, Orchard Core writes HTML comments around rendered shapes so you can inspect which shape binding or template produced a fragment on a running site.

In our example, we have a site set up with the Blog recipe and checked the source code of the homepage. As you can see, the rendered shapes are wrapped with comments on any page you inspect. The opening comment contains the shape type and the binding used. Razor bindings report the .cshtml path, while Liquid bindings report a virtual .liquid source.

Demos

Inside Orchard Harvest's New Website

Nick Jackson presented the redesign concepts for the Orchard Harvest website: layout changes, improved navigation, dynamic content blocks, and enhancements to the Try Orchard Core site.

The preview shows the new hero section, call-to-action buttons, sponsorship logos, and streamlined navigation. The redesign supports dynamic layouts for pre- and post-conference states, including sections for submitting talks, past event photos, and sponsor information. Speaker profiles are simplified with links to GitHub or LinkedIn, and the schedule is presented in an accordion style to save vertical space and highlight breaks.

Nick also showcased improvements to the Try Orchard Core demo site, clarifying the signup process, emphasizing privacy and free access, and adding frequently asked questions for user reassurance.

See the preview and share your feedback on direction, accuracy, and tone.

Watch it on YouTube and check out the pull request!

News from the community

Ready to simplify your Orchard Core hosting?

We launched DotNest, our fully managed Orchard Core hosting platform, on Microsoft Marketplace, already powering more than 6,000 websites worldwide. IT teams, marketing teams, and digital agencies can now provision a fully managed Orchard Core site in minutes, directly through their existing Azure subscription: no separate procurement, no infrastructure to manage.

What you get: automatic updates, native Azure integration, extensive theming and content-modeling freedom, built-in ecommerce, enterprise-grade performance, and GDPR compliance out of the box.

Skip the infrastructure work. Explore DotNest on Microsoft Marketplace, or visit DotNest.com to learn more.

Read the announcement on our site!

Orchard Harvest 2026 Program

The Orchard Harvest 2026 conference will be held in Vancouver, and we look forward to seeing you all this autumn in Canada. Our confirmed dates for this year are September 10th and 11th.

Don't miss this limited-time offer: just $280 for two days of all-access learning and networking. Secure your early-bird tickets to the conference now!

The full Orchard Harvest 2026 program is live! Be sure to check out the conference's updated official website for the program!

As we move forward, we will keep community members informed of the details, and you will find every detail in this newsletter, too!

Don't miss the biggest Orchard Core event of the year!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 413 subscribers! We have started this newsletter to keep the Orchard community informed about the latest platform news. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

OCAT CSS Classes for Admin Editors

This change by Mike Alhayek focuses on improving the consistency and maintainability of the Orchard Core admin UI by standardizing form layouts, enhancing accessibility, and refining the structure of several view files. The main changes include removing the TheAdminThemeOptions and the CssOrchardHelperExtensions, so admin editor views now use static CSS classes prefixed with ocat- (Orchard Core Admin Theme) instead of C# helper methods that injected CSS classes at runtime.

For example, in BooleanField.Edit.cshtml, the Orchard.GetFieldWrapperClasses() helper was replaced by ocat-wrapper and Orchard.GetEndClasses() by ocat-end-offset.

The docs about the Admin Theme Conventions mention the available OCAT CSS classes for Admin Editors, the Content Part and Field Wrapper classes with some examples about how to use OCAT classes in custom views.

The release notes for Orchard Core 3.0 list the CSS helper extensions that were removed along with the new CSS classes to use instead.

Enable Liquid Support for Workflow Tasks alongside JavaScript

Thanks to Mike Alhayek, all workflow tasks that previously only supported JavaScript now also support Liquid. Additionally, LiquidTask was added to mimic ScriptTask.

As you can see, the SetProperty task now includes a Syntax selector for switching between JavaScript and Liquid.

All affected workflow edit views (ForEachTask, ForLoopTask, IfElseTask, SetOutputTask, SetPropertyTask, WhileLoopTask, and the new LiquidTask) have been updated to use the ocat-* CSS class conventions mentioned previously required by the admin theme.

You can also find a new AI agent skill called OrchardCore Admin Edit Views under .agents/skills/ to document the ocat-* CSS class patterns so future AI-assisted development correctly uses the two-column admin edit view layout.

Demos

Help Shape Orchard Core's New Website

Nick Jackson presents a demo of the proposed Orchard Core website redesign, outlining design decisions, targeted audiences, content structure, and plans for feedback and further development.

The redesign targets two audiences: .NET developers evaluating the framework, and the business decision-makers (agency owners, CTOs, clients) who need reassurance that Orchard Core is a safe, mature choice. Nick explained the design reasoning in detail: the visual style intentionally mirrors the existing admin UI for consistency, the layout is clean and modular to match the product itself, the color palette leans on Orchard Core's green tones for a trustworthy feel, and icons and stock photography were minimized in favor of real screenshots and contributor data. His post on GitHub also includes a factual comparison table against Umbraco and ABP, positioning Orchard Core as a combined CMS/application framework that's free and community-led.

The stated goals are to drive more installs/trials and to reassure business stakeholders about cost, governance, and longevity, with a toggle letting visitors switch between developer-focused and business-focused messaging.

See the preview and share your feedback on direction, accuracy, and tone.

Watch it on YouTube and check out the pull request!

News from the community

A new website using Orchard Core: GoRide

GoRide is a hyperlocal marketplace, their mission is to bring merchants together to offer you the best possible bike rental fleet. Check out their Orchard Core site here!

For more Orchard Core sites in the wild, visit Show Orchard, a community showcase of representative Orchard CMS and Orchard Core websites maintained by Lombiq Technologies. Show Orchard itself runs on Orchard Core on DotNest. Read the case study on how we migrated it from Orchard 1!

If you're considering a similar migration, the Lombiq team is available to help. Get in touch!

Orchard Harvest 2026 Program

The Orchard Harvest 2026 conference will be held in Vancouver, and we look forward to seeing you all this autumn in Canada. Our confirmed dates for this year are September 10th and 11th.

Don't miss this limited-time offer: just $280 for two days of all-access learning and networking. Secure your early-bird tickets to the conference now!

The full Orchard Harvest 2026 program is live! Be sure to check out the conference's updated official website for the program!

As we move forward, we will keep community members informed of the details, and you will find every detail in this newsletter, too!

Don't miss the biggest Orchard Core event of the year!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 414 subscribers! We have started this newsletter to keep the Orchard community informed about the latest platform news. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Add import/export support for OrchardCore.Security settings

OrchardCore.Security lacked the ability to import/export its settings: no IRecipeStepHandler implementation (making even hand-crafted recipes impossible) and no IDeploymentSource. Kenneth Okalang fixed this by adding a SecurityDeploymentStartup that registers a site settings property deployment step for SecuritySettings via AddSiteSettingsPropertyDeploymentStep. Both import and export (via recipe steps and deployment plans) are now available through the standard UI.

In the admin UI, navigate to Settings -> Security -> Security Headers to configure the content security policy, permissions policy, and referrer policy.

To export, go to Tools -> Deployments -> Plans, create a new deployment plan, and add the Security settings step. Execute the plan and download the result. Unzipping the archive reveals a Recipe.json with the settings for all three Security Headers tabs.

Convert Alerts to Dismissible Toasts

Notification messages generated by INotifier will now display as toast alerts. By default, only Success notifications are automatically dismissed after 5 seconds, while Error, Warning, and Information notifications remain visible until manually dismissed.

Developers can customize the dismissal timeout or disable automatic dismissal entirely. All notification types can also be manually closed by users using the X button.

This improves the user experience by preventing transient success messages from permanently occupying screen space, while ensuring more important notifications remain visible without affecting the layout or positioning of HTML components such as buttons.

Mike Alhayek also updated the docs of the Notifications module with code examples about how to send a notification, or how to customize the toast messages by overriding the Message and the NotifyMessages shapes.

Demos

Never Let Your SSL Expire Again - SSL Check Feature

Hisham Bin Ateya created SSL Check, a new feature that will be part of the Orchard Core Security module. Enable it under Tools -> Features. Once active, the Multi-Tenancy -> Tenants page shows a colored SSL badge next to each tenant domain indicating certificate expiration status.

The thresholds are configurable under Configuration -> Security -> SSL Checker. Tenants within the warning threshold get a yellow badge; those within the critical threshold get a red badge.

The feature also integrates with the Admin Dashboard: enable the Admin Dashboard feature, and a widget appears on the admin home page summarizing all domains and their expiration dates.

And it's still not all of it! A recording is available on YouTube!

News from the community

Sponsorship Spotlight: Antoine Griffard

Antoine Griffard has been contributing to Orchard since its earliest days (more than 15 years). In our new Sponsorship Spotlight series, he talks about what keeps him going: "If you give some time and effort to contributing, everything you did will be yours forever."

Read the full interview to hear his story, from his first MVP Summit to the upcoming Orchard Harvest conference in Vancouver this September.

Orchard Harvest 2026 Program

The Orchard Harvest 2026 conference will be held in Vancouver, and we look forward to seeing you all this autumn in Canada. Our confirmed dates for this year are September 10th and 11th.

Don't miss this limited-time offer: just $280 for two days of all-access learning and networking. Secure your early-bird tickets to the conference now!

The full Orchard Harvest 2026 program is live! Be sure to check out the conference's updated official website for the program!

As we move forward, we will keep community members informed of the details, and you will find every detail in this newsletter, too!

Don't miss the biggest Orchard Core event of the year!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 414 subscribers! We have started this newsletter to keep the Orchard community informed about the latest platform news. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Jint async scripting APIs

JavaScript global methods received the new GlobalMethod.AsyncMethod property, which is accessible in JavaScript as a function using the given name and the Async suffix. This is non-breaking, but we suggest using the new methods where applicable going forward. In cases where the method value is immediately returned, this is very simple, for example, replacing deleteContentItem with deleteContentItemAsync:

"ContentItemId": "[js: deleteContentItem('blogContentItemId')]"

can be replaced with

"ContentItemId": "[js: deleteContentItemAsync('blogContentItemId')]"

which works without any need to await, because the expression returns a JavaScript Promise object, which is automatically awaited by the engine.

So, the idea here is that we have async methods, like deleteContentItemAsync, which means we can call await on them. But at the same time, if we don't call await, then the new code will handle that, and await it.

If you check out the related page in the Orchard Core documentation, you can see the new versions of the functions.

Using the new version avoids a sync-over-async call that can cause a thread deadlock, so it's always preferable. Thanks for the contribution to Sára El-Saig!

CancellationToken to NotificationServices and use Result Pattern

This change by Mike Alhayek introduces support for cancellation tokens throughout the email and SMS sending infrastructure and improves code documentation by adding XML doc comments. The most significant changes include updating public APIs to accept CancellationToken parameters, propagating these tokens through internal calls, and enhancing method documentation for clarity and maintainability.

So, the IEmailService.SendAsync(), ISmsService.SendAsync(), IEmailProvider.SendAsync(), and ISmsProvider.SendAsync() methods now accept a CancellationToken. This is a source- and binary-breaking change for custom email services, providers, and event handlers. Update your implementations and overrides to include the new cancellationToken parameter.

Check out the release notes of v3.0, where you can find the mentioned changes under the Notifications Module and Email Interfaces sections.

Demos

Rethinking the Media Gallery - Now Powered by Vue 3

The goal of this feature is to migrate the Media Library to Vue 3. It means migrating all the components (for example, the Media Picker) to Vue 3. Here you can find the pull request containing the changes by Jasmin Savard.

This change also involves adding new media-related features. If you navigate to Tools -> Features and search for "media", you will see several new ones:

• The Media SignalR and Media SignalR - Azure features enable real-time media updates via SignalR. When enabled, changes to media files and folders are broadcast to connected clients. You can use SignalR locally as a SignalR host, where the tenant becomes the host of the SignalR server. SignalR will synchronize changes across browsers, so you will see them instantly.
• The Media TUS Uploads feature enables resumable file uploads using the TUS protocol. When enabled, it replaces the default chunked upload mechanism with the TUS standard, allowing uploads to be paused and resumed.
• The Media SignalR - Redis feature uses Redis as the backplane for real-time media updates, enabling multi-instance deployments.

Now let's quickly see the new Media Library in action!

The navigation is different; we have different icons at the top. We can go to a grid with images and to a table view with more details about the files, but without the images. We can set the thumbnail size and the number of how many items we want to display per page. It also saves the preferences in your browser's local storage.

We have new modals in the Media Library. If we create a new subfolder, we can set the folder name in this modal. Or if we want to move/copy a file to a new folder, we can select the destination folder in another modal. As you can see, we have toast notifications for actions that happen on the Media Library. If you upload files, you can see the Upload modal at the bottom-right with the progress bar and a pause button.

And it's still not all of it! If you want to see the new Media Library in action, head to YouTube for a recording!

News from the community

Case study: Long-term Orchard Core maintenance for the City of Santa Monica

Several years ago, we helped migrate santamonica.gov from Orchard 1 to Orchard Core. Since then, our collaboration has continued with a different but equally critical focus: long-term maintenance and reliability.

Over the past couple of years, our work has centered on the kind of improvements that are rarely visible from the outside, yet essential for any long-running public website:

• Keeping Orchard Core up to date through major version upgrades.
• Adding comprehensive automated testing, including accessibility, security, and visual regression checks.
• Improving developer experience with predictable local setup.
• Cleaning up and standardizing the codebase to make future changes easier.
• Identifying and resolving performance bottlenecks.

The goal was to leave the project in a state where development can continue safely and efficiently, without regressions, surprises, or accumulated technical debt.

As Sushmita Inamdar, Software Developer at the City of Santa Monica, put it:

"Lombiq continues to be an invaluable partner in maintaining and improving our Orchard Core platform… Their work behind the scenes has significantly improved the reliability, security, and maintainability of our platform."

We're grateful for the trust and the ongoing collaboration, and we're glad to keep supporting a mission-critical public website as it evolves.

If you run an Orchard Core site and are thinking about upgrades, testing, performance, or long-term maintenance, this case study may be useful for planning your next steps.

Do you run an Orchard Core site that needs upgrading, testing, performance work, or long-term maintenance? Get in touch with us, and we can help you plan the next steps.

Orchard Harvest 2026 Program

The Orchard Harvest 2026 conference will be held in Vancouver, and we look forward to seeing you all this autumn in Canada. Our confirmed dates for this year are September 10th and 11th.

Don't miss this limited-time offer: just $280 for two days of all-access learning and networking. Secure your early-bird tickets to the conference now!

The full Orchard Harvest 2026 program is live! Be sure to check out the conference's updated official website for the program!

As we move forward, we will keep community members informed of the details, and you will find every detail in this newsletter, too!

Don't miss the biggest Orchard Core event of the year!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 414 subscribers! We have started this newsletter to keep the Orchard community informed about the latest platform news. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Antoine: In 2009-2010, I discovered the Orchard project in version 0.5 on Codeplex. It was originally managed by a team of people at Microsoft. I knew Bertrand Le Roy, one of the project managers, whom I had met in 2007 in Redmond when I went to my first MVP Summit. A few months later, another developer I knew, Sébastien Ros, joined the team. In 2010, version 1.0 was released with ASP.NET MVC Razor views, and the project switched to an open-source approach. I started contributing to issues, docs, translations, and modules like Fields. An election was organized to select the first Steering Committee members. Bertrand was the benevolent dictator at that time. There was an Orchard gallery (which ran the first version of the NuGet Gallery) where you could deploy your own modules and themes. In 2012, the first conference was held in Santa Monica, where I was lucky to meet in person some of the contributors I had been in touch with. Among them, two young Hungarian students.

Gábor: I think we all know who those two Hungarians could be!

Antoine: Yes, that was the first time I met Zoltán and Benedek in person. If I remember correctly, there was no Lombiq at that time.

Gábor: You are correct: Lombiq was founded a year later, in 2013. We have just had our 13th anniversary. But they started contributing to Orchard and were part of the community even before Lombiq was founded. Speaking of which, why do you like contributing to Orchard?

Antoine: After using the Framework and CMS, I felt like I had to give back a little. I switched from someone who uses a tool to someone who contributes to make it better and help people. For me, if you keep something for yourself, it is lost, but if you give some time and effort to contributing, everything you did will be yours forever. If you think about it, the contribution is the reward itself.

Gábor: You are totally right. It's a very good feeling to see that the code you write could be part of something others will use or improve later. But what do you like most about Orchard?

Antoine: Technically, I really like its modularity and extensibility. It offers many modules out of the box, and you can extend them with your own modules and themes. What I like most about Orchard Core is that it has made me a better developer in so many ways.

Gábor: Are you contributing to other open-source projects too?

Antoine: Probably not enough (laughs), but I try to contribute to other projects like Blazor component libraries (e.g., Fluent Blazor UI), Microsoft documentation, and products (e.g., Aspire). Sharing my knowledge is an important part of being a Microsoft MVP.

Gábor: I know we started our discussion about some members of the community, but what do you think about the community in general?

Antoine: The weekly meetings and discussion forums like Discord make you feel like you're part of a community. And being able to meet people and travel all around the world for conferences like Orchard Harvest is priceless.

Gábor: You attended the last two Harvests as well. In 2024, we organized it in Las Vegas, and last year the conference took place in Prague, Czechia. And we will organize it again this year: The next Orchard Core conference will take place in Vancouver, Canada, on September 10th and 11th! Will you be able to join, Antoine? If I remember correctly, you attended every single Harvest so far.

Antoine: Hopefully yes, I'm working on it!

Gábor: Thank you for the interview!

Stay tuned for the upcoming parts of the Sponsorship Spotlight series! If you don't want to miss them, sign up for the Lombiq Technologies Newsletter and stay up to date with what's new, insightful, and happening at Lombiq.

Check out our Orchard Dojo newsletter too for news about Orchard!

Set up tenants faster with improved shared and preset database support

The idea here is that if you have a setup with multiple tenants on the same database, you will need some sort of prefix to distinguish which one belongs to which. Today, the UI doesn't even require you to select the pattern; only the prefix is there to use. But if you don't use the prefix, you might get an error. So the RequireTablePrefix lets you make it required. But then, if you don't want that altogether, maybe you will have some sort of auto-generated prefix, and then you don't have to prompt the user at all. You can say just make the prefix the same as the tenant name and use that pattern everywhere. It allows users to make the tenants a bit easier to follow by using a given pattern.

So, if you check out the release notes for Orchard Core 3, you can see a new set of configuration options for creating table prefixes in multitenancy. The new RequireTablePrefix option can require a table prefix, and the new TablePrefixPattern lets you create a Liquid configuration like ShellSettings.Name to force the prefix to use the ShellSettings.Name. And this way, you don't have to provide it; it will be computed automatically. Thanks for the contribution from Mike Alhayek!

Add Settings Recipe Step sections in the docs

We were missing some documentation on how to customize settings via recipe steps. So, we can configure all the settings, but there is no documentation on which properties to provide for each setting. This contribution by Mike Alhayek is fixing the gap between what we can do and how we can do it. If people don't know what to do, then they will never do it. And if the Agent doesn't find the example, it will not know what to write in the recipe.

It means that from now on, you will find a Recipe Configuration section for all modules with settings that can be configured via the Settings recipe step. Here you can find an example showing how to configure the Login, Registration, and Reset Password settings, etc.

Demos

Lock Down Your Health Checks

The OrchardCoreContrib.Modules repository contains a set of modules for Orchard Core that are driven by the community members who love Orchard Core. The repository contains several modules, and this time we will focus on the Health Checks Module, which provides health checks for your website. You can also add this module as a NuGet package to your project. Now, if you go to Tools -> Features and search for Health Checks, you will see four features:

• Health Checks: Provides health checks for the website.
• Health Checks Blocking Rate Limiting: Adds blocking behavior to the health checks rate limiter. Clients exceeding the limit are temporarily blocked to prevent DoS attacks.
• Health Checks IP Restriction: Restricts access to health checks endpoints by IP address.
• Health Checks Rate Limiting: Limits requests to health checks endpoints to prevent DOS attacks.

Let's see how we can configure and use those!

As you can see, we have an AllowedIPs array under Access, where we can set the collection of IP addresses permitted to access health check endpoints.

The RateLimiting provides configuration options for rate limiting applied to health check endpoints. Here you can see that we set the maximum number of concurrent permits to 5 and the time window for which rate limiting is applied to 10 seconds. The duration a client is blocked after the rate limit is exceeded is 10 seconds.

As you can see, the health check URL is /health. So, if we hit that, we will get a detailed response because ShowDetails is true, which lets us show the details of the checks' dependencies. The Status is Unhealthy because one tenant is not running (Tenant's health check is provided by the OrchardCoreContrib.Tenants module).

If we hit the endpoint more times than allowed within a given time frame, we will be blocked for 10 seconds, as specified by the BlockDuration property. And as always, if you want to see this module in action, head to YouTube for a demo of this module by Hisham Bin Ateya!

News from the community

Your website should integrate with your business systems

When visitors submit a form, your team shouldn't be copy-pasting data into CRMs, sending Slack messages, or updating spreadsheets by hand. That's slow, inconsistent, and doesn't scale. Orchard Core makes integration simple without requiring custom code by:

• Sending form submission data directly to Zapier, Make, or n8n.
• Triggering CRM updates, email workflows, and team notifications automatically.
• Receiving webhook calls from external systems to create or update content inside your CMS.

The result: your website stays stable while your business workflows evolve freely in the automation layer.

Ready to connect your website to your business systems?

DotNest's managed Orchard Core hosting lets you set this up without any infrastructure overhead. Check out our post for the details and get in touch to explore what's possible for your team.

Orchard Harvest 2026 Program

The Orchard Harvest 2026 conference will be held in Vancouver, and we look forward to seeing you all this autumn in Canada. Our confirmed dates for this year are September 10th and 11th.

Don't miss this limited-time offer: just $280 for two days of all-access learning and networking. Secure your early-bird tickets to the conference now!

The full Orchard Harvest 2026 program is live! Be sure to check out the conference's updated official website for the program!

As we move forward, we will keep community members informed of the details, and you will find every detail in this newsletter, too!

Don't miss the biggest Orchard Core event of the year!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 414 subscribers! We have started this newsletter to keep the Orchard community informed about the latest platform news. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Admin Theme in Orchard Core: The Developer cheat sheet

When building modules or custom admin pages in Orchard Core, knowing how to work with the Admin Theme is essential for creating a consistent and maintainable user experience. Whether you're styling forms or building custom editors, Orchard Core gives you a clean, framework-agnostic toolkit to do it right.

Ready to build better admin experiences in Orchard Core? Dive into the Admin Theme Conventions documentation added by our new contributor, Quoc Bao An Nguyen, and start crafting custom admin interfaces that are flexible, maintainable, and visually consistent, no matter which theme your users choose.

Skip the Admin Dashboard: Configure ReCaptcha programatically

You currently need to configure ReCaptcha settings from settings. This is a good and necessary way to do it, but for environment-based settings (like different ones for staging and prod), it'd be better to make them configurable via configuration providers as well. ReCaptchaSettings is almost ready for this. We can solve this in a similar way to what we have in a lot of other modules:

• Provide an extension method to do environment configuration, similar to ConfigureAzureADSettings().
• Check that everywhere where ReCaptchaSettings is used, it's used as an IOptions<ReCaptchaSettings> and not directly as site settings (except when the site settings are edited). E.g., ReCaptchaLoginFilter goes directly to the site settings instead of going the options way.

With the latest updates by ghazi1567, you can now streamline this process using the ConfigureReCaptchaSettings() extension method. This allows you to map your settings directly from appsettings.json, ensuring the SiteKey and SecretKey are applied automatically during application initialization. Check out the documentation of the ReCaptcha module for the details, and thanks again, ghazi1567, for your first contribution!

Demos

Route Smarter: Chat Response Handlers

There is a feature in the AI Suite that is extremely helpful if you are exposing a chat widget to the public. It can change the chat's response using a chat response handler. This allows you to handle cases, like handing over a connection or a chat happening with AI. It means, like, you start a conversation with AI, and then the AI can decide to route you to a real person. So, using Chat Response Handlers lets you register custom handlers that route prompts to external systems, such as live agent platforms (e.g., Genesys, Twilio, Flex, LivePerson), rather than to AI.

This enables scenarios like:

• Live agent handoff: An AI function detects the user needs human support and transfers the session to a live agent queue.
• Hybrid AI + human: AI handles initial triage, then a human agent takes over mid-conversation.
• Non-AI chat profiles: Configure a profile to skip AI entirely and route all prompts to an external system from the start.

Check out this recording on YouTube to see how Orchard can transfer you to a human agent via the AI Chat Admin Widget and Frontend Widget. In this demo by Mike Alhayek, you can see that the AI Suite sends over the session with the context to Genesys, where the user can continue the conversation with a human.

News from the community

Orchard Core 3.0

The community yesterday released the third major version of Orchard Core with several new features and additions! This release is packed with performance improvements, bug fixes, and a variety of enhancements, making it our best version yet. Whether you're building a new project or maintaining an existing one, Orchard Core 3.0 brings stability and power to your fingertips. Why Upgrade to Orchard Core 3.0?

• Enhanced Performance: Your sites and applications will run faster, smoother, and more efficiently.
• Rock-Solid Stability: We've squashed numerous bugs, ensuring a more reliable and enjoyable development experience.
• Seamless Development: By sticking to version control best practices, we've ensured no breaking changes in any patch or minor release, allowing developers to confidently create modules and libraries that will work across the entire 3.x series.

Prior to initiating this upgrade, thoroughly review the documented list of breaking changes (such as Orchard Core 3.0 requiring .NET 10) to ensure a smooth, hassle-free transition.

Orchard Core is available as a NuGet package that you can easily add to your ASP.NET Core solution. Here's how you can get started with Orchard Core.

As you can see from the release notes, Orchard Core 3.0 contains many new additions compared to the previous version. From week to week, we try to summarize the latest features of the new release to make sure you will get the most out of your new version! If you are curious about what you can achieve, you will find all the information you need in this blog post series over the coming weeks!

Lombiq at BeerUP Tech Fest

We had a blast at Digitalk-tech's BeerUP Tech Fest! It was indeed more like a festival, with two tracks of talks running late into the night and a festival atmosphere in the garden. Met many people from Budapest's wider tech community and made many valuable connections.

Márk Bartha, Zoltán István Lehóczky, Milán Keszthelyi, and Gábor Domonkos, as pictured, manned our table at the ViVeTech Nyrt, booth and engaged with attendees. Zoltán also gave the ".NET web architecture in regulated environments: CMS or custom development" talk, sharing our experiences working with clients in the healthcare, finance, insurance, construction, and government sectors.

Orchard Harvest 2026 Early Bird tickets!

We're excited to open registration for Orchard Harvest 2026!

This year, we've also created a short "convince your boss" one-pager to help you make the case for attending. It highlights the practical takeaways, business value, and networking opportunities waiting at the event.

If you want to learn from real-world Orchard Core use cases, get a better sense of where the platform is heading, and connect with experts and active community members, this is for you. We'll be sharing this year's speakers and topics over time, so stay tuned!

Secure your spot today for the early bird pricing and get ready to level up your skills at Orchard Harvest!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 415 subscribers! We have started this newsletter to keep the Orchard community informed about the latest platform news. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Mastering Lucene Query Syntax in Orchard Core

Lost in your content? Lucene's got the map. From fuzzy searches to regex wizardry, Orchard Core's query syntax lets you hunt down any document with pinpoint precision, wildcards, ranges, booleans, and all. Whether you're searching for "everything" (*:*) or something that almost matches, Lucene speaks your language.

Thanks to Manuel Tamayo Montero, you can now find a new guide in the Orchard Core documentation with several examples of operators, expressions, fuzzy searches, and wildcard searches.

Use Jint async scripting APIs

Jint 4.8 can now await promises and .NET task interop asynchronously. Orchard's JavaScript scripting paths were still executing through synchronous evaluation, which meant script-exposed async services had to block with GetAwaiter().GetResult().

This change by Sébastien Ros is about supporting async JavaScript scripts, but more importantly, supporting the asynchronous execution of any JavaScript script. Previously, the Evaluate method was not async; now there is an EvaluateAsync method in Jint. This way we don't have to call GetAwaiter().GetResult() on scripting, and we can just await the result. It allows workflows and other features relying on JavaScript to run asynchronously without blocking.

Demos

How to quickly spin off your Orchard Core site?

The idea is to have an Electron app for people who are not really technical, or for those who just want to experiment with Orchard Core and quickly spin off a site. Nick Jackson demos an application that lets you do that without going to an IDE.

If you hit the New button, you can choose between two different creation modes to set up your site:

• Express: Quick setup with sensible default. Here you just need to pick a name, email, and recipe.
• Custom: Full control over database port, directory, and more.

In both cases, you can select which modules and themes you want to install. For a custom installation, you can select which Orchard Core version to install, choose the recipe, the database provider, and so on.

So, it's just a quick experiment using a desktop app to see how it can run with Orchard. And as always, if you want to see how you can use this application, head to YouTube for a quick demo!

News from the community

Rebuilding DotNest.com: Orchard Core, Tailwind 4, and a more maintainable workflow

As you may know, we recently rebuilt DotNest.com (our managed Orchard Core hosting platform), treating it as more than a visual refresh. The project had three main focuses:

• Better Landing Page structure.
• Modernized Front-End Workflow.
• Practical AI-Assisted development.

Our post concludes that all three areas yielded real benefits: cleaner content management, faster UI development, and clearer insights into where AI assistance genuinely helps versus where human oversight is essential. That experience ultimately led to the Tailwind Agent Skills and Orchard Core Agent Skills repositories.

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.

Orchard Harvest 2026 Early Bird tickets!

We're excited to open registration for Orchard Harvest 2026!

This year, we've also created a short "convince your boss" one-pager to help you make the case for attending. It highlights the practical takeaways, business value, and networking opportunities waiting at the event.

If you want to learn from real-world Orchard Core use cases, get a better sense of where the platform is heading, and connect with experts and active community members, this is for you. We'll be sharing this year's speakers and topics over time, so stay tuned!

Secure your spot today for the early bird pricing and get ready to level up your skills at Orchard Harvest!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 416 subscribers! We have started this newsletter to keep the Orchard community informed about the latest platform news. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

How to create and install a custom module?

Did you know that with just a few configuration tweaks and a single project reference, you can extend Orchard Core CMS with your very own custom module that is fully integrated into the admin UI and discoverable at runtime? Thanks to Manuel Tamayo Montero, this guide in the Orchard Core documentation reveals the simple steps that most developers overlook when trying to get a custom module up and running.

Category filtering for Deployment Steps

If you have the Workflows feature enabled, you can let users visually implement business rules using flowchart diagrams. Whenever you add events or tasks to your workflow, the modal organizes them into categories, and you also have a filter to find the next executable step more easily.

And this is a nice, helpful experience for users, so why don't we have it for the deployment steps too? Mike Alhayek thought that the same UI could be helpful when adding Deployment Steps to Deployment Plans. To check it out, head to Tools -> Deployments -> Plans and click on the Add Deployment Plan button. Give it a name, then add steps to your plan. And as you can see on the screen below, the Available Steps modal now also shows categories, helping you find the step you want to add to your plan much more quickly.

Demos

New visual Layout Editor for Orchard Core

This time, we will see a visual drag-and-drop editor for arranging content type editor fields into tabs, cards, and columns in Orchard Core. Here you can find the repository for the Editor Layout feature developed by Nick Jackson.

By default, Orchard Core renders all parts and fields on a content type's editor in a single flat list. This module lets you organize them into a structured layout using a drag-and-drop interface, without writing any placement.json or code.

So, after adding this module to your Orchard Core web project as a project reference, we can set up our site. For the demo, we used the Blog recipe. Once our site is up, we need to enable the Editor Layout feature under Configuration -> Features. Let's try this out by modifying the content definition of the predefined Blog Post content type. To do that, we navigated to Content -> Content Definition -> Content Types, then clicked Edit next to the Blog Post content type. At the bottom of the content type editor, we will find a button labeled Editor Layout. Click on it and use the switch to enable the editor layout, which shows us a visual representation of what we can build in the editor.

Here we can arrange our parts and fields:

• Add tabs to create tabbed sections on the editor.
• Add cards within a tab to group fields in a bordered card.
• Add columns within a tab or card to place fields side by side.
• Drag items from the Available Items sidebar into tabs, cards, or columns.
• Reorder items by dragging them within or between containers.

First, we added a new column to the Content card placed on the Content tab. It means we now have two columns in the Content card, and both columns will be set to 50% width by default to fill the space. But of course, we can change the width if we want. Once we have that, we move the Banner Image field to this new column inside the Content card.

We can also add new tabs by clicking on the Add Tab button. In the Add Tab modal, we can set the name of the new tab. We decided to move the Autoroute Part to the default Content card of this newly created Settings tab. We can easily do that by selecting the Autoroute on the left and dropping this into this card. Orchard will automatically notice that we have already used this part in the Content tab and remove it from there.

Save this editor layout and edit our predefined Blog Post content item to check how our new editor for this content type will look. As you can see, the blog post editor reflects the layout we set up.

And you can build a much more complex editor by using this feature! If you are curious about how you can do that, head to YouTube for a recording!

News from the community

Orchard Harvest 2026 Early Bird tickets!

We're excited to open registration for Orchard Harvest 2026!

This year, we've also created a short "convince your boss" one-pager to help you make the case for attending. It highlights the practical takeaways, business value, and networking opportunities waiting at the event.

If you want to learn from real-world Orchard Core use cases, get a better sense of where the platform is heading, and connect with experts and active community members, this is for you. We'll be sharing this year's speakers and topics over time, so stay tuned!

Secure your spot today for the early bird pricing and get ready to level up your skills at Orchard Harvest!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 416 subscribers! We have started this newsletter to keep the Orchard community informed about the latest platform news. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Sort user roles alphabetically in the admin UI

Georg von Kries made this change to ensure that user roles are consistently displayed in alphabetical order across the admin interface. This affects role filters, user edit forms, and user role displays, improving usability and readability. Let's see some samples for this!

If you navigate to the admin UI of Orchard Core and head to Access Control -> Users, you can see all of the available users in your site. If you hit the Role dropdown, you can see the Filter by role list, where the roles are now ordered alphabetically. And if you hit Edit near any of the users, you can see the list of the roles that you can assign to the currently-selected user. As you can see, the roles here are also ordered alphabetically.

Add DocumentsAddedOrUpdated and DocumentsDeleted events to IDocumentIndexHandler

Mike Alhayek added new events needed to allow other projects to implement the IDocumentIndexHandler for synchronization, such as when an index is updated or when another data source is updated. It means these events help keep external systems in sync with changes to the document index.

The news events are:

• DocumentsAddedOrUpdatedAsync, that notifies the handler after documents have been added to or updated in a provider-specific index.
• DocumentsDeletedAsync, that notifies the handler after documents have been removed from a provider-specific index.

If we check it out quickly, we may notice how these new events are utilized across Orchard Core. As you may know, we have three different index managers in Orchard to support Lucene, Elasticsearch, and Azure AI Search. If we check out one, for example, the LuceneIndexManager.cs, you can see how we utilize the new events at the end of the DeleteDocumentsAsync and AddOrUpdateDocumentsAsync methods.

Demos

Let Your AI Agents Talk to Each Other - A2A in Orchard Core

One of the issues you will notice is that the more code you write using AI, the more you couple your code with your system. Long system prompts in your code come really nasty, really quickly if you have a whole lot of them. Mike Alhayek created a structure that lets you define AI templates for prompts and profiles. Let's see an example for each of them!

Prompt templates are discovered from module files and other registered Orchard template providers. The common Orchard pattern is to place them in a module under Templates/Prompts/. You can find one here, called SMS Conclusion Analysis.

The Prompts folders contain markdown files with prompts that support Liquid to generate the system prompt. So, you don't have to define it in the code. You can see that they contain a title,a description, etc., and, of course, the prompt itself. The good thing about that is you don't really have to couple your code with prompts. Everything is separated, and with the help of Liquid, it's really helpful because we don't have to have system code all over the place, and we can reuse it or inject one into another.

The other one is a set of templates for AI Profiles, which are very similar in structure. AI profile templates are the Orchard Core-friendly way to stamp out repeatable AI profile configurations inside the admin UI and recipes. Here you can see a sample of it, this one called Executor Agent. It's preconfigured; you can just apply it.

Now let's see how you can use these along with another new feature called the Agent-to-Agent Protocol (A2A). The A2A modules bring the Agent-to-Agent protocol to Orchard Core, enabling tenants to connect to remote agents or expose local agent profiles to other clients. We will demo all of these by navigating to the admin UI and clicking the Add Profile button on the Artificial Intelligence -> Profiles page. Here, you will notice the new Apply Template dropdown, which contains predefined templates from the markdown files. We don't need to use them, but if we do and select one, it prefills everything based on the template right after we click on the Apply button. Obviously, you can override and change everything here that you want.

If you notice, there is a new profile type, called Agent. By creating a new profile type called Agent, you're creating an agent accessible via the A2A protocol. Before accessing that profile, we need to enable the Agent-to-Agent (A2A) Host feature, which exposes all AI Agent profiles through the A2A protocol, enabling external agents and clients to discover and communicate with locally hosted agents.

Now we open another app provided by the AI Suite called A2AClientSample. The easiest way to have this is to set the CrestApps.Aspire.AppHost as the startup project of the solution, and run it. It will start an Aspire host, which will also set up this sample project for you. Once you have it, click on the Go to Agents button to discover all agents exposed by the A2A host, view their skills, and send messages. Here you can see that we created two agents, the Planner Agent and the Research Agent, via profile templates. We can access those two via the A2A protocol and send prompts to them using the Message text area.

And that's still not all of it! If you want to see these features in action, head to YouTube for a recording by Mike Alhayek!

News from the community

Who Are We Building the New OrchardCore.net For?

Nick Jackson started a proposal to identify the target audience for a redesigned OrchardCore.net website, which identifies two main groups.

The primary audience is the .NET Developers, who have already chosen .NET and are evaluating Orchard Core as a framework to avoid building common features (user accounts, permissions, multi-tenancy, etc.) from scratch. Three personas are outlined: architects/tech leads, developers building sites or products, and existing contributors. Key competitors named are Umbraco (for content sites) and abp.io (for business applications). These users want to quickly assess code quality, maintenance health, getting-started steps, and built-in features.

The secondary audience is the Business Decision-Makers, people who fund or approve platform choices but don't write code, like agency owners, product managers, CTOs, and clients whose agency chose Orchard Core for them. They care about cost, longevity, licensing, hiring availability, and plain-language explanations of what the platform does.

The core design philosophy is that, rather than trying to appeal to all developers, the site deliberately focuses on the .NET audience, so every page can be specific and relevant by using .NET terminology, naming .NET alternatives, and showing .NET code instead of being vague for everyone.

Who should the OrchardCore.net redesign speak to? Take a look at our audience proposal and share your thoughts. Do you agree with the personas? Are we missing anyone? Chime in, push back, and help shape the redesign's direction in this GitHub discussion.

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 417 subscribers! We have started this newsletter to keep the Orchard community informed about the latest platform news. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

File Upload Limit documentation

There was a question about how to set file upload size limits, and we came up with an idea to have a global solution so we don't have to set custom limits every time we create new actions. Hisham Bin Ateya added a new section to the Orchard Core documentation explaining how file upload limits work and how to customize them.

New Transliterate Liquid Filter

Sotiris Roussos introduced a new transliterate Liquid filter to the OrchardCore.Liquid module. It converts Unicode text (e.g., Greek, Cyrillic, Arabic, Chinese, etc.) into its closest ASCII/Latin representation using the AnyAscii library. It also means that, from now on, the Slugify string filter transliterates the provided string. The same applies to the Media Slugify module (if enabled) for Media files. Let's see how this works!

We set up our site using the Agency recipe, which enables the Templates module by default and provides a template for the Landing Page content type, which we can use for our small presentation. But first, don't forget to enable the Localization feature, as the transliterate filter is part of it.

Another thing to mention is the Media Slugify module, which transforms newly created folders and files into SEO-friendly versions by generating slugs. By default, transliteration happens when the feature is enabled. But there are configuration values you can use to enable or disable transliteration. You can read more about it in the Media Slugify module's documentation.

But for now, let's navigate to Design -> Templates and edit the predefined Content__LandingPage template. As you can see, we used the transliterate filter in line 6, which transliterates the non-Latin text to Ellinika.

Demos

How Does AI Stay Personalized Across Sessions?

The AI Memory feature of the AI Suite for Orchard Core provides persistent, user-scoped AI memory, enabling the AI to remember durable, non-sensitive preferences and background details for authenticated users across multiple conversations.

To test this quickly, clone the repository from GitHub, then head to Orchard's admin UI and select Tools -> Features. Here you will find three features related to memory:

• AI Memory: Provides persistent, user-scoped AI memory for AI profiles and chat interactions.
• AI Memory indexing using Azure AI Search: Provides services to index AI memory in Azure AI Search indexes.
• AI Memory indexing using Elasticsearch: Provides services to index AI memory in Elasticsearch indexes.

For now, we want authenticated user memories to be stored in the core AI Memory feature and indexed into Elasticsearch for semantic lookup, so we will enable the AI Memory indexing using Elasticsearch feature. After, we have to make sure that we have an AI Memory (Elasticsearch) index set up (we can do that under Search -> Indexes).

But why is it good for us, or what's the advantage of using AI Memory? We can use memory for durable, non-sensitive information, like:

• response style preferences,
• formatting preferences,
• active projects or workstreams,
• recurring topics the user commonly asks about,
• stable background context that the user explicitly wants remembered.

OK, now let's see it in action using a Profile. Head to Artificial Intelligence -> Profiles and create a new one or edit an existing AI Profile. Here, you will notice that we have ticked the Enable user memory checkbox. Now start a chat with this profile and ask something like, "Who am I?"

As you can see, the profile has information about me; it knows my name because it's stored in the memory (this information comes from the internal memory).

And as always, if you want to see this feature in action, head to YouTube for a recording by Mike Alhayek!

News from the community

Orchard Harvest 2025 recordings are up!

The 8th Orchard Harvest Conference was held in Prague on the 11th and 12th of November, 2025. It was an excellent opportunity to share knowledge, discuss development plans and ideas, and, foremost, meet the community.

We recorded every session, and they are now available on YouTube (the last recording will be available in a few hours)! If you haven't done so yet, subscribe to this YouTube channel, and you can find the playlist of last year's Harvest recordings here.

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 417 subscribers! We have started this newsletter to keep the Orchard community informed about the latest news on the platform. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

SMS Health Checks feature

The Health Checks module enables the health checks feature from ASP.NET Core, and the health check endpoint is available at /health/live for each tenant. This module now includes a health check that reports the status of the Twilio SMS service. Thanks for the contribution by Hisham Bin Ateya!

To make this work, don't forget to enable Health Checks and SMS features under Tools -> Features. Once you have that, head to Settings -> Communication -> SMS and set up your Twilio Account Info on the Twilio tab. As you can see here, the status is Healthy, which means we set up our Twilio account correctly and Twilio itself is working.

Reduce allocations by using .TryGet<> method over .As<>

The ISite interface now includes a new method, bool TryGet<T>(out T settings), to support checking for optional site settings without allocating a new instance when a settings object is missing.

This is a minor breaking change for custom ISite implementations, which must now implement this method.

So, if you check out the changes in Orchard, you can see that we prefer .TryGet<> method over .As<> to reduce allocations, and prefer .TryGet<> and .GetOrCreate<> extensions to improve readability. Thanks for the contribution by Mike Alhayek!

Demos

Content Transfer module

This time, Mike Alhayek introduces the new Content Transfer module, which provides bulk import and export of content items using Excel files. You can find the code for this module in this pull request.

First, let's head to Tools -> Features and enable the Content Transfer module to import and export content to and from Excel files. This allows us to configure a content type to make it importable and exportable.

Let's say we want to make the Article content type importable and exportable. To do that, we need to navigate to Design -> Content Definition -> Content Types and hit Edit near the Article one. Put a tick in the Allow bulk import and Allow bulk export checkboxes.

Once you have that, you can go to Content, where you will see the two new options: Bulk Export and Bulk Import. We want to export, so we select the Bulk Export option and click the Export button in the upper right. We select the Article from the Content type drop-down (that's the only content type we can export right now), and if we select Partial Export as the Export scope, we can filter down the data. We can filter by owners or version, or specify the date range for created and modified. For now, we simply export all published and click the Export Data button.

When you do that, it provides you with these files in two ways. If there are only a few items, it returns the file in real time. If there are too many, it will queue them for later access. And to access it later, you can use the list on the Bulk Export page to download the data you require.

If we want to import data, we need to select the Bulk Import option from the menu. Hitting the Import button in the top-right corner lets you select the content type you want to import. First of all, based on the content type, you can see the file's requirements, such as accepted file formats and file size limits. Under you can see the column requirements, such as which fields are required. You can also download a template to see a sample of the accepted file format.

Hitting Upload will start importing the records in the background. At the list on the Bulk Import page, you can see the progress of the import, and the errors if you have any (like "Your permalink is already in use" if the AutoroutePart_Path contains an existing permalink).

As you can see, the Bulk Import page shows we imported 232 articles, and the process completed without any errors. If we navigate to Content -> Content Items, we can see several Article content items that we just created a few minutes ago.

And as always, if you want to see this feature in action, head to YouTube for a recording!

News from the community

A new website using Orchard Core: JobsIreland

At JobsIreland, they aim to help people to get jobs and help employers connect with the right people. Whether you're looking for your next job or finding the right person to join your team, JobsIreland can help you. Check out their Orchard Core site here!

If you are interested in more websites using Orchard and Orchard Core, don't forget to visit Show Orchard. Show Orchard is a website that showcases representative Orchard CMS and Orchard Core websites from around the internet. Ryan Drew Burnett started it, but since he no longer works with Orchard, it is now maintained by our team at Lombiq Technologies. Oh, and in case you haven't heard about it yet, Show Orchard is also running on Orchard Core in DotNest for more than two years now! Here's the case study about how we migrated it from Orchard 1!

If you're considering migrating your Orchard 1 website to Orchard Core, this is an excellent time. Should you have any questions or encounter challenges, don't hesitate to reach out to us. We're always ready to bring our expertise to your unique project needs. Get in touch with us today, and let's start making your Orchard Core website even better!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 418 subscribers! We have started this newsletter to keep the Orchard community informed about the latest news on the platform. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Improve feature dependency display and interactivity

There is a minor UI issue on the Features page: the dependency tags for some features can be crowded because they recursively list all dependencies for a module.

Hisham Bin Ateya had an idea to fix this by not listing all the dependencies here. And after a discussion with Georg von Kries, the final decision was to show only the direct dependencies by default. Transient dependencies are hidden by default and revealed by clicking the ellipsis icon, which then displays a Show indirect dependencies tooltip.

As you can see, we are on the Features page under Tools, and we hover over the ellipsis icon next to the Layers feature. The Layers feature has three direct dependencies (Widgets, Scripting, Rules), and clicking the ellipsis icon shows the indirect dependencies as well.

New protect global method provider

Mike Alhayek added a new global method provider, protect, to the list of JavaScript methods provided by Orchard Core, which can be used to protect the specified value using the ASP.NET Core Data Protection API with the given purpose string. Let's see how it's working!

First, we navigated to Tools -> Features and enabled the View or Download Content as JSON feature, which added the JSON Import option under the Tools -> Deployments submenu. Here you can see that we stored our my-secret-value secret in the ApiKey setting, which is part of the MyModule module.

Please note that the protect function is intended for use only in development and testing scenarios. Storing secrets in recipe files for production environments is not recommended and should be avoided. Use a secure secret management solution (e.g., Azure Key Vault, environment variables) for production deployments.

Demos

AI Initial Prompt Behavior and AI Chat Session Analytics

In the Profiles now, you have more power, more capabilities to do more things in the AI Suite, like data processing after the session has ended.

But before that, there is another thing that Mike Alhayek added, which is to set up an initial prompt. If the initial prompt is enabled on the profile, the session is created immediately with an assistant message from the configured Initial prompt, which appears in chat history when the page loads or when a new session is started. It's a nice-to-have feature, for example, for chat widgets, where the chat widget can immediately welcome the user with some initial message. We have a profile called GitHub profile, and immediately after we start a new chat session with it, it greets us with the initial prompt we provided.

Now let's move on to the Data Processing & Metrics tab. If you want to extract data or do something with the data for a chat session, you can enable data extraction by putting a tick in the Enable data extraction checkbox, and you can add extraction entries by clicking the Add Entry button. Here you can see we say to extract the customer's first name, last name, and email address.

There is another option called post-session processing, which you can enable by putting a tick in the Enable post-session processing checkbox. Here, you can add tasks you want to do after the session ends. Like, create a task here that just generates a summary of the conversation and sends me an email. In this case, we will know what people are doing with our chat widgets. And in the Instructions, we say to create a summary, use the sendEmail tool, and set up the email subject, body, and so on.

You can also enable session metrics. When you do that, session metrics such as usage, token consumption, response latency, and user feedback are captured for analytics. Metrics can be viewed in the Chat Analytics dashboard. The other thing you can do is to enable conversation metrics. When enabled, AI evaluates each session against defined goals and assigns scores to measure session success and conversion rates. This operates independently of session metrics.

Now let's talk about analytics! The AI Chat Session Analytics feature provides comprehensive analytics and reporting for AI chat sessions. By using it, you can track conversation metrics, user engagement, model performance, and user satisfaction through an admin dashboard. Once you enable the AI Chat Session Analytics feature under Tools -> Features, you will find the analytics dashboard under Artificial Intelligence -> Reports -> AI Chat Session Analytics. The analytics dashboard provides a comprehensive view of AI chat performance through multiple report sections. You can use the filters panel at the top to narrow results by date range and AI profile.

And as always, if you want to see this feature in action, head to YouTube for a recording by Mike Alhayek, and don't forget to check out the official documentation to read more about the dashboard and the metrics!

News from the community

Speaker application deadline for Orchard Harvest extended to May 15

The next Orchard Core conference will take place in Vancouver, Canada, on the 10th and 11th of September.

Do you have an interesting Orchard Core-related topic that you'd like to present to the community? Development techniques, memorable case studies, and useful experiences that you'd like to share?

This year's leading themes:

• From CMS to content platform: where Orchard Core fits in 2026.
• Automation superpowers: AI tools, recipes, and workflows in everyday projects.
• Performance and reliability in Orchard Core.
• Looking beyond Orchard Core 3.0: what’s next for the platform and community.

Application form: https://forms.office.com/pages/responsepage.aspx?id=Wt6elek45kStyIVVO-uCICDdeeZFbXdAlSWTkdgpZAtUQzA3UzVNUERJTk4zVlEwRUtXNkM2SlI4Sy4u

Apply to be a speaker by the 15th of May, midnight, anywhere on Earth! We'll notify you whether your talk is selected for Harvest in 1 or 2 weeks after the application period. The chosen speakers will receive complimentary tickets for the event.

The 8th Orchard Harvest Conference was held in Prague on the 11th and 12th of November, 2025. We recorded every session, and are currently publishing them on the Orchard Core YouTube channel. The videos are published every Monday, Wednesday, and Friday at 4:00 PM UTC. If you haven't done so yet, subscribe to this YouTube channel for the Harvest videos and some inspiration if you are considering being a speaker this year! Here you can find the playlist for last year's Harvest recordings.

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 419 subscribers! We have started this newsletter to keep the Orchard community informed about the latest news on the platform. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Support static data migration methods

Public static data migration methods are now supported for Create, CreateAsync, UpdateFromX, UpdateFromXAsync, Uninstall, and UninstallAsync, so CA1822 suppressions are no longer required for migration steps that don't use instance state. It means that all methods could now be static if we don't use services, and we can remove the warnings that say mark members as static.

Make List Part pagination configurable

From now on, for the List Part, you can choose to use the current PagerSlim, which just shows next and previous, or use page numbers as well. But don't forget that showing page numbers, too, requires an additional database query to determine the total item count. By default, we are still using PagerSlim. Thanks to Jack Liu for his first contribution!

We can try this out quickly by setting up our site using the Blog recipe. The Blog recipe provides us with the Blog content type, which has the List Part attached. If we navigate to Design -> Content Definition -> Content Types and click Edit next to Blog, we can find the attached List Part, where we can see the new Show full pager checkbox.

Now, let's see the differences between using a full pager and not using one. On the left side of the screen, we can see the full pager in use. In this case, you can see the page numbers and the << >> arrows to be able to jump to the first and the last page of the list. The right side of the screen shows you the PagerSlim usage, where you can only navigate to the previous and next pages.

Demos

Copilot Integration

Let's continue our journey with the AI suite, this time with the AI Copilot Orchestrator!

If you navigate to Tools -> Features and enable the AI Copilot Orchestrator feature, it will provide a GitHub Copilot SDK-based orchestrator for AI chat sessions. Then, you can go to Settings -> Artificial Intelligence, where you will see a new Copilot section. You can set the authentication type and choose between GitHub Signed-in User and API Key (BYOK). The API Key can be used if you have this service hosted in Azure. For the sake of the demo, we chose the GitHub signed-in user authentication type and followed the steps mentioned to create a GitHub app.

Now, we can go to Artificial Intelligence -> Chat Interactions, where we can create a new chat or continue an existing one. Here you can select the orchestrator to use for this chat interaction. The orchestrator controls how tools are selected and how the AI execution loop is managed. If you select the GitHub Copilot Orchestrator here, the site will ask you to log in to your GitHub account. Once you have it, a new drop-down will display where you can select the Copilot model to use for this interaction.

Copilot will be aware of all the capabilities that you select under the Capabilities tab, and it is also aware of the documents that you can attach under the Documents tab. And the same applies to profiles. You can reach profiles under Artificial Intelligence -> Profiles, where you can edit/create profiles and set the orchestrator nearly the same way. Here you can read more about Profiles and Chat Interactions.

And as always, if you want to see this feature in action, head to YouTube for a recording by Mike Alhayek, and don't forget to check out the official documentation about the Copilot Integration!

News from the community

Speaker application for Orchard Harvest 2026 and Orchard Harvest 2025 recordings

The next Orchard Core conference will take place in Vancouver, Canada, on the 10th and 11th of September.

Do you have an interesting Orchard Core-related topic that you'd like to present to the community? Development techniques, memorable case studies, and useful experiences that you'd like to share?

This year's leading themes:

• From CMS to content platform: where Orchard Core fits in 2026.
• Automation superpowers: AI tools, recipes, and workflows in everyday projects.
• Performance and reliability in Orchard Core.
• Looking beyond Orchard Core 3.0: what’s next for the platform and community.

Application form: https://forms.office.com/pages/responsepage.aspx?id=Wt6elek45kStyIVVO-uCICDdeeZFbXdAlSWTkdgpZAtUQzA3UzVNUERJTk4zVlEwRUtXNkM2SlI4Sy4u

Apply to be a speaker by the 5th of May, midnight, anywhere on Earth! We'll notify you whether your talk is selected for Harvest in 1 or 2 weeks after the application period. The chosen speakers will receive complimentary tickets for the event.

The 8th Orchard Harvest Conference was held in Prague on the 11th and 12th of November, 2025. We recorded every session, and are currently publishing them on the Orchard Core YouTube channel. The videos are published every Monday, Wednesday, and Friday at 4:00 PM UTC. If you haven't done so yet, subscribe to this YouTube channel for the Harvest videos and some inspiration if you are considering being a speaker this year! Here you can find the playlist for last year's Harvest recordings.

Bringing Orchard Core into the classroom at Óbuda University

Ever wonder how a CMS can make university courses more practical? At Óbuda University, Orchard Core did just that. Students learn ASP.NET Core by building live sites on DotNest. They go through milestones, create custom forms and workflows. We talked with our project leader, Gábor Domonkos, about how it started, what students build, and why it prepares them for real careers.

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.

Check out the full interview here!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 419 subscribers! We have started this newsletter to keep the Orchard community informed about the latest news on the platform. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Warn against unsafe Liquid output in SQL queries

A SQL query is actually a Liquid template. This allows your queries to be shaped based on the parameters it gets. But you could srew up with SQL and Liquid if you start by injecting Liquid in a value, as you can see below. Because in that case, you can inject any SQL and expose all your databases. So, do not inject user-provided values directly with Liquid output expressions, as this can lead to SQL injection.

Use SQL parameters (@name or @name:default) for all user-provided values, and only use Liquid templates to change the shape of the query.

This change by Georg von Kries adds some validation, so whenever you edit a SQL query like the one we mentioned, it will tell you not to use this kind of usage in Liquid. The SqlLiquidOutputExpressionDetector will detect the issues based on the resolved FluidParser. What matters here is the OutputStatementDetector, which inherits from AstVisitor in Fluid and lets you detect specific statements. Here you can see the VisitOutputStatement, which checks for curly braces; when it finds them, the ContainsOutputStatement checks whether they contain curly braces. And in this case, we emit a warning to let users know to be careful when doing that.

And we can easily try it out by navigating to Search -> Queries -> All Queries and adding the query we mentioned above. Once we hit save, Orchard warns us that potentially unsafe Liquid output expressions ('{ ... }') were detected in this query template.

Add IJSLocalizer infrastructure and framework-agnostic JavaScript localization helpers

This is about providing localization for JavaScript files. In a nutshell, this will load the localization from the PO files and make it available in JavaScript.

When a Vue, TypeScript, or plain JavaScript component needs translated strings, it cannot call IStringLocalizer directly. IJSLocalizer bridges this gap: each module registers one implementation that knows how to map a group name to a dictionary of localized strings, which a Razor view or layout can serialize and pass into a scoped module entry point before the script runs. Check out the documentation of the JavaScript Localization to see how you can register a custom implementation, pass localizations to the browser, use localizations in JavaScript or TypeScript, and more with examples!

Demos

AI Chat Admin widget and Frontend widget

Let's continue our journey with the AI suite, this time with the widgets!

If you head to Design -> Widgets and hit the Add Widget button for one of the defined Zones, you will find a new option called Artificial Intelligence Chat. Once you have it, you can select whichever profile you want to use with this widget. If you are not familiar with AI profiles, you can check out our previous post or head to the official documentation for CrestApps Orchard Core to learn more. Once you select your profile and navigate to the frontend of your site, you will notice the new AI Chat widget there, and you can start a chat with it.

The other new feature that we want to highlight today is called AI Chat Admin Widget, which provides a floating AI chat widget on every admin page, allowing users to interact with a predefined AI profile. You can enable it under Tools -> Features. Once you enable it, you can configure it under Settings -> Artificial Intelligence, where you will find a new section called Admin Widget. Here, you need to select the API Profile to use for the admin widget. Users with the appropriate permission can chat with this profile from any admin page. But you can also set the maximum number of previous chat sessions to display in the widget history panel and the primary color for the admin chat widget. After that, you will see a UI similar to the frontend, with the same capabilities.

And it's still not all of it! If you want to see these features in action, don't forget to head to YouTube for a demo by Mike Alhayek!

News from the community

Speaker application for Orchard Harvest 2026 and Orchard Harvest 2025 recordings

The next Orchard Core conference will take place in Vancouver, Canada, on the 10th and 11th of September.

Do you have an interesting Orchard Core-related topic that you'd like to present to the community? Development techniques, memorable case studies, and useful experiences that you'd like to share?

This year's leading themes:

• From CMS to content platform: where Orchard Core fits in 2026.
• Automation superpowers: AI tools, recipes, and workflows in everyday projects.
• Performance and reliability in Orchard Core.
• Looking beyond Orchard Core 3.0: what’s next for the platform and community.

Application form: https://forms.office.com/pages/responsepage.aspx?id=Wt6elek45kStyIVVO-uCICDdeeZFbXdAlSWTkdgpZAtUQzA3UzVNUERJTk4zVlEwRUtXNkM2SlI4Sy4u

Apply to be a speaker by the 5th of May, midnight, anywhere on Earth! We'll notify you whether your talk is selected for Harvest in 1 or 2 weeks after the application period. The chosen speakers will receive complimentary tickets for the event.

The 8th Orchard Harvest Conference was held in Prague on the 11th and 12th of November, 2025. We recorded every session, and are currently publishing them on the Orchard Core YouTube channel. The videos are published every Monday, Wednesday, and Friday at 4:00 PM UTC. If you haven't done so yet, subscribe to this YouTube channel for the Harvest videos and some inspiration if you are considering being a speaker this year! Here you can find the playlist for last year's Harvest recordings.

DotNest has a new look!

The previous site was starting to show its age. Not just visually, but also in day-to-day site management UX. So we took a step back and rebuilt the frontend from the ground up.

The new site is built with Tailwind CSS and a much more user-friendly content management approach. Our goal was a simple, straightforward UX that stays out of the way of the content, no unnecessary fluff, just clarity and focus. Stay tuned for an in-depth case study!

Take a look at this post here, and if you're curious, you can create Orchard Core sites here for free!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 419 subscribers! We have started this newsletter to keep the Orchard community informed about the latest news on the platform. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Independent Render Liquid and Sanitize HTML settings for HTML and Markdown components

The current SanitizeHtml settings' hint could be a little bit misleading, and enabling or disabling it causes potentially unwanted behavior because the hint only refers to preventing custom scripts, which is true, but it does much more by default. This, in itself, is trivial to fix. However, the SanitizeHtml setting also governs whether Liquid markup is rendered. If SanitizeHtml is false, that means Liquid is rendered. This prevents a simple use case where (script) sanitization is desired, but Liquid should still be rendered.

Regardless of the setting, the Liquid code is always validated. This is problematic when Liquid code is included as a code sample (in a <code> block) and is invalid, e.g., because it references a Liquid tag that is not available in the current system. This affects HtmlBody Part, Html Field, Markdown Part, and Markdown Field.

Let's see Benedek Farkas's solution to this issue! If you set up your site using the Blog recipe, you will get a predefined Blog Post content type with the MarkdownBody Part attached. If you edit the settings of the attached MarkdownBody Part, you will notice the new Render Liquid option, which lets you control whether your Liquid markup is rendered or displayed raw. Please note that the Liquid rendering support is here only for backward compatibility and will be removed in version 4.0. As you can see, both settings are false in our case.

Now, let's create a new Blog Post with some sample content. As you can see in the screen below, the Liquid code is not validated because the Render Liquid option is disabled.

New Data Localization Liquid filter

And while we are talking about Liquid, let's take a look at a new Liquid filter by Hisham Bin Ateya, that localizes dynamic data string using the current culture. We fire up the blog post that we created earlier and make sure that the Render Liquid option is set to true. Then we have to make sure that our site supports multiple cultures under Settings -> Localization -> Cultures. We used the Dynamic Translations UI under Settings -> Localization -> Dynamic Translations to add a Hungarian translation for the Blog Post content type. If that UI is new to you, it's OK; that's quite a recent addition that you can read about in detail in this post.

Now let's see how that filter works! As you can see, we want to display the localized value of the Blog Post string, and the context for the string is Content Types. If we publish this content item and view it in the front end, we will see that the site displays the text Blog Post as Blogposzt.

Demos

AI Documents for Chat Interactions and Chat Sessions

We will continue the demo from last week, where we discussed the AI Data Source module of the AI Suite, which provides AI data source management, knowledge base indexing, and RAG search capabilities for Orchard Core. If you haven't read it yet, you can find it here.

Let's say we don't want to have only data in the indexes; we also want to use the uploaded documents, work with them, and ask questions about them. The features called AI Documents (OpenXML) and AI Documents (PDF) extend the AI Documents feature by allowing PDF and OpenXML files (ie, docx, xlsx, pptx). If we enable the AI Documents for Chat Interactions feature, we will be able to upload documents in the Chat Interactions UI.

Now we can go to Artificial Intelligence -> Chat Interactions, where we can start a new chat or continue an existing one. You will notice the Documents tab, which allows you to attach documents to chat against your own data. The content will be extracted and used as context for AI responses. But as you can see, it warns you to select an index profile for indexing documents in chat interactions.

To do that, we need to navigate to Settings -> Artificial Intelligence and select an index profile.

Now we can go back to the Chat Interactions UI, attach documents, and ask questions like "summarize the file". AI can do that because the document is processed and indexed, so we can retrieve data from the index.

There is another feature called AI Documents for Chat Sessions, which provides document upload and Retrieval-Augmented Generation (RAG) support for AI Chat Sessions and Widgets. The difference between Chat Interaction and Chat Session is that Chat Interaction is a playground that you can reach under Artificial Intelligence -> Chat Interactions, the one that we showed you previously. There is nothing preconfigured.

If you want to have a Chat Session, you have to create a Profile first under Artificial Intelligence -> Profiles. A Profile allows you to preconfigure system instructions, setting up an initial prompt, the Profile Type, and so on. But what's interesting for us here is the content of the Documents tab. If you enable the AI Documents for Profiles feature, you can allow Documents and Attachments in this tab, which means users can upload documents to chat sessions using this profile, as you can read. If we upload a file here and create a new chat based on the profile (which we can do by clicking on the Actions button and select the New chat from the drop-down menu near the profile under Artificial Intelligence -> Profiles), we can chat about the content of the uploaded document without having the need to upload the given documents again and again because it's preconfigured.

And it's still not all of it! If you want to see these features in action, don't forget to head to YouTube for a demo by Mike Alhayek!

News from the community

Speaker application for Orchard Harvest 2026 and Orchard Harvest 2025 recordings

The next Orchard Core conference will take place in Vancouver, Canada, on the 10th and 11th of September.

Do you have an interesting Orchard Core-related topic that you'd like to present to the community? Development techniques, memorable case studies, and useful experiences that you'd like to share?

This year's leading themes:

• From CMS to content platform: where Orchard Core fits in 2026.
• Automation superpowers: AI tools, recipes, and workflows in everyday projects.
• Performance and reliability in Orchard Core.
• Looking beyond Orchard Core 3.0: what’s next for the platform and community.

Application form: https://forms.office.com/pages/responsepage.aspx?id=Wt6elek45kStyIVVO-uCICDdeeZFbXdAlSWTkdgpZAtUQzA3UzVNUERJTk4zVlEwRUtXNkM2SlI4Sy4u

Apply to be a speaker by the 5th of May, midnight, anywhere on Earth! We'll notify you whether your talk is selected for Harvest in 1 or 2 weeks after the application period. The chosen speakers will receive complimentary tickets for the event.

The 8th Orchard Harvest Conference was held in Prague on the 11th and 12th of November, 2025. We recorded every session, and starting next Monday, we will begin publishing them on the Orchard Core YouTube channel. The videos will be published every Monday, Wednesday, and Friday at 4:00 PM UTC. If you haven't done so yet, subscribe to this YouTube channel for upcoming Harvest videos and some inspiration if you are considering being a speaker this year! Here you can find the playlist for last year's Harvest recordings.

Event management backend for one of the largest retailers - Avastec case study by Lombiq

When a live, high–traffic event platform needs new features urgently, you don't get the luxury of rewrites or downtime.

That was the situation when Avastec asked us to take over and continue the development of an Orchard Core–based headless event management backend used by one of the world's largest retailers.

The system was already in production, powering a public Node.js frontend. The goals were clear:

• ship new functionality quickly,
• improve performance and reliability,
• keep upgrades safe and traceable,
• all without disrupting users.

Our work focused on long-term maintainability under real delivery pressure:

• Replacing recipe-based data migrations with code-based migrations for better traceability.
• Introducing automated UI tests to protect core user journeys.
• Delivering new features like ticketing, GDPR integrations, multi-brand rollout, and QR code-based entry management.
• Adding observability via Azure Application Insights to support stable operations.

All of this was done incrementally, without breaking the live experience.

As Steve Taylor, CTO and Founder of Avastec, put it:

"They (...) delivered improvements without disrupting a live, high-traffic platform… balancing rapid feature delivery with long-term maintainability and performance."

This project is a good example of what Orchard Core enables when combined with disciplined engineering practices: fast change, low risk, and systems that keep improving instead of accumulating debt.

Read the full case study here!

Do you want to launch an event management platform on Orchard Core? We have actually built several more too, get in touch with us!

Orchard Dojo Newsletter

Lombiq's Orchard Dojo Newsletter has 421 subscribers! We have started this newsletter to keep the Orchard community informed about the latest news on the platform. By subscribing to this newsletter, you will receive an email whenever a new post is published to Orchard Dojo, including 'This Week in Orchard', of course.

Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here!

If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!