diff --git a/AGENTS.md b/AGENTS.md index 5fa7aa5b2a1..95ad0c7137e 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -6,6 +6,8 @@ This file is the canonical source of context and guardrails for AI coding agents Open-source Sumo Logic documentation site built with Docusaurus 3. Docs live in /docs, written in Markdown. Contributions follow the Sumo Logic style guide. +This repo takes contributions from both Sumo Logic employees and external community contributors (see [docs/contributing](https://www.sumologic.com/help/docs/contributing) for the fork-and-PR workflow external contributors follow). Most of this file — the skills, directory conventions, frontmatter rules, and slash commands below — works the same for anyone with the repo cloned and Claude Code installed. The exception is anything under **Jira Rules** and the Jira-specific steps in **Pull Requests**: those require internal Sumo Logic Atlassian access, so external contributors should skip them and follow the plain PR steps in docs/contributing instead. + ## Repository @https://github.com/SumoLogic/sumologic-documentation @@ -83,8 +85,8 @@ Before pushing any commit that changes docs content: 2. Tell the user to confirm the changes appear correctly on the site 3. Wait for explicit approval before pushing -## Jira Rules -**CRITICAL**: All Jira operations MUST follow the patterns defined in `.claude/commands/jira.md`. +## Jira Rules (Sumo Logic internal — requires Atlassian access) +**CRITICAL**: All Jira operations MUST follow the patterns defined in `.claude/commands/jira.md`. This section applies to Sumo Logic employees only — external contributors don't have access to the internal Jira instance and should skip it. ### Field Requirements - **Assignee**: Do not set manually — Jira Automation assigns based on Technical Area. @@ -130,8 +132,8 @@ If you change the `/help/llm/` URL structure or add new machine-readable mirror The sections below apply only to Claude Code. Other agents can ignore them. -### Jira Commands -All Jira operations MUST follow the patterns defined in `.claude/commands/jira.md`, including the three-approach ticket-creation pattern and Technical Area mappings. +### Jira Commands (Sumo Logic internal) +All Jira operations MUST follow the patterns defined in `.claude/commands/jira.md`, including the three-approach ticket-creation pattern and Technical Area mappings. Requires internal Atlassian access — not available to external contributors. ### Slash Commands Primary commands for documentation work. Proactively suggest when context fits — don't wait for the user to ask. diff --git a/README.md b/README.md index 7527ac943ee..403ad8839e0 100644 --- a/README.md +++ b/README.md @@ -13,9 +13,9 @@ Our site is built with [Docusaurus 3](https://docusaurus.io/) and supports React ## Get involved -We welcome contributions from the community. You can fix a typo, propose new content, or improve existing docs by [opening an issue](https://github.com/SumoLogic/sumologic-documentation/issues/new/choose) or submitting a pull request. +We welcome contributions from the community. You can fix a typo, propose new content, or improve existing docs by [opening an issue](https://github.com/SumoLogic/sumologic-documentation/issues/new/choose) or submitting a Pull Request (PR). -Browse [existing issues](https://github.com/SumoLogic/sumologic-documentation/issues) before opening a new one — someone may have already reported it. +Browse [existing issues](https://github.com/SumoLogic/sumologic-documentation/issues) before opening a new one. Someone may have already reported it. We use [cla-bot](https://colineberhardt.github.io/cla-bot/) to manage our Contributor License Agreement (CLA) process. You will be prompted to sign the CLA on your first contribution. @@ -43,7 +43,7 @@ We use [cla-bot](https://colineberhardt.github.io/cla-bot/) to manage our Contri Edit files using [Markdown syntax](https://www.sumologic.com/help/docs/contributing/style-guide/#markdown). Keep contributions concise, accurate, and aligned with our [Style Guide](https://www.sumologic.com/help/docs/contributing/style-guide/). -See our [Contributor Guidelines](https://www.sumologic.com/help/docs/contributing/create-edit-doc/#edit-a-doc) for details on Markdown editing, proposing bug fixes, and testing your changes. +See our [Contributor Guidelines](https://www.sumologic.com/help/docs/contributing/create-edit-doc/#edit-a-doc) for details on Markdown editing, proposing content fixes, and testing your changes. ## Build locally @@ -55,6 +55,8 @@ yarn start Any broken links or images will be listed in the output. Fix them, rebuild, and verify before submitting. Press `Ctrl + C` to stop the local server. +We exclusively use [Yarn](https://classic.yarnpkg.com/en/) for all installations and builds. Avoid using NPM commands for package installations or updates. + ## Repo structure | Path | Contents | @@ -66,21 +68,21 @@ Any broken links or images will be listed in the output. Fix them, rebuild, and | `/blog-csoar` | Cloud SOAR release notes | | `/static/img` | Images and media assets | | `sidebars.ts` | Left-nav sidebar configuration | -| `docusaurus.config.ts` | Site configuration | -| `cid-redirects.json` | Permanent URL redirects (CID mappings) | +| `docusaurus.config.js` | Site configuration | +| `cid-redirects.json` | URL redirects and CID mappings | -## For Docs Team contributors +## Claude Code tooling -This repo includes [Claude Code](https://claude.ai/code) tooling for the Docs Team — slash commands for creating docs, auditing content, managing Jira tickets, and more. See [CLAUDE.md](CLAUDE.md) for the full reference. +This repo includes [Claude Code](https://claude.ai/code) slash commands for creating docs, auditing content, and more. Most commands work for anyone with the repo cloned, including external contributors. The exception is Jira-related commands, which require internal Sumo Logic Atlassian access and are for Sumo Logic employees only. See [AGENTS.md](AGENTS.md) for the full reference. ## Publishing -Our docs team reviews issues and pull requests regularly. Response times may vary depending on the backlog. +Our docs team reviews issues and PRs regularly. Response times may vary depending on the backlog. Merge times depend on the type of change: -- **Content changes** (`docs/`, `blog-*`, `static/img`) — no hard merge window. We prefer U.S. or India business hours when possible. -- **Back-end changes** (`src/`, `sidebars.ts`, config files, `.github/`) — merged **Monday–Friday, 7:00am–2:00pm PT** only, when the WebOps team is available. +- **Content changes** (`docs/`, `blog-*`, `static/img`): no hard merge window. We prefer U.S. or India business hours when possible. +- **Back-end changes** (`src/`, `sidebars.ts`, config files, `.github/`): merged **Monday–Friday, 7:00am–2:00pm PT** only, when the WebOps team is available. PRs that mix content and back-end files follow the back-end rules. diff --git a/cid-redirects.json b/cid-redirects.json index c59fe975f77..0745d3f94a2 100644 --- a/cid-redirects.json +++ b/cid-redirects.json @@ -90,7 +90,6 @@ "/docs/contributing/create-document": "/docs/contributing/create-edit-doc", "/docs/contributing/edit-doc": "/docs/contributing/create-edit-doc", "/docs/contributing/markdown-cheat-sheet": "/docs/contributing/style-guide", - "/docs/contributing/templates": "/docs/contributing/templates/generic-doc", "/docs/contributing/templates/template-doc": "/docs/contributing/templates/generic-doc", "/docs/c2c": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework", "/Send-Data": "/docs/send-data", diff --git a/docs/contributing/create-edit-doc.md b/docs/contributing/create-edit-doc.md index 399402b530e..360630db5ff 100644 --- a/docs/contributing/create-edit-doc.md +++ b/docs/contributing/create-edit-doc.md @@ -1,7 +1,7 @@ --- id: create-edit-doc title: Create or Edit a Doc -description: Learn how to create or edit a doc, write content in markdown, and submit your changes to our GitHub repository. +description: Learn how to create or edit a doc, write content in Markdown, and submit your changes to our GitHub repository. --- import useBaseUrl from '@docusaurus/useBaseUrl'; @@ -9,13 +9,16 @@ import Iframe from 'react-iframe'; Discovered an error in a document? Learn how to submit a fix, along with a comprehensive guide on creating or editing a Sumo Logic document. +:::tip Recommended: Use Claude Code +If you have [Claude Code](https://claude.ai/code) installed, this repo's `/doc`, `/audit-doc`, and `/seo-audit` slash commands can help you draft and review docs locally against your fork. See the [README](https://github.com/SumoLogic/sumologic-documentation#claude-code-tooling) for the full command list and which ones require internal access. +::: + ## Prerequisites -import DocPrereq from '../reuse/doc-prerequisites.md'; +import DocPrereq from '../reuse/contributing/doc-prerequisites.md'; - ## Quickstart ### Submit a GitHub Issue @@ -26,7 +29,7 @@ Before submitting an issue, you can browse our [existing GitHub issues](https:// ### Submit a minor fix -Submitting a minor fix, such as correcting a typo, is very easy and can be done quickly without having to clone or fork your GitHub repository locally. Check out the instructions below. +You can submit a minor fix, like a typo correction, without cloning or forking the repository locally. Check out the instructions below. :::training Micro Lesson Check out this brief tutorial on how to submit a basic change to our docs. @@ -61,21 +64,13 @@ This will fork and submit changes to the Docs Team for review. ### Step 1: Fork the Sumo Docs repository -1. Fork the [Sumo Docs repository](https://github.com/SumoLogic/sumologic-documentation) locally. Remember to sync your fork and update branches as needed. - :::tip GitHub tips - * [How to fork a repo](https://help.github.com/articles/fork-a-repo/) - * [How to sync your fork with branches](https://help.github.com/articles/syncing-a-fork/) - ::: -1. Review our [README](https://github.com/SumoLogic/sumologic-documentation#readme) documentation guidelines. -1. Create a new branch from your forked repo using a name that best describes the work or references a GitHub issue number. For example, if you wanted to submit a PR to edit our Elasticsearch app doc, you'd write something like: `-apps-elasticsearch`. - -import Tools from '../reuse/contributing/tools.md'; +import ForkRepo from '../reuse/contributing/fork-repo.md'; - + ### Step 2: Edit your doc -In your new branch, edit the doc markdown file. See our [Style Guide](/docs/contributing/style-guide) to learn how to style content, add code snippets, import multimedia, and more. Doc body text content is written in GitHub-flavored markdown, with some customizations. +In your new branch, edit the doc Markdown file. See our [Style Guide](/docs/contributing/style-guide) to learn how to style content, add code snippets, import multimedia, and more. Doc body text content is written in GitHub-flavored Markdown, with some customizations. ### Step 3: Preview your changes @@ -89,37 +84,30 @@ In your new branch, edit the doc markdown file. See our [Style Guide](/docs/cont To submit more extensive edits, such as creating a new doc, we recommend forking our repo, making changes in a new branch, and submitting a PR for review. -Feel free to [reach out to the Docs Team](#contact-us) to discuss. We're happy to work with you on the project and talk through rewriting content, changing flow, adding a new topic or section, and deprecating content. +Feel free to [reach out to the Sumo Logic Docs Team](#contact-us) to discuss. We're happy to work with you on the project and talk through rewriting content, changing flow, adding a new topic or section, and deprecating content. ### Step 1: Fork the Sumo Docs repository -import ForkRepo from '../reuse/contributing/fork-repo.md'; - - - ### Step 2: Create a doc file -Our docs are GitHub-flavored markdown files containing content like bulleted instructions, screenshots, tables, interactive code samples, and more. +Our docs are GitHub-flavored Markdown files containing content like bulleted instructions, screenshots, tables, interactive code samples, and more. 1. Open your new branch in your IDE and go to the `/docs` folder. -1. Create a new markdown file in the format `.md` and save it to the appropriate subfolder. For example, if you're creating a new metrics doc, you'd save it to the `/docs/metrics` folder. +1. Create a new Markdown file in the format `.md` and save it to the appropriate subfolder. For example, if you're creating a new metrics doc, you'd save it to the `/docs/metrics` folder. 1. At the top of your file, add your frontmatter, which is the doc metadata. Follow the instructions under [Frontmatter](/docs/contributing/style-guide/#metadata-frontmatter), and see [Metadata descriptions](/docs/contributing/style-guide/#metadata-descriptions) for description length and formatting rules. - ### Step 3: Write your doc -In your Integrated Development Environment (IDE), compose the body of your document. - -Refer to our [Style Guide](/docs/contributing/style-guide) for instructions on crafting and styling content, including adding code snippets, importing multimedia, and more. The body text of your document is written in GitHub-flavored markdown, with some customizations. +In your Integrated Development Environment (IDE), compose the body of your document in GitHub-flavored Markdown. Refer to our [style guide](/docs/contributing/style-guide) for instructions on crafting and styling content, including adding code snippets, importing multimedia, and more. ### Step 4: Add doc to the navigation menu To add your new doc to the left-nav menu, you'll need to add its name and file path to the [`sidebars.ts` file](https://github.com/SumoLogic/sumologic-documentation/blob/main/sidebars.ts). -:::note Doc Team Support -The Sumo Logic Doc Team can help you add your doc to the sidebar and top navigation. If you have suggestions, include those in your Pull Request description. If you add the documentation to the sidebar, the team will review the location and names for building and placement in navigation. +:::note Docs Team Support +The Docs Team can help you add your doc to the sidebar and top navigation. If you have suggestions, include those in your PR description. If you add the documentation to the sidebar, the team will review the location and names for building and placement in navigation. ::: ### Step 5: Add doc to the hub page @@ -132,12 +120,12 @@ Once you decide on placement, use the card HTML code in that doc to create a new ### Step 6: Create CID URL -We often encounter changes in links, so we assign each document a permanent URL, which includes a Content ID (CID) number. This permanent URL performs a 301 redirect to the canonical URL. This approach ensures that future modifications to the canonical URL, such as product name changes, do not affect the 'Learn More' links for users. Additionally, it reduces the need for code changes to the user interface, offering greater flexibility for making quick updates. +We assign each document a permanent URL with a content ID (CID) number, which performs a 301 redirect to the canonical URL. This means future changes to the canonical URL, such as a product name change, won't break **Learn More** links or require code changes to the user interface. This URL is then placed in the UI in the appropriate place. For example, `cid=0071` links to a metrics page, which appears in the product in the **Metrics** section as a help link. To create a CID: -1. In your GitHub authoring tool (like Atom or VS Code), open our [cid-redirects.json file](https://github.com/SumoLogic/sumologic-documentation/blob/main/cid-redirects.json), which contains all 301 redirects. +1. In a GitHub authoring tool like VS Code, open our [cid-redirects.json file](https://github.com/SumoLogic/sumologic-documentation/blob/main/cid-redirects.json), which contains all 301 redirects. 1. Scroll down to the CIDs section, where the line items start with `"/cid/"`. 1. Find an unused CID number, then associate that CID value to your doc's file path. For example, if `5122` is unused, and your file path is `/docs/metrics/chart`: ```json title="Example" {2} @@ -163,22 +151,10 @@ import Submit from '../reuse/contributing/submit.md'; ## What happens next? -Docs Team members will review contributions, provide feedback, and approve. When approved, the Docs Team will merge and update staging. Updates to production will be handled by the Docs Team. +The Docs Team will review contributions, provide feedback, and merge approved changes to staging. They'll handle production updates separately. ## Contact us Need to get in touch? You can find us at: * [Sumo Logic Support](https://support.sumologic.com/support/s) * [Sumo Logic Community](https://sumologic.my.site.com/support/s/) -* [Sumo Dojo Slack](https://sumodojo.slack.com) - - - diff --git a/docs/contributing/index.md b/docs/contributing/index.md index 0121f114e08..bb8a08377bf 100644 --- a/docs/contributing/index.md +++ b/docs/contributing/index.md @@ -1,20 +1,16 @@ --- slug: /contributing title: Contribute to Sumo Docs -description: Learn how to provide feedback and contribute to Sumo Logic Docs, an open source project. +description: Learn how to provide feedback and contribute to Sumo Logic Docs, an open-source project. --- import useBaseUrl from '@docusaurus/useBaseUrl'; -Welcome to Sumo Logic Open Source! +Welcome to the Sumo Logic open source docs! -We're a community of developers and practitioners dedicated to building reliable and secure modern apps. At Sumo Logic, we believe in the power of collaboration and community-driven innovation. Our open-source projects go beyond code—they're about fostering a vibrant, inclusive community where every contribution, big or small, makes an impact. +This [repository](https://github.com/SumoLogic/sumologic-documentation) is the open-source home for Sumo Logic's documentation. Whether you're fixing a typo, clarifying a confusing section, adding a new doc, or sharing feedback, every contribution helps other users get more out of Sumo Logic. We welcome contributors of every experience level. -Whether you’re fixing bugs, adding features, writing documentation, or sharing feedback, your contributions help others to learn and grow within the Sumo Logic ecosystem. From typo fixes to new docs, we welcome all forms of participation. - -Our open-source [documentation](https://github.com/SumoLogic/sumologic-documentation) project is hosted on GitHub, where you can find all the resources to get started—guidelines on creating files, writing in Markdown, using templates, and submitting pull requests. - -Whether you’re a seasoned developer or just starting, join us in building tools that help everyone better understand and optimize their systems. Ready to contribute? Explore the articles below and get involved today! +Our GitHub repo includes guidelines on creating files, writing in Markdown, using templates, and submitting Pull Requests (PRs). Ready to contribute? Explore the guides below. You can also explore more Sumo Logic open-source projects on our [GitHub site](https://github.com/SumoLogic). @@ -22,31 +18,43 @@ You can also explore more Sumo Logic open-source projects on our [GitHub site](h
Documentation icon

Create or Edit a Doc

+

Create or edit a doc and submit a PR.

Documentation icon

Move or Remove a Doc

+

Move or remove a doc and set up a redirect.

Documentation icon

Style Guide

+

Styling and formatting conventions for Sumo Logic Docs.

Documentation icon

Glossary

+

Definitions of Sumo Logic terms and features you'll encounter in the docs.

Documentation icon

Word List

+

Preferred spelling, capitalization, and punctuation for Sumo Logic terms.

+
+
+
+
+ Documentation icon

Docs Templates

+

Copy-paste templates for starting a new doc, App Catalog doc, or Cloud-to-Cloud source doc.

Documentation icon

Code of Conduct

+

Our community standards for contributors.

diff --git a/docs/contributing/remove-doc.md b/docs/contributing/remove-doc.md index b1949a83cfd..da99f76053b 100644 --- a/docs/contributing/remove-doc.md +++ b/docs/contributing/remove-doc.md @@ -10,13 +10,23 @@ When you move a doc or remove it altogether, that deletes its URL. Visiting the To prevent this, create a 301 redirect. Follow these steps to ensure a smooth transition and maintain the health of our docs site. +:::tip Recommended: Use Claude Code +If you have [Claude Code](https://claude.ai/code) installed, this repo's `/remove-doc` slash command automates the steps below, including creating the redirect, updating internal links, and removing the doc from navigation. See the [README](https://github.com/SumoLogic/sumologic-documentation#claude-code-tooling) for the full command list and which ones require internal access. +::: + ## Prerequisites -import DocPrereq from '../reuse/doc-prerequisites.md'; +import DocPrereq from '../reuse/contributing/doc-prerequisites.md'; -## Step 1: Create a 301 redirect +## Step 1: Fork the Sumo Docs repository + +import ForkRepo from '../reuse/contributing/fork-repo.md'; + + + +## Step 2: Create a 301 redirect As an example, let's say there are two docs called **Nginx App** and **Nginx (Legacy) App**, and we need to deprecate the latter. @@ -26,29 +36,45 @@ As an example, let's say there are two docs called **Nginx App** and **Nginx (Le "/docs/integrations/web-servers/nginx-legacy": "/docs/integrations/web-servers/nginx", ``` -## Step 2: Update internal links +## Step 3: Update internal links Ensure any internal links pointing to the deleted doc are updated to the new URL. 1. In your GitHub authoring tool, run a search for the URL you're removing. For example, if the legacy URL appears in other documents, replace all instances with the new URL.
Screenshot of a 'Find All' search for the URL to be removed :::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'; + + + +## Step 7: Submit your request + +import Submit from '../reuse/contributing/submit.md'; + + + +## Step 8: Test the redirect + +After your pull request is merged and deployed, visit the old URL and verify that it performs a 301 redirect to the intended destination. + +## What happens next? -Verify that the redirect works correctly and leads to the intended destination. +The Docs Team will review your pull request, provide feedback, and merge approved changes to staging. They'll handle production updates separately. ## Optional steps @@ -66,7 +92,7 @@ You can prevent content from being indexed by excluding it from compilation enti To exclude docs, add their paths to the `docs.exclude` setting in `docusaurus.config.js`: -```json title="docusaurus.config.js" +```js title="docusaurus.config.js" presets: [ [ '@docusaurus/preset-classic', @@ -82,8 +108,8 @@ presets: [ ]; ``` -Any markdown files in the listed directories are excluded from the build and won't be served or indexed. Note that `reuse` files are still embedded where referenced — they just won't compile as standalone pages. +Any Markdown files in the listed directories are excluded from the build and won't be served or indexed. Note that `reuse` files are still embedded where referenced; they just won't compile as standalone pages. -For finer-grained control — for example, keeping a page compiled but hidden from search — use `robots.txt` or `noindex` meta tags instead. If content should never be published at all, excluding it from compilation is the most reliable approach. +For finer-grained control, such as keeping a page compiled but hidden from search, use `robots.txt` or `noindex` meta tags instead. If content should never be published at all, excluding it from compilation is the most reliable approach. If a document has already been indexed and needs to be urgently removed from Google search results, follow [Google's removal instructions](https://support.google.com/webmasters/answer/9689846?sjid=11985967130976965420-NC). diff --git a/docs/contributing/style-guide.md b/docs/contributing/style-guide.md index e01c3745a4e..551115ed743 100644 --- a/docs/contributing/style-guide.md +++ b/docs/contributing/style-guide.md @@ -42,6 +42,10 @@ To create a new doc quickly, use a template. You can copy and paste the file, ad * [Partner app template](/docs/contributing/templates/partner-app-doc) ::: +:::tip Recommended: Use Claude Code +If you have [Claude Code](https://claude.ai/code) installed, this repo's `sumo-style` skill automatically applies the conventions on this page when you draft or edit docs — you don't need to invoke it manually. See [AGENTS.md](https://github.com/SumoLogic/sumologic-documentation/blob/main/AGENTS.md) for details. +::: + ## Voice and tone * **Clarity and professionalism**. We are clear, genuine, and trustworthy. We understand that our customers entrust us with their vital data and never make light about our commitment to data access and security. @@ -1608,7 +1612,7 @@ For clarity and search engine discoverability: * Example: _System architecture and monitoring_. :::sumo For internal contributors -* If you change a URL, set up a [redirect](/docs/contributing/remove-doc#step-1-create-a-301-redirect) so that users don’t get a 404 page. +* If you change a URL, set up a [redirect](/docs/contributing/remove-doc#step-2-create-a-301-redirect) so that users don’t get a 404 page. * Use Google Analytics to make data-driven decisions. ::: diff --git a/docs/contributing/templates/app-template-v2.md b/docs/contributing/templates/app-template-v2.md index 139efc19012..65b1b46c0b8 100644 --- a/docs/contributing/templates/app-template-v2.md +++ b/docs/contributing/templates/app-template-v2.md @@ -4,14 +4,23 @@ title: Apps Template description: Use this template to create an App Catalog doc (/docs/integrations/...). --- -Use this template to create an [App Catalog](/docs/integrations) doc. Copy and paste this into your new .md file. Refer to the [Style Guide](/docs/contributing/style-guide) if needed. + + + + +Use this template to create an [App Catalog](/docs/integrations) doc. + +:::tip Recommended: Use Claude Code +Skip copying this template by hand. If you have [Claude Code](https://claude.ai/code) installed, use the `/app-doc` slash command to scaffold a new app doc for you. See the [README](https://github.com/SumoLogic/sumologic-documentation#claude-code-tooling) for the full command list. +::: + +Copy and paste this into your new .md file. Refer to the [Style Guide](/docs/contributing/style-guide) if needed. ```md --- -id: vendor-name #example: acme -title: Vendor Name #example: Acme -image: 'https://app_icons.s3.amazonaws.com/dropbox.svg' #replace with your app logo +id: {{vendor-name}} #example: acme +title: {{Vendor Name}} #example: Acme tags: - apps - vendor-name #example: acme @@ -20,7 +29,7 @@ description: 'The Sumo Logic app for {{vendor name}} analyzes...' #Aim for 140 import useBaseUrl from '@docusaurus/useBaseUrl'; -\Introduction: The Sumo Logic app for `{{vendor name}}`, which `{{vendor description}}` enables you to `{{verb}}` `{{data type}}` from `{{vendor name}}`. This integration helps you `{{business value, security, performance outcome}}`, providing visibility into `{{specific activities, events, or metrics}}`. With this data in Sumo Logic, you can `{{key use cases}}`.\ +\Introduction: The Sumo Logic app for `{{vendor name}}`, which `{{vendor description}}`, enables you to `{{verb}}` `{{data type}}` from `{{vendor name}}`. This integration helps you `{{business value, security, performance outcome}}`, providing visibility into `{{specific activities, events, or metrics}}`. With this data in Sumo Logic, you can `{{key use cases}}`.\ diff --git a/docs/contributing/templates/c2c-source.md b/docs/contributing/templates/c2c-source.md index b398b245df6..75891e2ca30 100644 --- a/docs/contributing/templates/c2c-source.md +++ b/docs/contributing/templates/c2c-source.md @@ -4,14 +4,23 @@ title: Cloud-to-Cloud Source Template description: Use this template to create a Cloud-to-Cloud source doc (/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/...). --- -Use this template to create a [Cloud-to-Cloud source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework) doc. Copy and paste this into your new .md file. Refer to the [Style Guide](/docs/contributing/style-guide) if needed. + + + + +Use this template to create a [Cloud-to-Cloud source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework) doc. + +:::tip Recommended: Use Claude Code +Skip copying this template by hand. If you have [Claude Code](https://claude.ai/code) installed, use the `/c2c-source-doc` slash command to scaffold a new C2C doc for you. See the [README](https://github.com/SumoLogic/sumologic-documentation#claude-code-tooling) for the full command list. +::: + +Copy and paste this into your new .md file. Refer to the [Style Guide](/docs/contributing/style-guide) if needed. ```md --- id: {{vendor-name}}-source #example: druva-source title: {{Vendor Name}} Source #example: Druva Source -image: 'https://app_icons.s3.amazonaws.com/dropbox.svg' #replace with your app logo sidebar_label: {{Vendor Name}} #example: Druva tags: - cloud-to-cloud diff --git a/docs/contributing/templates/generic-doc.md b/docs/contributing/templates/generic-doc.md index ac639d5446b..be215743356 100644 --- a/docs/contributing/templates/generic-doc.md +++ b/docs/contributing/templates/generic-doc.md @@ -8,7 +8,13 @@ description: Use this generic template to create a Sumo Logic doc. -Use this generic template to create a new doc. Copy and paste this into your new .md file and refer to the [Style Guide](/docs/contributing/style-guide). +Use this template to create a new generic doc. + +:::tip Recommended: Use Claude Code +Skip copying this template by hand. If you have [Claude Code](https://claude.ai/code) installed, use the `/doc` slash command to scaffold a new doc for you. See the [README](https://github.com/SumoLogic/sumologic-documentation#claude-code-tooling) for the full command list. +::: + +Copy and paste this into your new .md file and refer to the [Style Guide](/docs/contributing/style-guide). ```md diff --git a/docs/contributing/templates/index.md b/docs/contributing/templates/index.md new file mode 100644 index 00000000000..adf0a804e40 --- /dev/null +++ b/docs/contributing/templates/index.md @@ -0,0 +1,40 @@ +--- +slug: /contributing/templates +title: Docs Templates +description: Copy-paste templates for creating a new Sumo Logic Docs page, App Catalog doc, Cloud-to-Cloud source doc, or Partner app doc. +--- + +import useBaseUrl from '@docusaurus/useBaseUrl'; + +Copy one of these templates into a new `.md` file to start a doc from a consistent starting point. Refer to the [Style Guide](/docs/contributing/style-guide) as you fill it in. + +:::tip Recommended: Use Claude Code +Skip copying a template by hand. If you have [Claude Code](https://claude.ai/code) installed, these slash commands scaffold a new doc for you: `/doc` for a generic doc, `/app-doc` for an App Catalog doc, and `/c2c-source-doc` for a Cloud-to-Cloud source doc. For release notes, use `/release-note-service`, `/release-note-collector`, `/release-note-cse`, `/release-note-csoar`, or `/release-note-developer`. See the [README](https://github.com/SumoLogic/sumologic-documentation#claude-code-tooling) for the full command list. +::: + +
+
+
+ Documentation icon

Doc (Generic) Template

+

Create a general feature, how-to, or concept doc.

+
+
+
+
+ Documentation icon

Apps Template

+

Create an App Catalog integration doc.

+
+
+
+
+ Documentation icon

Cloud-to-Cloud Source Template

+

Create a Cloud-to-Cloud source doc.

+
+
+
+
+ Documentation icon

Partner App Template

+

Create a Sumo Logic Partner app doc.

+
+
+
diff --git a/docs/contributing/templates/partner-app-doc.md b/docs/contributing/templates/partner-app-doc.md index 7817206cd57..d76910f9aca 100644 --- a/docs/contributing/templates/partner-app-doc.md +++ b/docs/contributing/templates/partner-app-doc.md @@ -8,112 +8,14 @@ description: Use this template to create a Sumo Logic Partner app doc (/docs/int -Use this template to create a [Sumo Logic Partner app](/docs/integrations/partner-ecosystem-apps) doc. Copy and paste this into your new .md file. Refer to the [Style Guide](/docs/contributing/style-guide) if needed. +:::important +Most Partner Ecosystem apps are documented on the partner's own website or in the [sumologic-public-partner-apps](https://github.com/SumoLogic/sumologic-public-partner-apps) GitHub repo, not as an individual page on this site. Use this template only if you're creating a new, individually hosted partner app doc here. +::: +For [Sumo Logic Partner app](/docs/integrations/partner-ecosystem-apps) docs, follow the [apps template](/docs/contributing/templates/app-template-v2), and append this at the end: ```md - ---- -id: vendor-name -title: Vendor Name -description: Short description. ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -`Thumbnail icon` - -(Introduction about the app) - -\Add the description from the app description above\ - -## Log types and metrics - -The `{AppName}` App uses... - -\Enter a list of log types, usually hyperlinked to vendor docs.\ - -## Sample log and metrics messages - -### Log message - -```json title="Log message" -\ -``` - -### Metric message - -```json title="Metric message" -\ -``` - -## Sample queries - -### Log query - -```sql title="Log query" -\ -``` - -### Metric query - -```sql title="Metric query" -\ -``` - -## Prerequisites (optional) - -\Any steps like permissions or roles that the user should have for configuring the collection steps.\ - -## Collection configuration and app installation - -\This section instructions for collecting logs, metrics, or logs and metrics. You can also give link to collection docs if they are hosted publicly. Include a diagram, as appropriate. For an example, see [Collection process for GCP services](/docs/integrations/google/app-engine/#collection-process-for-gcp-services).\ - -### Step 1. - -\step description\ - -### Step 2. - -\step description\ - -### Step n. - -\step description\ - -## Install the `{AppName}` app - -import AppInstall from '../../reuse/apps/app-install.md'; - - - -## Viewing the `{AppName}` dashboards - -import FilterDashboards from '../../reuse/filter-dashboards.md'; - - - -### Dashboard 1 - -\Descriptions of each app dashboard.\ -\This section has dashboard description, use cases, and screenshot for each dashboard.\ - -The Overview Dashboard provides a quick snapshot of .... - - Use this dashboard to: -- \use-case-1\ -- \use-case-2\ - -### Dashboard 2 - -View stats and metrics related to ... - -Use this dashboard to: -- \use-case-1\ -- \use-case-2\ - ## Support This application has been developed and is supported by `{app-owner-name}`. In case of any technical queries, contact support at `support contact`. - ``` diff --git a/docs/reuse/contributing/doc-prerequisites.md b/docs/reuse/contributing/doc-prerequisites.md new file mode 100644 index 00000000000..58a8a627192 --- /dev/null +++ b/docs/reuse/contributing/doc-prerequisites.md @@ -0,0 +1,10 @@ +* You'll need a [GitHub account](https://github.com/signup/free) to contribute to Sumo Logic Docs. +* We recommend adding [2FA protection](https://devdocs.magento.com/contributor-guide/contributing.html#two-factor) when contributing to Sumo Logic repositories. +* Help us keep Sumo Logic Docs open and inclusive by reviewing our [Code of Conduct](/docs/contributing/code-of-conduct). + +**Recommended:** New to GitHub or Markdown? Try [VS Code](https://code.visualstudio.com/), a development application to open the repo, edit and create files, and preview pages as you write, along with the following extensions: + * Markdown All in One. + * Markdown Preview GitHub Styling. + * Markdown Preview Enhanced. + * Markdown Preview Mermaid Support. + * Mermaid Markdown Syntax Highlighting for charts and graphs. diff --git a/docs/reuse/contributing/fork-repo.md b/docs/reuse/contributing/fork-repo.md index e2537449a81..2143197d25a 100644 --- a/docs/reuse/contributing/fork-repo.md +++ b/docs/reuse/contributing/fork-repo.md @@ -1,11 +1,9 @@ -To create new doc, we recommend forking our repo, making changes in a new branch, and submitting a PR for review. - -Feel free to reach out to the Docs Team to discuss. We're happy to work with you on the project and talk through rewriting content, changing flow, adding a new topic or section, and deprecating content. - -1. Fork the [Sumo Docs repository](https://github.com/SumoLogic/sumologic-documentation) locally. Remember to sync your fork and update branches as needed. - :::tip GitHub tips - * [How to fork a repo](https://help.github.com/articles/fork-a-repo/) - * [How to sync your fork with branches](https://help.github.com/articles/syncing-a-fork/) - ::: +1. Fork the [Sumo Docs repository](https://github.com/SumoLogic/sumologic-documentation) locally. + :::tip GitHub tips + * [How to fork a repo](https://help.github.com/articles/fork-a-repo/) + * [How to sync your fork with branches](https://help.github.com/articles/syncing-a-fork/) + ::: 1. Review our [README](https://github.com/SumoLogic/sumologic-documentation#readme) documentation guidelines. -1. Create a new branch from your forked repo using a name that best describes the work or references a GitHub issue number. For example, if you wanted to submit a PR to edit our Elasticsearch app doc, you'd write something like: `-apps-elasticsearch`. +1. Create a new branch from your forked repo using a name that best describes the work or references a GitHub issue number. For example, if you wanted to submit a Pull Request (PR) to edit our Elasticsearch app doc, you'd write something like: `-apps-elasticsearch`. + +Remember to sync your fork and update branches as needed. diff --git a/docs/reuse/contributing/preview.md b/docs/reuse/contributing/preview.md index 0ab60b78a81..d0966dca726 100644 --- a/docs/reuse/contributing/preview.md +++ b/docs/reuse/contributing/preview.md @@ -1,9 +1,3 @@ -Before proceeding, you'll need to preview your changes. - -1. Go to the [Building Locally](https://github.com/SumoLogic/sumologic-documentation#building-locally) section in our README. -1. Review installation requirements. -1. Preview your build. +Before proceeding, you'll need to preview your changes. See the [Build Locally](https://github.com/SumoLogic/sumologic-documentation#build-locally) section in our README for instructions. This constructs and deploys a local version of the Sumo Logic Docusaurus site. Our site relies on Docusaurus, a static site generator. It creates your site as basic static HTML, JavaScript, and CSS files. - -We exclusively use [Yarn](https://classic.yarnpkg.com/en/) for all installations and builds. Avoid using NPM commands for package installations or updates. diff --git a/docs/reuse/contributing/submit.md b/docs/reuse/contributing/submit.md index 9a7122db14e..9ca75241d94 100644 --- a/docs/reuse/contributing/submit.md +++ b/docs/reuse/contributing/submit.md @@ -1,6 +1,6 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; -1. Commit your changes to the branch with a meaningful message.
Pull request
Use descriptive commit messages (and issue or ticket numbers, if applicable) detailing the content updates you are entering for content. One-line messages are fine for small changes, but bigger changes should look like this: +1. [Commit your changes](https://github.com/git-guides/git-commit) to the branch with a meaningful message.
Pull request
Use descriptive commit messages (and issue or ticket numbers, if applicable) that describe the changes you're making. One-line messages are fine for small changes, but bigger changes should look like this: ```bash $ git commit -m "A brief summary of the commit > @@ -11,17 +11,16 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; 1. Visit [our repo](https://github.com/SumoLogic/sumologic-documentation) after pushing your branch. If you see an option to **Compare & pull request** for your branch, click this.
Compare * 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**.
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**.
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.
CLA bot + 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.
CLA bot 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 @@ -
-New to GitHub and/or Markdown? Check out our recommended authoring tools. - -* [GitHub Desktop](https://desktop.github.com/). Easy-to-use interface to update your local machine clone, create branches, push to GitHub, and more. -* [VS Code](https://code.visualstudio.com/). Development application to open the repo, edit and create files, and preview pages as you write. We recommend the following extensions: - * Markdown All in One - * Markdown Preview GitHub Styling - * Markdown Preview Enhanced - * Markdown Preview Mermaid Support and Mermaid Markdown Syntax Highlighting for charts and graphs -* [iTerm2](https://iterm2.com/). Terminal application for macOS. You can also install [Oh My Zsh](https://ohmyz.sh/) for theming. - -
diff --git a/docs/reuse/doc-prerequisites.md b/docs/reuse/doc-prerequisites.md deleted file mode 100644 index 589d3a0a243..00000000000 --- a/docs/reuse/doc-prerequisites.md +++ /dev/null @@ -1,3 +0,0 @@ -* You'll need a [GitHub account](https://github.com/signup/free) to contribute to Sumo Logic Docs. -* We recommend adding [2FA protection](https://devdocs.magento.com/contributor-guide/contributing.html#two-factor) when contributing to Sumo Logic repositories. -* Help us keep Sumo Logic Docs open and inclusive by reviewing our [Code of Conduct](/docs/contributing/code-of-conduct). diff --git a/docusaurus.config.js b/docusaurus.config.js index cbaa18727b2..d572b0216a6 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -485,6 +485,11 @@ module.exports = { label: 'Traces, RUM, APM', icon: 'account_tree', }, + { + label: 'Contribute to Docs', + to: 'docs/contributing', + icon: 'edit_note', + }, ] }, { @@ -532,11 +537,6 @@ module.exports = { to: 'https://github.com/SumoLogic/sumologic-documentation/issues/new/choose', icon: 'thumbs_up_down', }, - { - label: 'Contribute to Docs', - to: 'docs/contributing', - icon: 'edit_note', - }, ], }, { diff --git a/sidebars.ts b/sidebars.ts index 71cca5484a2..ca05982e21f 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -60,20 +60,21 @@ module.exports = { 'contributing/style-guide', 'contributing/glossary', 'contributing/word-list', - 'contributing/code-of-conduct', // 'contributing/translations', { type: 'category', label: 'Docs Templates', collapsible: true, collapsed: true, + link: {type: 'doc', id: 'contributing/templates/index'}, items: [ 'contributing/templates/app-template-v2', 'contributing/templates/c2c-source', 'contributing/templates/generic-doc', 'contributing/templates/partner-app-doc', ] - } + }, + 'contributing/code-of-conduct', ], }, ],