Create or edit a doc and submit a PR.
Move or remove a doc and set up a redirect.
Styling and formatting conventions for Sumo Logic Docs.
Definitions of Sumo Logic terms and features you'll encounter in the docs.
Preferred spelling, capitalization, and punctuation for Sumo Logic terms.
+Copy-paste templates for starting a new doc, App Catalog doc, or Cloud-to-Cloud source doc.
Our community standards for contributors.
:::warning
- Never do a Find All > Replace All, as this can break unrelated items like image paths. Replace each URL on a one-by-one basis.
+ Never do a Find All > Replace All, as this can break unrelated items like image paths. Replace each URL one at a time.
:::
1. If applicable:
* Remove from its parent index.md hub page.
* Remove from [Product List](/docs/integrations/product-list/).
-## Step 3: Delete the doc file
+## Step 4: Delete the doc file
-Delete the actual .md doc file from the repository (in this example, it'd be `docs/integrations/web-servers/nginx-legacy.md`).
+Delete the actual .md doc file from the repository (in this example, it would be `docs/integrations/web-servers/nginx-legacy.md`).
-## Step 4: Remove doc from navigation
+## Step 5: Remove doc from navigation
Remove the doc from the navigation menu ([sidebars.ts](https://github.com/SumoLogic/sumologic-documentation/blob/main/sidebars.ts) file).
-## Step 5: Publish and test the redirect
+## Step 6: Preview your changes
+
+import Preview from '../reuse/contributing/preview.md';
+
+Create a general feature, how-to, or concept doc.
+Create an App Catalog integration doc.
+Create a Cloud-to-Cloud source doc.
+Create a Sumo Logic Partner app doc.
+
* If you do not see it, [create a new PR](https://github.com/SumoLogic/sumologic-documentation/compare).
1. Select `main` for the base branch. This is the branch all staging and production content builds from.
- 1. Select your branch for the **compare**.
- 1. Click **Create pull request**.
-1. On the Pull Request page, enter the following:
+ 1. Select your branch for the comparison.
+ 1. Click **Create pull request**.
+1. On the PR page, enter the following:
* Make sure **base** branch is `main` and **compare** branch is the one you pushed.
* Enter a title for the PR.
* If applicable, include a GitHub issue number (or, for internal Sumos, the Jira ticket number).
- * Describe what changed, new pages, updates.
+ * Describe the changes you made.
* Apply a [label](https://github.com/SumoLogic/sumologic-documentation/wiki#github-labels) that best describes your contribution.
1. (Optional). For urgent, high-priority PRs (for example, doc edits tied to a GA release happening within 24 hours):
- 1. Add the GA release date to the title. For example, `AWS Integration release (GA: Jan 1, 2023)`.
- 1. From the labels list, select the `hot🔥` label, signifying it's an extremely urgent PR.
- 1. For internal Sumos only: after completion of all GitHub checks, send your PR link to the `#doc-int` and `#open-source` Slack channels for review.
-1. Click **Create pull request**.
-1. First-time contributors will be prompted in a comment to sign our Contributor License Agreement. We allow individual contributions and contributions made on behalf of companies.
+ 1. Add the GA release date to the title. For example, `AWS Integration release (GA: Jan 1, 2026)`.
+ 1. From the labels list, select the `hot🔥` label, signifying it's an urgent PR.
+ 1. For internal Sumos only: after completion of all GitHub checks, send your PR link to the **#dochub** Slack channel for review.
+1. First-time contributors will be prompted in a PR comment to sign our Contributor License Agreement. We allow individual contributions and contributions made on behalf of companies.
diff --git a/docs/reuse/contributing/tools.md b/docs/reuse/contributing/tools.md
deleted file mode 100644
index a86cf50e542..00000000000
--- a/docs/reuse/contributing/tools.md
+++ /dev/null
@@ -1,12 +0,0 @@
-