[[language-content-config]]

=== Configuring Content Translation

[role="summary"]
How to configure content items to make them translatable.

(((Content,translation)))
(((Configuring,content translation)))

==== Goal

Make _Custom block_, _Custom menu link_, and _Content_ entity types
translatable. Select specific subtypes and set which fields of these can be
translated.

==== Prerequisite knowledge

* <<planning-data-types>>
* <<language-concept>>

==== Site prerequisites

The core Content Translation module must be installed, and your site must
have at least two languages. See <<language-add>>.

==== Steps

. In the _Manage_ administrative menu, navigate to _Configuration_ > _Regional
and Language_ > _Content Language and Translation_
(_admin/config/regional/content-language_).

. Under _Custom language settings_, check _Content_,
_Custom block_ and _Custom menu link_ to make these entity types translatable.
+
--
// Top section of Content language settings page
// (admin/config/regional/content-language).
image:images/language-content-config_custom.png["Custom language settings checklist",width="193px"]
--

. Configuration options appear for _Content_, _Custom block_ and  _Custom menu
link_. Choose the subtypes you want to translate for each entity
type. Check _Basic page_ for _Content_, _Basic block_ for _Custom block_ and
_Custom menu link_ for _Custom menu link_.

. Verify the settings for the entity types as shown below:
+
[width="100%",frame="topbot",options="header"]
|================================
|Field name | Explanation | Example value
| Default language | The default language for the entity subtype | Site's default language (English)
| Show language selector on create and edit pages | Whether or not the language selector should be shown while editing and creating content | Checked
|================================
+
--
// Main settings area for Custom Block translations.
image:images/language-content-config_content.png["Default language and translatability for content types"]
--

. Choose the fields that should be translatable for _Basic page_ as shown in the
table below. If a field is not translation-dependent, leave it
unchecked. Enabling translation for fields that are numbers or dates has use for
accountability or implementing workflows.
+
[width="100%",frame="topbot",options="header"]
|================================
|Field name | Explanation | Example value
| Title	| The title of the content | Checked
| Authored by | The author | Unchecked
| Publishing status | Whether the content has been published or not | Checked
| Authored on | Date of publishing | Unchecked
| Changed | Date of last update | Unchecked
| Promoted to front page | Whether the content will be included in some content views | Unchecked
| Sticky at top of lists | Whether the content will be displayed first in some content views | Unchecked
| URL alias | Nicer URL for the content | Checked
| Body | The main content of the page | Checked
|================================
+
--
// Field settings area for Basic page translations.
image:images/language-content-config_basic_page.png["Translatable content entity subtypes' fields checklist"]
--

. Similarly, check the appropriate boxes for translatable fields belonging to
_Basic block_ and _Custom menu link_.

. Click _Save configuration_.

==== Expand your understanding

* <<language-config-translate>>
* <<language-content-translate>>

//==== Related concepts

==== Additional resources

* http://hojtsy.hu/blog/2013-jun-21/drupal-8-multilingual-tidbits-5-almost-limitless-language-assignment[Blog post "Multilingual Drupal 8 tidbits, part 5"]

* http://hojtsy.hu/blog/2015-jan-27/drupal-8-multilingual-tidbits-17-content-translation-basics[Blog post "Multilingual Drupal 8 tidbits, part 17"]


*Attributions*

Written and edited by https://www.drupal.org/u/lolk[Laura Vass] at
https://pronovix.com/[Pronovix],
https://www.drupal.org/u/jojyja[Jojy Alphonso] at
http://redcrackle.com[Red Crackle],
and https://www.drupal.org/u/jhodgdon[Jennifer Hodgdon].
