mirror of
https://github.com/mintlify/docs.git
synced 2026-09-14 13:35:46 +08:00
Ethan Palm
9a4ec7b557
* Fix editor docs accuracy, split media page, clear translation orphans
Accuracy fixes, each verified against mintlify/mint or mintlify/server:
- pages.mdx: "Editors and managers can restore them" -> "admins".
"Manager" is not a Mintlify role.
- index.mdx: publishing on a feature branch does not automatically open a
pull request; you choose commit-to-branch or PR. Contradicted the
branching page's own table.
- branching-and-publishing.mdx: preview deployments build when you open a
pull request, not on every branch save. Confirmed in gitlabWebhooks
(handleMergeRequestOpenEvent) and cruxWebhooks (keyed on reviewId).
tutorial.mdx was already correct.
- settings.mdx: rewritten against editor-settings-form.tsx. The panel has
four sections, not "two layers", and the entire Appearance section was
undocumented - including "Open live preview in new tab", which
live-preview.mdx already linked readers to. Corrected three setting
labels, noted that draft PRs default to on, added the 20,000-character
instruction limit.
- live-preview.mdx: link now resolves to /editor/settings#appearance.
De-bloat:
- Split the media section out of pages.mdx (172 lines, 15 subtopics) into
editor/media.mdx and added it to the nav.
- Trimmed index.mdx from 11 sidebar-duplicating cards to 4.
Translation orphans and redirects:
- Deleted 7 translated files whose English source was removed in April and
June. The translate automation never cleaned them up, and in PR #6062 it
wrote into es|fr|zh/editor/media.mdx 34 days after the English source was
deleted.
- Dropped /editor/media -> /editor/pages so it stops shadowing the
recreated page.
- Added /{es,fr,zh}/editor/publish, completing an English-only redirect.
- Added /editor/collaborate and its language variants. That page was
deleted in June with no redirect and has been a live 404 since.
mint broken-links clean, mint a11y clean, vale 0/0/0 on changed files.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Restructure editor docs: 14 pages to 9, cut UI description
The editor section had grown to 14 pages, about 40% of which described
things a user can see on screen. The ratio was 105 field-enumeration
bullets to 42 procedural steps.
New structure, organized around what is invisible rather than what is
on screen:
Overview absorbs git-essentials (concepts + the Git mapping table)
Tutorial unchanged
Edit content absorbs media and navigation
Publish branch mechanics, conflicts, git sync, commit signing
Review previews, pull requests, approve and merge
Collaborate comments + suggestions + real-time editing
Editor agent trimmed
Settings absorbs configurations as a pointer
Keyboard shortcuts unchanged
Removed: git-essentials, media, navigation, live-preview, comments,
suggestions, configurations, branching-and-publishing. Added: publish,
review, collaborate.
configurations.mdx was the clearest cut. It was a 193-line field-by-field
mirror of the Site configurations panel, which is a third rendering of
information already in the docs.json schema and in organize/settings-*
(2,694 lines). It is now a short section in settings.mdx covering only
what is specific to editing configuration from the editor: real-time
sync, the SVG logo constraint, and the redirects interface.
Also cut: block actions, the minimap, code block options, right-click
menu enumerations, page settings field lists (already delegated to
/organize/pages), and most screenshots of self-evident controls.
1,320 to 848 body lines. Field-enumeration bullets 105 to 29.
English redirects added for all eight removed pages. Language variants
deliberately omitted: es/fr/zh still carry the old structure, so
redirecting those paths now would shadow pages that still exist there.
The translation automation should mirror this restructure; verify
afterward that no orphans remain.
Vale vocabulary widened rather than reworded around: autocommit(s|ed|ing)?,
autosav(e|es|ed|ing), dotfile(s)?.
mint broken-links clean, mint a11y clean, vale 0 errors on editor/.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Correct keyboard shortcuts against the editor keymap
Verified every documented shortcut against the bindings in mintlify/mint
rather than inferring them. The app-level set is exhaustive:
mod+backslash, mod+i, mod+k, mod+s, mod+shift+period, mod+z, shift+mod+d,
shift+mod+s. Visual-mode bindings come from the Tiptap extensions.
- Cmd/Ctrl+Shift+F ("Switch between Navigation and Files tree") does not
exist. No such binding is registered anywhere in the dashboard. Replaced
with the real binding at that spot in the UI: Cmd/Ctrl+Shift+. toggles
"Show all files".
- Added Heading 5 and Heading 6. Heading.configure sets levels 1-6 and
preserves the parent Mod-Alt-N shortcuts; the table stopped at 4.
- Added Cmd/Ctrl+G for accordion group, bound in Accordions.tsx.
Confirmed correct and unchanged: Cmd+K search, Cmd+I agent, Cmd+Shift+S
mode toggle, Cmd+Shift+D diff, Cmd+\ sidebar, Cmd+Shift+M comment,
Cmd+Shift+E suggesting mode, Cmd+Shift+X strikethrough, Cmd+K link,
Cmd+Enter line break, Cmd+Shift+8 unordered list, and that source mode
runs Monaco.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Document auto publish, drop the deprecated deploy branch lock
Auto publish is available to all deployments, so the settings panel shows
"Auto publish" rather than "Main branch autocommits". It is not just a
rename: when it is on, the editor hides the branch selector and the
Publish button entirely (TopBar returns null for both), so there is no
pending state and no review step. Documented that behavior in
settings.mdx and added a note at the top of publish.mdx, since that page
otherwise assumes a publish step exists.
The deployment branch lock was deprecated and removed, so it stays out of
the docs. It was already dropped from settings.mdx in the restructure.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* 💅
* copy edit index
* Fix editor docs I verified against dead code
Three claims traced to code that never mounts. Ethan confirmed the diff
shortcut does not work, which exposed the pattern.
- Removed Cmd/Ctrl+Shift+D for diff view. It is registered only at
SubBar/index.tsx:488, inside EditorSubBar, which is exported and
imported by nothing. There is no live diff shortcut; exitDiff exists
only as an onClick in EditorModeContextMenu.
- Source mode runs CodeMirror, not Monaco. SourceEditor resolves through
source-editor/index.tsx to editor-view.tsx, which imports
@codemirror/state and @codemirror/view. Monaco is used only by
EmbedModal. The shortcut rows themselves were correct: CodeMirror's
defaultKeymap and searchKeymap match VS Code for toggle comment, move
line, duplicate line, find, and add cursor above/below, all confirmed
against @codemirror/commands.
- Rewrote the left panel section of pages.mdx. The tabs are Home and
Publishing (EditorNavigationSidebarContents.tsx:62), not Navigation and
Files. The Navigation/Files switcher lives in the same dead SubBar
component. Home renders the workspace file tree including private
pages; Publishing renders the site navigation and site settings.
Confirmed by the e2e helper openPublishingNavigation, which queries the
Publishing tab by role against the running app.
Also corrected in that section: the tree hides docs.json, dotfiles,
extensionless files, all-caps Markdown, and css/js/jsx/mjs/cjs/pdf unless
Show all files is on; "unlisted" was an invented term, replaced with a
link to /organize/hidden-pages; and the folder menu item is "New page",
confirmed by e2e, not "New file".
Added four source-mode bindings that are real and undocumented: Cmd+B and
Cmd+I insert Markdown markers, Cmd+Option+Shift+[ and ] fold and unfold
all.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* copy edit pages
* copy edit publish
* copy edit review
* copy edit settings
* copy edit collaborate
* Updated mintlify pages
- Updated quickstart.mdx
Mintlify-Source: dashboard-editor
* copy edit keyboard shortcuts
* Updated mintlify pages
- Updated quickstart.mdx
Mintlify-Source: dashboard-editor
* Revert "Updated mintlify pages"
This reverts commit 8d1b50cbfc.
* Updated mintlify pages
- Updated quickstart.mdx
Mintlify-Source: dashboard-editor
* fix editor edits
* Mirror the editor restructure into es, fr, and zh
Brings all three translated sites onto the same nine-page structure as
English instead of waiting for the translate automation, which has a
documented history of leaving orphans behind.
Content:
- Deleted 21 orphans: branching-and-publishing, comments, configurations,
git-essentials, live-preview, navigation, and suggestions in each
language. None had an English source after the restructure.
- Added publish, review, and collaborate in each language.
- Rewrote index, pages, settings, agent, and keyboard-shortcuts to match
the current English content, including Home/Publishing tabs, CodeMirror
source mode, Show all files, and the restored Appearance section.
- Kept the existing conventions: es uses usted, fr uses vous, keywords and
product UI labels stay in English, and every heading is wrapped in a
<div id="english-slug"> so cross-language anchors resolve. Verified that
every English anchor exists in all three languages.
Navigation and redirects:
- es.json, fr.json, and zh.json now list the same nine pages as docs.json.
- Removed six locale redirects that would have shadowed the new publish
and collaborate pages once they existed.
- Added 21 locale redirects for the removed pages and retargeted the
destinations that pointed at them.
- Retargeted four /editor/configurations redirects that pointed at
#site-configurations, an anchor dropped in the settings rewrite.
- Rewrote stale links in changelog, authentication-setup, concepts, and
glossary across all three languages, since broken-links does not follow
redirects.
English fixes needed first, all caused by the settings restructure:
- Restored ## Appearance. Two pages link to #appearance, and its four
preferences were otherwise undocumented.
- Restored ## Create draft pull requests by default, which changelog
links to and which defaults to on.
- Promoted Main branch autocommits from ### to ##; it was nested under PR
instructions, and its warning named a setting no longer on the page.
- Retargeted publish.mdx from the removed #auto-publish anchor.
- Fixed a missing space in the settings page intro.
mint broken-links clean, mint a11y clean (1042 files), vale 0 errors,
all five JSON files valid.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
97 lines
5.2 KiB
Plaintext
97 lines
5.2 KiB
Plaintext
---
|
|
title: "Publier des modifications"
|
|
sidebarTitle: "Publier"
|
|
description: "Publiez des modifications depuis l'éditeur vers votre site publié. Les branches et les règles de protection déterminent ce qui se passe lorsque vous publiez."
|
|
keywords: ["publish", "branch", "git", "commit", "conflicts", "deploy", "pull request"]
|
|
---
|
|
|
|
Vos modifications sont enregistrées automatiquement pendant que vous travaillez, mais elles n'atteignent votre site publié que lorsque vous les publiez. Ce qui se passe alors dépend de la branch sur laquelle vous travaillez et du fait que cette branch exige ou non des pull requests.
|
|
|
|
<Note>
|
|
Si vous ne voyez ni sélecteur de branch ni bouton **Publish**, la [publication automatique](#auto-publish) est activée sur votre deployment et vos modifications sont mises en ligne automatiquement.
|
|
</Note>
|
|
|
|
<div id="pending-changes">
|
|
|
|
## Modifications en attente
|
|
|
|
</div>
|
|
|
|
L'éditeur considère les éléments suivants comme des modifications en attente :
|
|
|
|
- Les modifications de contenu dans les pages
|
|
- Les pages ajoutées ou supprimées
|
|
- Les changements de structure de navigation
|
|
- Les médias téléversés
|
|
- Les mises à jour de configuration
|
|
|
|
S'il n'y a aucune modification en attente, l'éditeur désactive les actions de publication et d'enregistrement.
|
|
|
|
<div id="what-happens-when-you-publish">
|
|
|
|
## Ce qui se passe lorsque vous publiez
|
|
|
|
</div>
|
|
|
|
| Type de branch | Protection de branch | Actions disponibles |
|
|
| --- | --- | --- |
|
|
| <Tooltip tip="La branch qui publie vers votre site, généralement 'main'." headline="Deployment branch">Deployment branch</Tooltip> | Aucune | **Publish** directement vers votre site publié |
|
|
| Deployment branch | Pull requests requises | **Create branch** pour déplacer les modifications vers une nouvelle branch |
|
|
| <Tooltip tip="Une branch isolée sur laquelle vous travaillez avant de fusionner dans votre deployment branch." headline="Feature branch">Feature branch</Tooltip> | Aucune | **Save in branch**, **Create pull request** |
|
|
| Feature branch | Pull requests requises | **Save in branch**, **Create pull request** |
|
|
|
|
- **Publish** : Commit et déploie vos modifications vers votre site publié immédiatement.
|
|
- **Save in branch** : Commit vos modifications sur la feature branch sans fusionner dans votre deployment branch.
|
|
- **Create branch** : Déplace vos modifications en attente vers une nouvelle feature branch lorsque vous êtes sur une deployment branch protégée.
|
|
- **Create pull request** : Ouvre une pull request vers votre deployment branch.
|
|
|
|
Une seule publication peut avoir lieu à la fois par branch. Si un collègue publie sur la même branch, attendez la fin de sa publication avant de réessayer.
|
|
|
|
<Note>
|
|
Votre site est mis à jour une fois que Mintlify a compilé et déployé vos modifications. Cela prend généralement de 30 secondes à quelques minutes. Consultez l'état du déploiement sur votre [dashboard](https://app.mintlify.com).
|
|
</Note>
|
|
|
|
<div id="when-to-use-a-branch">
|
|
|
|
## Quand utiliser une branch
|
|
|
|
</div>
|
|
|
|
Travaillez directement sur votre deployment branch si vous n'utilisez pas de workflow basé sur Git. Créez une branch si chaque modification passe par une révision avant d'atteindre votre site publié.
|
|
|
|
Pour créer une branch, cliquez sur le nom de la branch dans la barre d'outils de l'éditeur, sélectionnez **Create new branch**, saisissez un nom, puis cliquez sur **Create branch**.
|
|
|
|
<Note>
|
|
Créer une branch ou en changer alors que vous avez des modifications non publiées vous invite à les emporter avec vous ou à les laisser. Les modifications que vous laissez restent sur la branch d'origine.
|
|
</Note>
|
|
|
|
<div id="resolve-conflicts">
|
|
|
|
## Résoudre les conflits
|
|
|
|
</div>
|
|
|
|
Les conflits surviennent lorsque votre branch et la deployment branch comportent des modifications incompatibles sur les mêmes fichiers. Par exemple, lorsque vous et un collègue modifiez les mêmes lignes ou déplacez un fichier vers des emplacements différents.
|
|
|
|
Lorsque quelqu'un pousse des modifications vers votre dépôt en dehors de l'éditeur, l'éditeur applique automatiquement celles qui ne se chevauchent pas. Si une modification distante et la vôtre portent sur la même partie d'une page, l'éditeur met le conflit en évidence.
|
|
|
|
L'éditeur affiche un avertissement lorsque des conflits empêchent la publication. Suivez les instructions pour choisir la version à conserver pour chaque section en conflit.
|
|
|
|
<div id="commit-signing">
|
|
|
|
## Signature des commits
|
|
|
|
</div>
|
|
|
|
Signez vos commits avec votre compte GitHub en l'autorisant dans les [paramètres de votre compte](https://app.mintlify.com/settings/account). Sans cette autorisation, la GitHub App de Mintlify signe les commits effectués dans l'éditeur.
|
|
|
|
<div id="auto-publish">
|
|
|
|
## Publication automatique
|
|
|
|
</div>
|
|
|
|
Si la [publication automatique](/fr/editor/settings#main-branch-autocommits) est activée sur votre deployment, l'éditeur commit sur votre deployment branch peu après que vous arrêtez d'écrire. Le sélecteur de branch et le bouton **Publish** sont masqués. Il n'y a ni état en attente ni étape de révision.
|
|
|
|
Les modifications sur les feature branches créées depuis l'éditeur sont commitées automatiquement dans les deux cas, mais elles ne sont jamais publiées tant que vous ne les fusionnez pas dans votre deployment branch.
|