Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions editor/branching-and-publishing.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
keywords: ["editor", "branch", "publish", "pull request", "preview", "git", "merge", "deploy"]
---

The web editor autosaves everything as you type, but your changes are only live when you choose to publish them.

Check warning on line 7 in editor/branching-and-publishing.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/branching-and-publishing.mdx#L7

Did you really mean 'autosaves'?

What happens when you publish depends on two things: **which branch you're on** and **whether that branch requires pull requests**.

Expand Down Expand Up @@ -124,7 +124,7 @@

### Approve pull requests from the editor

For GitHub repositories, reviewers can approve open pull requests in the editor. When a pull request is open, an **Approve pull request** button appears in the review panel if your account has permission to review it. Click **Approve pull request** when the changes are ready to be merged. The review status updates to **Approved** and the **Merge and publish** action becomes available.

Check warning on line 127 in editor/branching-and-publishing.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/branching-and-publishing.mdx#L127

In general, use active voice instead of passive voice ('be merged').

The approve action is not available for draft pull requests, pull requests you have already approved, or GitLab merge requests. Click **Open in GitLab** to approve a merge request in GitLab.

Expand All @@ -140,6 +140,10 @@

Only one publish can happen at a time per branch. If another team member publishes to the same branch, wait for the current publish to complete before trying again.

### Unapplied `docs.json` changes

If `docs.json` has edits that haven't been applied, the publish menu shows a **docs.json has unapplied changes** banner and disables the publish actions. Click the banner to open `docs.json`, then apply or discard the edits to unblock publishing. See [Edit docs.json directly](/editor/configurations#edit-docs-json-directly).

Check warning on line 145 in editor/branching-and-publishing.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/branching-and-publishing.mdx#L145

Use 'JSON' instead of 'json'.

Check warning on line 145 in editor/branching-and-publishing.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/branching-and-publishing.mdx#L145

In general, use active voice instead of passive voice ('been applied').

Check warning on line 145 in editor/branching-and-publishing.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/branching-and-publishing.mdx#L145

Did you really mean 'unapplied'?

### Commit messages

When you publish, you can enter a commit message before confirming. If you leave it blank, the editor generates a message based on the files changed.
Expand All @@ -152,13 +156,13 @@

## Collaborate in real time

When multiple people open the same page on the same branch, they edit together in real time. Each person's cursor and edits are visible to everyone, with avatars shown in the toolbar.

Check warning on line 159 in editor/branching-and-publishing.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/branching-and-publishing.mdx#L159

Use 'Cursor' instead of 'cursor'.

- Changes from all collaborators merge automatically. Two people editing the same section won't create conflicts.
- Undo only affects your own edits.
- If you lose your connection, edits save locally and sync when you reconnect.

When the [Mintlify agent](/agent) edits a page through the API or MCP, it appears in the editor like any other collaborator. You see the agent's avatar in the toolbar and a live cursor at its most recent edit location. The cursor clears automatically after the agent finishes.

Check warning on line 165 in editor/branching-and-publishing.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/branching-and-publishing.mdx#L165

Use 'Cursor' instead of 'cursor'.

Check warning on line 165 in editor/branching-and-publishing.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/branching-and-publishing.mdx#L165

Use 'Cursor' instead of 'cursor'.

## Git sync

Expand Down
19 changes: 19 additions & 0 deletions editor/configurations.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -139,3 +139,22 @@
- **Menu drilldown**: Enable or disable auto-navigating to the first page when a user clicks a navigation group.
- **Timestamps**: Show "Last modified on [date]" on all pages.
- **SEO indexing**: Choose whether to index hidden pages for search engines.

## Edit `docs.json` directly

For configuration options that aren't surfaced in the **Configurations** panel, open `docs.json` from the file tree and edit it as raw JSON. Manual edits and changes from the **Configurations** panel stay in sync, so you can switch between them on the same branch.

When you open `docs.json`, a toolbar appears above the editor with **Apply changes** and **Discard** actions:

Check warning on line 147 in editor/configurations.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/configurations.mdx#L147

Use 'preceding' instead of 'above'.

- **Apply changes**: Validates your JSON and writes it to the working copy of `docs.json` on the current branch. The navigation sidebar updates immediately to reflect the new structure. Press <kbd>Cmd</kbd> + <kbd>S</kbd> (macOS) or <kbd>Ctrl</kbd> + <kbd>S</kbd> (Windows) to apply.
- **Discard**: Reverts the file to the last applied version.

If your edit contains invalid JSON, the toolbar turns red and shows the line number of the syntax error. **Apply changes** stays disabled until the JSON parses successfully.

<Note>
Applying changes does not publish them. To deploy your edits to your live site, use **Publish** in the toolbar. See [Branching and publishing](/editor/branching-and-publishing).
</Note>

<Warning>
The publish menu blocks publishing while `docs.json` has unapplied edits and shows a **docs.json has unapplied changes** banner. Click the banner to open the file, then apply or discard your changes before publishing.

Check warning on line 159 in editor/configurations.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/configurations.mdx#L159

Use 'JSON' instead of 'json'.

Check warning on line 159 in editor/configurations.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/configurations.mdx#L159

Did you really mean 'unapplied'?

Check warning on line 159 in editor/configurations.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/configurations.mdx#L159

Did you really mean 'unapplied'?
</Warning>
8 changes: 8 additions & 0 deletions editor/keyboard-shortcuts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@
| **Add link** to selected text | <kbd>Cmd</kbd> + <kbd>K</kbd> | <kbd>Ctrl</kbd> + <kbd>K</kbd> |
| **Add line break** | <kbd>Cmd</kbd> + <kbd>Enter</kbd> | <kbd>Ctrl</kbd> + <kbd>Enter</kbd> |
| **Component menu** | <kbd>/</kbd> | <kbd>/</kbd> |
| **Emoji picker** | <kbd>:</kbd> + keyword | <kbd>:</kbd> + keyword |

Check warning on line 55 in editor/keyboard-shortcuts.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/keyboard-shortcuts.mdx#L55

Use 'emojis?' instead of 'Emoji'.

### Smart substitutions

Expand Down Expand Up @@ -93,6 +93,14 @@

| Command | macOS | Windows |
| :--- | :--- | :--- |
| **Add cursor** | <kbd>Option</kbd> + Click | <kbd>Alt</kbd> + Click |

Check warning on line 96 in editor/keyboard-shortcuts.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/keyboard-shortcuts.mdx#L96

Use 'Cursor' instead of 'cursor'.
| **Add cursor above** | <kbd>Cmd</kbd> + <kbd>Option</kbd> + <kbd>↑</kbd> | <kbd>Ctrl</kbd> + <kbd>Alt</kbd> + <kbd>↑</kbd> |

Check warning on line 97 in editor/keyboard-shortcuts.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/keyboard-shortcuts.mdx#L97

Use 'Cursor' instead of 'cursor'.

Check warning on line 97 in editor/keyboard-shortcuts.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/keyboard-shortcuts.mdx#L97

Use 'preceding' instead of 'above'.
| **Add cursor below** | <kbd>Cmd</kbd> + <kbd>Option</kbd> + <kbd>↓</kbd> | <kbd>Ctrl</kbd> + <kbd>Alt</kbd> + <kbd>↓</kbd> |

Check warning on line 98 in editor/keyboard-shortcuts.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/keyboard-shortcuts.mdx#L98

Use 'Cursor' instead of 'cursor'.

## `docs.json` editor

Check warning on line 100 in editor/keyboard-shortcuts.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/keyboard-shortcuts.mdx#L100

'editor' should use sentence-style capitalization.

Use these shortcuts when editing `docs.json` directly. See [Edit docs.json directly](/editor/configurations#edit-docs-json-directly).

| Command | macOS | Windows |
| :--- | :--- | :--- |
| **Apply changes** | <kbd>Cmd</kbd> + <kbd>S</kbd> | <kbd>Ctrl</kbd> + <kbd>S</kbd> |
2 changes: 1 addition & 1 deletion editor/navigation.mdx
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
---
title: "Organize navigation"
description: "Reorder pages, add groups, and manage your documentation sidebar structure using drag-and-drop in the Mintlify web editor — no docs.json edits needed."

Check warning on line 3 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L3

Don't put a space before or after a dash.

Check warning on line 3 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L3

Use 'JSON' instead of 'json'.
keywords: ["editor", "navigation", "sidebar", "structure"]
---

Use the navigation sidebar to organize your documentation. Changes you make in the editor sync to your repository when you publish—you don't need to edit `docs.json` manually.
Use the navigation sidebar to organize your documentation. Changes you make in the editor sync to your repository when you publish—you don't need to edit `docs.json` manually. If you prefer to edit the file directly, see [Edit docs.json directly](/editor/configurations#edit-docs-json-directly).

## Add navigation elements

Click **Add new** at the bottom of the navigation tree to add a new element at the root level. To add an element nested inside another, click the <Icon icon="plus" /> plus button next to that element.

After creating an element, drag and drop it to reorder or nest it. Hover over an element and click the gear icon to configure its properties.

Check warning on line 13 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L13

Use the Oxford comma in 'After creating an element, drag and'.

Right-click a **page** to open its settings or delete it.

Expand All @@ -24,15 +24,15 @@

Choose the right structure for your content:

- **Pages** — Individual documentation files. The core building block of navigation.

Check warning on line 27 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L27

Don't put a space before or after a dash.
- **Groups** — Collapsible sections that cluster related pages together. Can nest within other groups.

Check warning on line 28 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L28

Don't put a space before or after a dash.
- **Tabs** — Top-level sections with horizontal navigation at the top of your site. Use tabs when you have distinct areas like API Reference and Guides.

Check warning on line 29 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L29

Don't put a space before or after a dash.
- **Anchors** — Persistent items at the top of your sidebar. Useful for quick access to external resources or top-level sections. Can be global to appear on every page.

Check warning on line 30 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L30

Don't put a space before or after a dash.
- **Dropdowns** — Expandable menus at the top of your sidebar. A lighter alternative to tabs for multiple related sections.

Check warning on line 31 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L31

Use 'dropdowns?' instead of 'Dropdowns'.

Check warning on line 31 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L31

Don't put a space before or after a dash.
- **Menus** — Dropdown navigation items within a tab for direct links to specific pages.

Check warning on line 32 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L32

Don't put a space before or after a dash.

Check warning on line 32 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L32

Use 'dropdowns?' instead of 'Dropdown'.
- **Products** — A switcher for multiple distinct product documentation sets, each with its own navigation structure.

Check warning on line 33 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L33

Don't put a space before or after a dash.
- **Versions** — A switcher for multiple simultaneous documentation versions.

Check warning on line 34 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L34

Don't put a space before or after a dash.
- **Languages** — A switcher for documentation in multiple languages.

Check warning on line 35 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L35

Don't put a space before or after a dash.

## Configure elements

Expand All @@ -40,5 +40,5 @@

- **Title**: The label shown in the sidebar.
- **Icon**: A visual marker next to the label.
- **Tag**: A badge like "NEW" or "BETA" to highlight the item.

Check warning on line 43 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L43

Spell out 'NEW', if it's unfamiliar to the audience.

Check warning on line 43 in editor/navigation.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/navigation.mdx#L43

Spell out 'BETA', if it's unfamiliar to the audience.

22 changes: 21 additions & 1 deletion es/editor/configurations.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -123,4 +123,24 @@ Realiza el seguimiento del comportamiento de los visitantes con:
Integraciones adicionales:

* **Telemetry**: Activa o desactiva la telemetría de uso
* **Cookies**: Define pares personalizados de key y value de cookies
* **Cookies**: Define pares personalizados de key y value de cookies
<div id="edit-docs-json-directly">
## Editar `docs.json` directamente
</div>

Para las opciones de configuración que no aparecen en el panel **Configurations**, abre `docs.json` desde el árbol de archivos y edítalo como JSON sin formato. Las ediciones manuales y los cambios realizados desde el panel **Configurations** se mantienen sincronizados, por lo que puedes alternar entre ambos en la misma branch.

Cuando abres `docs.json`, aparece una barra de herramientas encima del editor con las acciones **Apply changes** y **Discard**:

- **Apply changes**: Valida tu JSON y lo escribe en la copia de trabajo de `docs.json` en la branch actual. La barra lateral de navegación se actualiza de inmediato para reflejar la nueva estructura. Presiona <kbd>Cmd</kbd> + <kbd>S</kbd> (macOS) o <kbd>Ctrl</kbd> + <kbd>S</kbd> (Windows) para aplicar.
- **Discard**: Revierte el archivo a la última versión aplicada.

Si tu edición contiene JSON no válido, la barra de herramientas se vuelve roja y muestra el número de línea del error de sintaxis. **Apply changes** permanece deshabilitado hasta que el JSON se analice correctamente.

<Note>
Aplicar los cambios no los publica. Para implementar tus ediciones en tu sitio en producción, usa **Publish** en la barra de herramientas. Consulta [Publicar](/es/editor/publish).
</Note>

<Warning>
El menú de publicación bloquea la publicación mientras `docs.json` tenga ediciones sin aplicar y muestra un banner **docs.json has unapplied changes**. Haz clic en el banner para abrir el archivo, luego aplica o descarta tus cambios antes de publicar.
</Warning>
11 changes: 10 additions & 1 deletion es/editor/keyboard-shortcuts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -117,4 +117,13 @@ El modo Markdown usa el editor Monaco, que es compatible con los atajos de tecla
| :--- | :--- | :--- |
| **Agregar cursor** | <kbd>Option</kbd> + clic | <kbd>Alt</kbd> + clic |
| **Agregar cursor encima** | <kbd>Cmd</kbd> + <kbd>Option</kbd> + <kbd>↑</kbd> | <kbd>Ctrl</kbd> + <kbd>Alt</kbd> + <kbd>↑</kbd> |
| **Agregar cursor debajo** | <kbd>Cmd</kbd> + <kbd>Option</kbd> + <kbd>↓</kbd> | <kbd>Ctrl</kbd> + <kbd>Alt</kbd> + <kbd>↓</kbd> |
| **Agregar cursor debajo** | <kbd>Cmd</kbd> + <kbd>Option</kbd> + <kbd>↓</kbd> | <kbd>Ctrl</kbd> + <kbd>Alt</kbd> + <kbd>↓</kbd> |
<div id="docs-json-editor">
## Editor de `docs.json`
</div>

Usa estos atajos al editar `docs.json` directamente. Consulta [Editar docs.json directamente](/es/editor/configurations#edit-docs-json-directly).

| Comando | macOS | Windows |
| :--- | :--- | :--- |
| **Aplicar cambios** | <kbd>Cmd</kbd> + <kbd>S</kbd> | <kbd>Ctrl</kbd> + <kbd>S</kbd> |
2 changes: 1 addition & 1 deletion es/editor/navigation.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ description: "Organiza la estructura de tu sitio de documentación con el editor
keywords: ["editor", "navegación", "barra lateral", "estructura"]
---

Usa la barra lateral de navegación para organizar tu documentación. Los cambios que realices en el árbol de navegación del editor web aparecerán en la barra lateral de navegación de tu sitio y se sincronizarán con tu archivo de configuración `docs.json`.
Usa la barra lateral de navegación para organizar tu documentación. Los cambios que realices en el árbol de navegación del editor web aparecerán en la barra lateral de navegación de tu sitio y se sincronizarán con tu archivo de configuración `docs.json`. Si prefieres editar el archivo directamente, consulta [Editar docs.json directamente](/es/editor/configurations#edit-docs-json-directly).

<div id="add-navigation-elements">
## Agregar elementos de navegación
Expand Down
6 changes: 6 additions & 0 deletions es/editor/publish.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,12 @@ Los conflictos se producen cuando intentas fusionar branches con cambios incompa
* Tú y otra persona del equipo modifican las mismas líneas de un archivo en distintas branches.
* Los archivos se mueven, renombran o eliminan en una branch, pero se modifican de otra forma en otra.

<div id="unapplied-docs-json-changes">
### Cambios sin aplicar en `docs.json`
</div>

Si `docs.json` tiene ediciones que no se han aplicado, el menú de publicación muestra un banner **docs.json has unapplied changes** y deshabilita las acciones de publicación. Haz clic en el banner para abrir `docs.json` y luego aplica o descarta las ediciones para desbloquear la publicación. Consulta [Editar docs.json directamente](/es/editor/configurations#edit-docs-json-directly).

<div id="resolve-conflicts">
### Resolver conflictos
</div>
Expand Down
23 changes: 22 additions & 1 deletion fr/editor/configurations.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -123,4 +123,25 @@ Suivez le comportement des visiteurs avec :
Intégrations supplémentaires :

* **Telemetry** : activer ou désactiver la télémétrie d&#39;utilisation
* **Cookies** : définir des paires clé/valeur de cookies personnalisées
* **Cookies** : définir des paires clé/valeur de cookies personnalisées

<div id="edit-docs-json-directly">
## Modifier `docs.json` directement
</div>

Pour les options de configuration qui n'apparaissent pas dans le panneau **Configurations**, ouvrez `docs.json` depuis l'arborescence de fichiers et modifiez-le sous forme de JSON brut. Les modifications manuelles et les changements effectués depuis le panneau **Configurations** restent synchronisés, vous pouvez donc passer de l'un à l'autre sur la même branche.

Lorsque vous ouvrez `docs.json`, une barre d'outils apparaît au-dessus de l'éditeur avec les actions **Apply changes** et **Discard** :

- **Apply changes** : Valide votre JSON et l'écrit dans la copie de travail de `docs.json` sur la branche actuelle. La barre latérale de navigation se met à jour immédiatement pour refléter la nouvelle structure. Appuyez sur <kbd>Cmd</kbd> + <kbd>S</kbd> (macOS) ou <kbd>Ctrl</kbd> + <kbd>S</kbd> (Windows) pour appliquer.
- **Discard** : Restaure le fichier à la dernière version appliquée.

Si votre modification contient un JSON invalide, la barre d'outils devient rouge et affiche le numéro de ligne de l'erreur de syntaxe. **Apply changes** reste désactivé jusqu'à ce que le JSON soit analysé correctement.

<Note>
Appliquer les modifications ne les publie pas. Pour déployer vos modifications sur votre site en production, utilisez **Publish** dans la barre d'outils. Consultez [Publier](/fr/editor/publish).
</Note>

<Warning>
Le menu de publication bloque la publication tant que `docs.json` contient des modifications non appliquées et affiche une bannière **docs.json has unapplied changes**. Cliquez sur la bannière pour ouvrir le fichier, puis appliquez ou ignorez vos modifications avant de publier.
</Warning>
11 changes: 10 additions & 1 deletion fr/editor/keyboard-shortcuts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -117,4 +117,13 @@ Le mode Markdown utilise l’éditeur Monaco, qui prend en charge les raccourcis
| :--- | :--- | :--- |
| **Ajouter un curseur** | <kbd>Option</kbd> + Clic | <kbd>Alt</kbd> + Clic |
| **Ajouter un curseur au-dessus** | <kbd>Cmd</kbd> + <kbd>Option</kbd> + <kbd>↑</kbd> | <kbd>Ctrl</kbd> + <kbd>Alt</kbd> + <kbd>↑</kbd> |
| **Ajouter un curseur en dessous** | <kbd>Cmd</kbd> + <kbd>Option</kbd> + <kbd>↓</kbd> | <kbd>Ctrl</kbd> + <kbd>Alt</kbd> + <kbd>↓</kbd> |
| **Ajouter un curseur en dessous** | <kbd>Cmd</kbd> + <kbd>Option</kbd> + <kbd>↓</kbd> | <kbd>Ctrl</kbd> + <kbd>Alt</kbd> + <kbd>↓</kbd> |
<div id="docs-json-editor">
## Éditeur `docs.json`
</div>

Utilisez ces raccourcis lors de la modification directe de `docs.json`. Consultez [Modifier docs.json directement](/fr/editor/configurations#edit-docs-json-directly).

| Commande | macOS | Windows |
| :--- | :--- | :--- |
| **Appliquer les modifications** | <kbd>Cmd</kbd> + <kbd>S</kbd> | <kbd>Ctrl</kbd> + <kbd>S</kbd> |
2 changes: 1 addition & 1 deletion fr/editor/navigation.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ description: "Organisez la structure de votre site de documentation avec l’éd
keywords: ["editor", "navigation", "sidebar", "structure"]
---

Utilisez la barre latérale de navigation pour organiser votre documentation. Les modifications que vous effectuez dans l’arborescence de navigation de l’éditeur web apparaissent dans la barre latérale de navigation de votre site et sont synchronisées avec votre fichier de configuration `docs.json`.
Utilisez la barre latérale de navigation pour organiser votre documentation. Les modifications que vous effectuez dans l’arborescence de navigation de l’éditeur web apparaissent dans la barre latérale de navigation de votre site et sont synchronisées avec votre fichier de configuration `docs.json`. Si vous préférez modifier le fichier directement, consultez [Modifier docs.json directement](/fr/editor/configurations#edit-docs-json-directly).

<div id="add-navigation-elements">
## Ajouter des éléments de navigation
Expand Down
6 changes: 6 additions & 0 deletions fr/editor/publish.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,12 @@ Les conflits surviennent lorsque vous essayez de fusionner des branches contenan
* Vous et un autre membre de l&#39;équipe modifiez les mêmes lignes dans un fichier sur des branches différentes.
* Vous déplacez, renommez ou supprimez des fichiers dans une branche, mais les modifiez différemment dans une autre.

<div id="unapplied-docs-json-changes">
### Modifications non appliquées de `docs.json`
</div>

Si `docs.json` contient des modifications qui n'ont pas été appliquées, le menu de publication affiche une bannière **docs.json has unapplied changes** et désactive les actions de publication. Cliquez sur la bannière pour ouvrir `docs.json`, puis appliquez ou ignorez les modifications pour débloquer la publication. Consultez [Modifier docs.json directement](/fr/editor/configurations#edit-docs-json-directly).

<div id="resolve-conflicts">
### Résoudre les conflits
</div>
Expand Down
Loading