Source
Structured content, localisation & export — found from sitemap — Umbraco
Checked for Umbraco on 3 Nov 2026
- Page
- https://docs.umbraco.com/umbraco-cms/model-your-content/content-types-and-structure/data/defining-content/document-type-localization
- Checked
- 3 Nov 2026, 14:55 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:3c1fb88ca6e8fbbf390d455254c1b5e4f259a91e34f453710c1249dd9b634986
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Document type localization supported items Report an error
“When defining a Document Type, you can apply localization to: Document Type names and descriptions. Property names and descriptions. Custom property validation messages. Tab and group names.”
-
Localization applies to media and member types Report an error
“Everything in this article also applies to defining Media Types and Member Types.”
-
Localization registration manifest Report an error
“Register the Document Type localization files via a new manifest 'umbraco-package.json' file.”
-
Localization manifest location Report an error
“The umbraco-package.json file is only registered when placed directly in the /App_Plugins/ or /App_Plugins/{SubFolderName} folder. It will not be recognized in nested subfolders.”
-
Localization restart required Report an error
“Umbraco must be restarted to register the localization manifest. Any subsequent localization text changes will need to be reloaded within the browser.”
-
Localization syntax Report an error
“The localizations are applied by using the syntax #{area alias}_{key alias}.”
-
Property descriptions markdown Report an error
“Property descriptions support Umbraco Flavored Markdown, which uses a different syntax (wrapped in brackets) to avoid conflicts with Markdown headers.”
-
Backoffice UI localization Report an error
“The Umbraco backoffice is localized to match the user's configured UI Culture.”
Scores citing this record
- The Head of Content Structured content, localisation & export
- The Data Protection Officer Structured content, localisation & export
- The Localisation Lead Structured content, localisation & export
- The Skeptic Structured content, localisation & export
- The SME Marketer Structured content, localisation & export
- The Web Engineer Structured content, localisation & export