Editor share previews and publishing workflows (#2380)

* document sharing previews and publishing workflows

* add note on changes

* fix list numbering

* use table

* make table nicer

Author: ethanpalm

editor.mdx

@@ -42,7 +42,7 @@ Here is how you'll typically work in the web editor:
     Visual mode shows you how your changes will appear on your live site. Use this to verify everything looks correct.
   </Step>
   <Step title="Publish your changes">
-    If you're working on your deployment branch, publish your changes directly from the web editor. On other branches, you'll create a pull request for review before publishing.
+    Publish your changes directly to your live documentation site or create a pull request to review changes before merging.
   </Step>
 </Steps>
 
@@ -248,10 +248,18 @@ See [Format text](/create/text) and [Format code](/create/code) for more informa
 
 ## Publish your changes
 
-The branch that you work on determines how the editor publishes your changes:
+The editor's publishing workflow depends on which branch you work on and your repository's branch protection rules.
 
-- **Deployment branch**: Publishing updates your live site immediately.
-- **Other branches**: Publishing creates a pull request so you can review changes before deploying them to production.
+| Branch type | Branch protection | What happens when you publish |
+| :---------- | :----------------- | :------------------------------ |
+| Deployment branch | None | Changes merge and are live immediately |
+| Deployment branch | Pull requests required | Creates a pull request for review |
+| Other branch | None | Changes merge into deployment branch and are live immediately |
+| Other branch | Pull requests required | Creates a pull request for review |
+
+<Tip>
+  Configure branch protection rules in your Git provider to require pull request reviews before merging. See [About protected branches](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches) in the GitHub docs or [Protected branches](https://docs.gitlab.com/user/project/repository/branches/protected/) in the GitLab docs for more information.
+</Tip>
 
 <Frame>
   <img
@@ -324,6 +332,22 @@ Once your pull request is created:
 4. **Approve**: Approve the pull request when you're satisfied with the changes.
 5. **Merge**: Merge the pull request when you're ready to deploy your changes to production.
 
+### Share preview deployments
+
+Share preview deployments with your team to gather feedback before you publish changes.
+
+1. Click the **Share** button in the editor toolbar.
+1. Click the **Preview** button to open the preview deployment in a new browser tab.
+    <Frame>
+      <img src="/images/editor/share-preview-light.png" alt="Share preview panel opened in the editor toolbar." className="block dark:hidden" />
+      <img src="/images/editor/share-preview-dark.png" alt="Share preview panel opened in the editor toolbar." className="hidden dark:block" />
+    </Frame>
+1. Share the preview URL with anyone who needs to review your changes.
+
+When you make changes, the preview deployment updates automatically. Changes may take a short time to appear.
+
+Preview URLs are publicly accessible by default. Anyone with the link can view your preview deployment. To restrict access to authenticated members of your organization, enable preview authentication in your [dashboard](https://dashboard.mintlify.com/products/addons).
+
 ## Keyboard shortcuts
 
 The web editor supports all common keyboard shortcuts such as copy, paste, undo, and select all, and the following shortcuts: