Our blog contains the activity stream of Orchard Dojo: general news, new resources or tutorials are announced here.

Help shape Orchard Core's new website, a new website using Orchard Core - This week in Orchard (17/07/2026)

When you add a custom settings page, does it look like it belongs in the admin UI?

When you utilize workflow activities, does JavaScript syntax have to be the only option?

After checking out this week's Orchard news, both have better answers.

Thanks to Mike Alhayek, admin forms across settings and configuration pages now use the same ocat-* CSS class conventions, replacing legacy Bootstrap and Orchard-specific helpers. And all workflow tasks that previously only supported JavaScript now also support Liquid, with a new LiquidTask added to match ScriptTask.

Also this week: Nick Jackson's Orchard Core website redesign is open for community feedback, and GoRide joins the showcase of sites running on Orchard Core.

Read on for the details, or jump to the section that matters to you!

Latest tutorials

Step away from that Node.js
sara.el-saig
How we reduced our app's server-side latency in Azure by 98% while lowering cost by 28%
zoltan.lehoczky

Featured tags

This week in Orchard
Documentation
Announcement
Admin UI
Orchard Harvest
Workflows
Localization
Media Library
Liquid
Tutorial
Content field
Shape
Theme
Role
Recipes
Performance
Multi-tenancy
Permission
Query
Permissions
Security
Orchard Harvest 2025
Orchard Core
Development
Orchard Core Nuggets
Dojo Course
Content part
Content management
Widget
Admin menu
Community resource
Caching
Search
Training
DotNest
Module
Resource manifest
Flow Part
Orchard Harvest 2026
Background task
Elasticsearch
Database
GraphQL
Extensions
AI
Azure
SQL Server
Event handlers
ASP.NET Core
Azure AI Search feature
OpenAI
Content model
Placement
Navigation
Authorization
Translation
Admin Dashboard
Migration
Tag Helpers
Orchard Harvest 2024
Bag Part
Video
JavaScript
Facebook
Crowdin
Orchard Harvest conference
Click to deploy
Shortcodes
Node.js
SMS
Forum favorites
IIS
Multi-node setup
Social
File storage
Advanced
Upgrade
Orchard 1.x
Harvest 2014
Orchard Harvest Seattle
Publishing
MSBuild
Update Content Workflow Task - This week in Orchard (17/04/2020)
NuGet
OpenAPI
GitHub Actions
Admin Dashboard Widgets
Security Scanning
Case study
Authentication
Lucene
MCP
eInvoicing
Hosting
Agent Skills
API
Harvest Challenge
Microsoft
How-to
Update
Orchard Harvest 2017
Sitemaps
Debugging
User Picker Field
Audit Trail module UI improvements
Archive Later Feature
Named style and script Tag Helpers
This is Lombiq! - This week in Orchard (09/05/2020)
Pager
Lombiq
SEO
UI Testing Toolbox
ReCaptcha
Assets Manager
Fluid
Cloud
Survey
Validation
Company
Hungary
SQL CE
IDependency
Event bus
Projector
NHibernate
LazyField
Dojo
Model binder
Scheduled task
Antispam
C# scripting
Beginners
InfoSet
Orchard 1.8
New Orchard Dojo Trainer
Orchard Beginner
Getting Started with Orchard CMS
Introducing Abhishek Luv
Orchard Dojo Trainer!
Orchard CMS Workshop
Orchard CMS Workshop In Mumbai
Orchard
Owin
SQL Server 2016
SQL Server Management Studio
SQL Server Management Studio 2016
Troubleshooting
Windows 10
day 1
day 2
Dojo Course 2
Sortable lists
IScopedDistributedCache - This week in Orchard (17/01/2020)
headless recipe
jsonparse Liquid filter - This week in Orchard (24/01/2020)
Taxonomy and contained content items routing
Culture picker on the Setup page
CodeMirror editor for TextField - This week in Orchard (28/03/2020)
Scoped Liquid TemplateContext
Template Azure Blob with Liquid - This week in Orchard (10/01/2020)
Favicon
Breadcrumbs
Exception
Content Picker Menu Item
Kast case study - This week in Orchard (02/05/2020)
Click to deploy improvements
autoroute container routing - This week in Orchard (24/04/2020)
Audit Trail - This week in Orchard (31/07/2020)
Swagger
Taxonomy Localization - This week in Orchard (12/06/2020)
Orchard branding
Assign Role permissions - This week in Orchard (28/03/2021)
content
Secrets module
JSON Recipe Deployment Step
Tenant Feature Profiles - This week in Orchard (14/10/2021)
Notifications Feature - This week in Orchard (23/09/2022)
Add title to background tasks and improve the UI
Lombiq Node.js Extensions - This week in Orchard (17/02/2023)
support login via username or email address for OpenID - This week in Orchard (28/07/2023)
Shape Tracing Helpful Extensions
Alt and Class attributes for the Image Shortcode - This week in Orchard (28/08/2020)
Short codes
new content filters - This week in Orchard (22/05/2020)
How to add a culture URL segment for localization in Orchard Core - Orchard Nuggets
Zed Attack Proxy (ZAP)
Orchard Dojo
Alias
Menu
Orchard Core Commerce
OAuth
EN 16931
XRechnung
ZUGFeRD
Factur-X
UpCloud
Exoscale
Schema
Schematron
Validator
SaxonJS
OpenID
ASP.NET Aspire
Razor
Copilot
Interview
Sponsorship Spotlight
SSL
Notifications
All tags >

How to localize content items? - Orchard Core Nuggets
So you want to create an Orchard Core website that presents its content in multiple languages. There are many parts of this, but what about content items? How do you make them ready for localization? We'll assume that you have your site already set up. We'll use the Page content type found in e.g. the Agency setup recipe as an example. First, make sure that you've set up available site cultures on the Orchard dashboard. This is under Configuration, Settings, Cultures (or the /Admin/Settings/localization URL). Set up LocalizationPart for content types to be localized as mentioned in the docs. Now comes the hard part: You need content items' URLs to be generated with the culture in it, so something like "en-US/demo". This is so you can have two versions of a content item, in different languages but with the same slug ("demo"). So, edit the settings of the Autoroute part from under the content type's editor under the Content menu on the admin, Content Definition, Content Types. For the Page type it's here: /Admin/ContentTypes/Page/ContentParts/AutoroutePart/Edit. There you need to change the default Autoroute pattern to include the culture's ID. This you can do by accessing the culture set in LocalizationPart, so the whole pattern will be something like this: {{ Model.ContentItem.Content.LocalizationPart.Culture }}/{{ Model.ContentItem | display_text | slugify }}. That's pretty much it. Now when you create a new Page you'll be able to tell Orchard which culture it belongs to and the URL will automatically reflect that. This is of course not the complete localization story. You'll also need to display the culture options to the user which you can do with the ContentCulturePicker shape as explained here. Other UI labels coming from code need to be localized too with PO files, as you can read about in the docs too. Have fun with your multi-language sites! We also have a follow-up post on how to add a culture URL segment for non-content pages. Did you like this post? It's part of our Orchard Core Nuggets series where we answer common Orchard questions, be it about user-facing features or developer-level issues. Check out the other posts for more such bite-sized Orchard Core tips and let us know if you have another question!