New Crowdin translations

fr/README.md

@@ -4,7 +4,7 @@ Craft is a flexible, user-friendly CMS for creating custom digital experiences o
 
 It features:
 
-- An intuitive, user-friendly Control Panel for content creation and administrative tasks.
+- An intuitive, user-friendly control panel for content creation and administrative tasks.
 - A clean-slate approach to content modeling and [front-end development](dev/README.md) that doesn’t make any assumptions about your content or how it should be consumed.
 - A built-in Plugin Store with hundreds of free and commercial [plugins](https://plugins.craftcms.com/), all just a click away.
 - A robust framework for [module and plugin development](extend/README.md).
@@ -29,8 +29,10 @@ Craft is a self-hosted PHP 7 application, built on [Yii 2](https://www.yiiframew
 
 ## Diving In
 
+If you’re new to Craft CMS the best place to start is [the tutorial](https://docs.craftcms.com/tutorial/).
+
 To start getting acquainted with how content modeling works in Craft, read [Sections and Entries](sections-and-entries.md) and [Fields](fields.md).
 
-When you’re ready to install Craft, read [Server Requirements](requirements.md) and [Installation Instructions](installation.md).
+Before installing, check out the [Server Requirements](requirements.md) and [Installation Instructions](installation.md).
 
 Finally, read the [Front-End Development](dev/README.md) section when you’re ready to start building out the front-end of your site or application.

fr/assets-fields.md

@@ -40,6 +40,10 @@ Subfolder paths defined by the “Upload Location” and “Default Upload Locat
 
 Any properties supported by the source element (the element that has the Assets field) can be used here.
 
+::: tip
+If you want to include the entry’s ID or UID in a dynamic subfolder path, use `{sourceId}` or `{sourceUid}` rather than `{id}` or `{uid}`, so the source entry’s ID or UID is used rather than the revision / draft’s.
+:::
+
 ::: tip
 If you are creating the Assets field within a [Matrix field](matrix-fields.md), the source element is going to be the Matrix block, _not_ the element that the Matrix field is being created on.
 
@@ -52,6 +56,10 @@ Assets fields list all of the currently-related assets, with a button to select
 
 Clicking the “Add an asset” button will bring up a modal window where you can find and select additional assets, as well as upload new ones.
 
+::: tip
+You can also upload assets by dragging files directly onto the assets field or modal window.
+:::
+
 ### Inline Asset Editing
 
 When you double-click on a related asset, a HUD will appear where you can edit the asset’s title and custom fields, and launch the Image Editor (if it’s an image).
@@ -68,10 +76,15 @@ When [querying for elements](dev/element-queries/README.md) that have an Assets
 
 Possible values include:
 
-| Value | Fetches elements…
-| - | -
-| `':empty:'` | that don’t have any related assets.
-| `':notempty:'` | that have at least one related asset.
+| Value                                                       | Fetches elements…                                       |
+| ----------------------------------------------------------- | ------------------------------------------------------- |
+| `':empty:'`                                                 | that don’t have any related assets.                     |
+| `':notempty:'`                                              | that have at least one related asset.                   |
+| `100`                                                       | that are related to the asset with an ID of 100.        |
+| `[100, 200]`                                                | that are related to an asset with an ID of 100 or 200.  |
+| `['and', 100, 200]`                                         | that are related to the assets with IDs of 100 and 200. |
+| an [Asset](api:craft\elements\Asset) object               | that are related to the asset.                          |
+| an [AssetQuery](api:craft\elements\db\AssetQuery) object | that are related to any of the resulting assets.        |
 
 ```twig
 {# Fetch entries with a related asset #}
@@ -103,6 +116,10 @@ To loop through all of the related assets, call [all()](api:craft\db\Query::all(
 {% endif %}
 ```
 
+::: warning
+When using `asset.url` or `asset.getUrl()`, the asset’s source volume must have “Assets in this volume have public URLs” enabled and a “Base URL” setting. Otherwise, the result will always be empty.
+:::
+
 If you only want the first related asset, call [one()](api:craft\db\Query::one()) instead, and then make sure it returned something:
 
 ```twig
@@ -132,40 +149,71 @@ You can set [parameters](dev/element-queries/asset-queries.md#parameters) on the
 It’s always a good idea to clone the asset query using the [clone()](./dev/functions.md#clone) function before adjusting its parameters, so the parameters don’t have unexpected consequences later on in your template.
 :::
 
-### Uploading Files from Front-End Entry Forms
+### Saving Assets Fields in Entry Forms
 
-If you want to allow users to upload files to an Assets field from a front-end [entry form](dev/examples/entry-form.md), you just need to do two things.
+If you have an [entry form](dev/examples/entry-form.md) that needs to contain an Assets field, you will need to submit your field value as a list of asset IDs, in the order you want them to be related.
 
-First, make sure your `<form>` tag has an `enctype="multipart/form-data"` attribute, so that it is capable of uploading files.
+For example, you could create a list of checkboxes for each of the possible relations:
 
-```markup
-<form method="post" accept-charset="UTF-8" enctype="multipart/form-data">
+```twig
+{# Include a hidden input first so Craft knows to update the
+   existing value, if no checkboxes are checked. #}
+{{ hiddenInput('fields[<FieldHandle>]', '') }}
+
+{# Get all of the possible asset options #}
+{% set possibleAssets = craft.assets()
+  .volume('siteAssets')
+  .kind('image')
+  .orderBy('filename ASC')
+  .withTransforms([
+    { width: 100, height: 100 }
+  ])
+  .all() %}
+
+{# Get the currently related asset IDs #}
+{% set relatedAssetIds = entry is defined
+  ? entry.<FieldHandle>.ids()
+  : [] %}
+
+<ul>
+  {% for possibleAsset in possibleAssets %}
+    <li>
+      <label>
+        {{ input('checkbox', 'fields[<FieldHandle>][]', possibleAsset.id, {
+          checked: possibleAsset.id in relatedAssetIds
+        }) }}
+        {{ tag('img', {
+          src: possibleAsset.
+        }) }}
+        {{ possibleAsset.getImg({width: 100, height: 100}) }}
+        {{ possibleAsset.filename }}
+      </label>
+    </li>
+    {% endfor %}
+</ul>
 ```
 
-Then add a file input to the form:
+You could then make the checkbox list sortable, so users have control over the order of related assets.
 
-```markup
-<input type="file" name="fields[<FieldHandle>]">
-```
+#### Creating New Assets
 
-::: tip
-Replace `<FieldHandle>` with you actual field handle. For example if you field handle is “heroImage”, the input name should be `fields[heroImage]`.
-:::
+Assets fields can handle new file uploads as well:
 
-If you want to allow multiple file uploads, add the `multiple` attribute and add `[]` to the end of the input name:
-
-```markup
-<input type="file" name="fields[<FieldHanlde>][]" multiple>
+```twig
+{{ input('file', 'fields[<FieldHandle>][]', options={
+  multiple: true,
+}) }}
 ```
 
-If you want to add files to a field with existing assets, you will need to first fetch the existing asset ids and add them to a hidden field:
+::: tip
+Don’t forget to set `enctype="multipart/form-data"` on your `<form>` tag so your browser knows to submit the form as a multipart request.
+:::
 
-```
-{% for asset in entry.<FieldHanlde> %}
-    <input type="hidden" name="fields[<FieldHanlde>][]" value="{{ asset.id }}">
-{% endfor %}
+Alternatively, you can submit Base64-encoded file data, which the Assets field will decode and treat as an uploaded file. To do that, you have to specify both the data and the filename like this:
 
-<input type="file" name="fields[<FieldHanlde>][]" multiple>
+```twig
+{{ hiddenInput('fields[<FieldHandle>][data][]', 'data:image/jpeg;base64,<BASE64DATA>') }}
+{{ hiddenInput('fields[<FieldHandle>][filename][]', 'myFile.ext') }}
 ```
 
 ## See Also

fr/assets.md

@@ -44,7 +44,7 @@ Any fields you select here will be visible in the asset editor HUD that opens up
 
 ## Assets Page
 
-When you create your first volume, an “Assets” item will be added to the main Control Panel navigation. Clicking on it will take you to the Assets page, which shows a list of all of your volumes in the left sidebar, and the selected volume’s files in the main content area.
+When you create your first volume, an “Assets” item will be added to the main control panel navigation. Clicking on it will take you to the Assets page, which shows a list of all of your volumes in the left sidebar, and the selected volume’s files in the main content area.
 
 From this page, you can do the following:
 

fr/categories-fields.md

@@ -59,10 +59,15 @@ You can set [parameters](dev/element-queries/category-queries.md#parameters) on
 
 Possible values include:
 
-| Value          | Fetches elements…                        |
-| -------------- | ---------------------------------------- |
-| `':empty:'`    | that don’t have any related categories.  |
-| `':notempty:'` | that have at least one related category. |
+| Value                                                             | Fetches elements…                                           |
+| ----------------------------------------------------------------- | ----------------------------------------------------------- |
+| `':empty:'`                                                       | that don’t have any related categories.                     |
+| `':notempty:'`                                                    | that have at least one related category.                    |
+| `100`                                                             | that are related to the category with an ID of 100.         |
+| `[100, 200]`                                                      | that are related to a category with an ID of 100 or 200.    |
+| `['and', 100, 200]`                                               | that are related to the categories with IDs of 100 and 200. |
+| an [Category](api:craft\elements\Category) object               | that are related to the category.                           |
+| an [CategoryQuery](api:craft\elements\db\CategoryQuery) object | that are related to any of the resulting categories.        |
 
 ```twig
 {% set relatedCategories = entry.<FieldHandle>.all() %}
@@ -111,8 +116,20 @@ To loop through all of the related categories as a flat list, call [all()](api:c
 Or you can show them as a hierarchical list with the [nav](dev/tags/nav.md) tag:
 
 ```twig
-{% if entry.<FieldHandle>.exists() %}
-    <p>There are related categories!</p>
+{% set relatedCategories = entry.<FieldHandle>.all() %}
+{% if relatedCategories|length %}
+    <ul>
+        {% nav rel in relatedCategories %}
+            <li>
+                <a href="{{ rel.url }}">{{ rel.title }}</a>
+                {% ifchildren %}
+                    <ul>
+                        {% children %}
+                    </ul>
+                {% endifchildren %}
+            </li>
+        {% endnav %}
+    </ul>
 {% endif %}
 ```
 

fr/categories.md

@@ -25,7 +25,7 @@ You can also add additional fields using all of the available field types in Cra
 
 ## Creating and Editing Categories
 
-If you have at least one category group, there will be a “Categories” tab in the primary Control Panel navigation. Clicking on it will take you to the category index. From there you can choose a category group from the sidebar, and add/reorder/delete categories within it:
+If you have at least one category group, there will be a “Categories” tab in the primary control panel navigation. Clicking on it will take you to the category index. From there you can choose a category group from the sidebar, and add/reorder/delete categories within it:
 
 ![Category Index](./images/categories-category-index.png)
 

fr/changes-in-craft-3.md

@@ -35,6 +35,10 @@ The “Position Select” field type has been removed from Craft 3. If you had a
 
 If you miss Position Select, you can try installing the [Position Fieldtype](https://github.com/Rias500/craft-position-fieldtype) plugin, which brings it back.
 
+## Lightswitch Fields
+
+Lightswitch field values are now always `true` or `false`. If you’re accessing a Lightswitch field value for an element that doesn’t have an explicit value set yet, the field’s default value will be returned instead.
+
 ## Remote Volumes
 
 Support for Amazon S3, Rackspace Cloud Files, and Google Cloud Storage have been moved into plugins. If you have any asset volumes that were using those services in Craft 2, you will need to install the new plugins:
@@ -132,7 +136,7 @@ The acceptable translation categories are:
 
 In Craft 3, your `translations/` folder might look something like this:
 
-```
+```treeview
 translations/
 └── de/
     ├── app.php
@@ -449,14 +453,14 @@ That made it possible to execute variations of an element query, without affecti
 {% set totalEntries = query.total() %}
 ```
 
-Here `.type()` is applying the `type` parameter to a *clone* of `query`, so it had no effect on `query.total()`, which will still return the total number of News entries, regardless of their entry types.
+Here `.type()` is applying the `type` parameter to a _clone_ of `query`, so it had no effect on `query.total()`, which will still return the total number of News entries, regardless of their entry types.
 
 This behavior has changed in Craft 3, though. Now any time you call a parameter-setter method, the method will:
 
 1. set the parameter value on the current element query
 2. return the element query
 
-Which means in the above code example, `totalEntries` will be set to the total *Article* entries, as the `type` parameter will still be applied.
+Which means in the above code example, `totalEntries` will be set to the total _Article_ entries, as the `type` parameter will still be applied.
 
 If you have any templates that count on the Craft 2 behavior, you can fix them using the [clone()](dev/functions.md#clone-object) function.
 
@@ -571,7 +575,7 @@ Your front-end `<form>`s and JS scripts that submit to a controller action will
 
 ### `action` Params
 
-`action` params must be rewritten in in `kebab-case` rather than `camelCase`.
+`action` params must be rewritten in `kebab-case` rather than `camelCase`.
 
 ```twig
 Old:

fr/checkboxes-fields.md

@@ -16,12 +16,12 @@ When [querying for elements](dev/element-queries/README.md) that have a Checkbox
 
 Possible values include:
 
-| Value | Fetches elements…
-| - | -
-| `'foo'` | with a `foo` option checked.
-| `'not foo'` | without a `foo` option checked.
-| `['foo', 'bar']` | with `foo` or `bar` options selected.
-| `['and', 'foo', 'bar']` | with `foo` and `bar` options selected.
+| Value                   | Fetches elements…                      |
+| ----------------------- | -------------------------------------- |
+| `'foo'`                 | with a `foo` option checked.           |
+| `'not foo'`             | without a `foo` option checked.        |
+| `['foo', 'bar']`        | with `foo` or `bar` options selected.  |
+| `['and', 'foo', 'bar']` | with `foo` and `bar` options selected. |
 
 ```twig
 {# Fetch entries with the 'foo' option checked #}

fr/coc.md

@@ -6,7 +6,7 @@ Diversity is one of our strengths. With that, challenges will arise that can lea
 
 This isn’t an exhaustive list of things that you can’t do. Rather, take it in the spirit in which it’s intended - a guide to make it easier to enrich all of us and the technical communities in which we participate.
 
-This code of conduct applies to all spaces used by the Craft community for communication. This includes Craft Slack, Craft CMS Stack Exchange, GitHub, Twitter, Facebook, meetups, conferences, and any other relevant forums. Violations of this code outside of any spaces managed by the Craft team will still affect a person’s ability to participate within them.
+This code of conduct applies to all spaces used by the Craft community for communication. This includes Craft Discord, Craft CMS Stack Exchange, GitHub, Twitter, Facebook, meetups, conferences, and any other relevant forums. Violations of this code outside of any spaces managed by the Craft team will still affect a person’s ability to participate within them.
 
 If you believe someone is violating the code of conduct, we ask that you report it by contacting us from [craftcms.com/contact](https://craftcms.com/contact). We take all reports seriously, and your identity will remain confidential.