Found 256 results for "features translation"
The search executed in 0.001780179 seconds. That's fast.
Gitana / 3.2 / Guide / Guide / FeaturesFeatures Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu
Score: 17.125124
|
|||||||||||||||||||||||||||||||||||||||||||||||||
Gitana / 4.0 / Data Engine / Aspects / Auto TranslateAuto Translate QName: f:auto-translate This feature makes it so that any content that is saved is automatically translated into any desired target locales and stored as translations within the Cloud CMS I18N (Internationalization) framework. With this feature, your editorial users could, for example, make a change to a node and save it. The change could then be translated into Chinese, Spanish and German so that content can be retrieved from Cloud CMS in those locales. This all happens automatic
Score: 15.367106
|
|||||||||||||||||||||||||||||||||||||||||||||||||
Gitana / 4.0 / Data Engine / Aspects / OverviewFeatures Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu
Score: 11.112315
|
|||||||||||||||||||||||||||||||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / Features / Translation
Translation QName: f:translation Indicates this node contains the translated content of a "master node". The master node is the original node. This feature is applied to the node which contains the translation. Note: This node will be pointed to from the master node via an a:has_translation association. The a:has_translation association contains the locale and edition as properties. Configuration
Translation QName: f:translation Indicates this node contains the translated content of a "master node". The master node is the original node. This feature is applied to the node which contains the translation. Note: This node will be pointed to from the master node via an a:has_translation association. The a:has_translation association contains the locale and edition as properties. Configuration
Content Modeling A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other neste
Content Modeling A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other neste
Default Paths Your content types define schemas that Cloud CMS uses to render intuitive forms for content entry. In addition, content types let you configure persistence paths so that JSON documents created using these forms are automatically saved in a directory structure that you intend. Paths support templated variables so that the path can be dynamic. It can depend on the values having been entered. For example, let's suppose I have the content type for an article, like this: {
"title":
Customize Translations UI Cloud CMS allows you to customize UI simply with configurations in your module. Here we will use the following example to demonstrate this feature. For multilingual documents with translations, if you go to the multilingual document's Edit Properties page, the default UI looks like this: In the above screenshot, the Edit Translations button allows you to select a translation of the multilingual document from the dropdown. It's a way to quickly edit the translated docume
Customize Translations UI Cloud CMS allows you to customize UI simply with configurations in your module. Here we will use the following example to demonstrate this feature. For multilingual documents with translations, if you go to the multilingual document's Edit Properties page, the default UI looks like this: In the above screenshot, the Edit Translations button allows you to select a translation of the multilingual document from the dropdown. It's a way to quickly edit the translated docume
Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Auto Translate QName: f:auto-translate This feature makes it so that any content that is saved is automatically translated into any desired target locales and stored as translations within the Cloud CMS I18N (Internationalization) framework. With this feature, your editorial users could, for example, make a change to a node and save it. The change could then be translated into Chinese, Spanish and German so that content can be retrieved from Cloud CMS in those locales. This all happens automatic
Watson Translate The IBM Watson™ Language Translator translates text from one language to another. The service offers multiple IBM provided translation models that you can customize based on your unique terminology and language Cloud CMS provides a IBM Watson Translator Provider that works with IBM Watson Language Translator to automatically create and update I18N translations as changes are made to content by your editorial team. To learn more, check out Auto Translate.
Watson Translate The IBM Watson™ Language Translator translates text from one language to another. The service offers multiple IBM provided translation models that you can customize based on your unique terminology and language Cloud CMS provides a IBM Watson Translator Provider that works with IBM Watson Language Translator to automatically create and update I18N translations as changes are made to content by your editorial team. To learn more, check out Auto Translate.
content-model-features-list-item-actions [
{
"config": {
"content-model-features-list-item-actions": [
{
"key": "edit-document",
"link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/properties",
"iconClass": "fa fa-pencil"
},
{
"key": "view-json",
"link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/json",
"iconClass": "fa fa-code"
},
{
"key": "content-i
content-model-features-list-item-actions [
{
"config": {
"content-model-features-list-item-actions": [
{
"key": "edit-document",
"link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/properties",
"iconClass": "fa fa-pencil"
},
{
"key": "view-json",
"link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/json",
"iconClass": "fa fa-code"
},
{
"key": "content-i
Multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale Marking a node as f:multilingual does not automatically produce translations for you. However, once marked, the Cloud CMS user i
Multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale Marking a node as f:multilingual does not automatically produce translations for you. However, once marked, the Cloud CMS user i
Default Paths Your content types define schemas that Cloud CMS uses to render intuitive forms for content entry. In addition, content types let you configure persistence paths so that JSON documents created using these forms are automatically saved in a directory structure that you intend. Paths support templated variables so that the path can be dynamic. It can depend on the values having been entered. For example, let's suppose I have the content type for an article, like this: {
"title":
Amazon Translate Amazon Translate is a neural machine translation service that delivers fast, high-quality, and affordable language translation. Neural machine translation is a form of language translation automation that uses deep learning models to deliver more accurate and more natural sounding translation than traditional statistical and rule-based translation algorithms. Amazon Translate allows you to localize content - such as websites and applications - for international users, and to eas
Amazon Translate Amazon Translate is a neural machine translation service that delivers fast, high-quality, and affordable language translation. Neural machine translation is a form of language translation automation that uses deep learning models to deliver more accurate and more natural sounding translation than traditional statistical and rule-based translation algorithms. Amazon Translate allows you to localize content - such as websites and applications - for international users, and to eas
Google Translate Google Translation Services offer the ability to quickly translate between languages, using the best model for your content needs. You can build custom models using AutoML Translation or leverage Google’s pre-trained models using Translation API. Cloud CMS provides a Google Translation Services Provider that works with Google Translate to automatically create and update I18N translations as changes are made to content by your editorial team. To learn more, check out Auto Transla
|