Skip to content

Commit 6792d40

Browse files
authored
DOCS-1098 - Docs templates - standardize app/source intros with Sumo Logic naming (#5866)
* Docs templates - standardize app/source intros with Sumo Logic naming * grammar fixes
1 parent df3be76 commit 6792d40

File tree

3 files changed

+22
-4
lines changed

3 files changed

+22
-4
lines changed

docs/contributing/style-guide.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1085,7 +1085,17 @@ tags: [metrics, traces]
10851085
10861086
For a full list of options, see [Docusaurus Markdown front matter](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-docs#markdown-front-matter).
10871087
1088+
### Branding and naming in app/source docs
10881089
1090+
To ensure consistency between our UI and our documentation, every App and Source doc must begin by clearly identifying it as a Sumo Logic integration. The UI often shows only the vendor name (for example, "Slack", "Amazon S3"), so the documentation must reinforce that Sumo Logic is delivering the integration.
1091+
1092+
* **App docs**. The `description:` frontmatter and intro paragraph must start with: "The Sumo Logic app for [vendor]..." (see [template](/docs/contributing/templates/app-template-v2)).
1093+
* **Source docs**. The `description:` frontmatter and intro paragraph must start with: "The Sumo Logic source for [vendor]..." (see [template](/docs/contributing/templates/c2c-source)).
1094+
1095+
This rule helps:
1096+
* Align docs with UI naming ("[vendor] by Sumo Logic”).
1097+
* Reinforce Sumo Logic as the provider of the integration.
1098+
* Prevent ambiguity that suggests the vendor is the owner of the app/source.
10891099
10901100
## Navigation menus
10911101

docs/contributing/templates/app-template-v2.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,15 @@ description: Description goes here. #example: The Sumo Logic App for Split enabl
1111

1212
import useBaseUrl from '@docusaurus/useBaseUrl';
1313

14-
/Introduction/
14+
<head>
15+
<meta name="robots" content="noindex" />
16+
</head>
17+
18+
\Introduction\
19+
20+
<!-- RULE: Always start with "The Sumo Logic app for [vendor]" in both the description (frontmatter) and the intro paragraph to ensure brand visibility and consistency with "[vendor] by Sumo Logic" in the UI. The exact wording after that can be adapted. This example shows a common structure, but you may rephrase to fit the use case. -->
21+
22+
The Sumo Logic app for [vendor] enables you to [monitor/analyze/collect/etc.] [data type] from [vendor]. 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 [identify/respond to/optimize/etc.] [key use cases].
1523

1624
## Data collected
1725

@@ -108,4 +116,4 @@ import AppUpdate from '../../reuse/apps/app-update.md';
108116

109117
import AppUninstall from '../../reuse/apps/app-uninstall.md';
110118

111-
<AppUninstall/>
119+
<AppUninstall/>

docs/contributing/templates/c2c-source.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,9 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
2020

2121
\Introduction\
2222

23-
The `{{source name}}` collects `{{data/event types}}` from `{{source of origin}}``{{What the app does}}`.
23+
<!-- RULE: Always start with "The Sumo Logic source for [vendor]" in both the description (frontmatter) and the intro paragraph. This ensures brand clarity since the UI shows only the vendor name. The exact wording after that can be adapted. This example shows a common structure, but you may rephrase to fit the use case. -->
2424

25-
Example: The Microsoft Graph Security API Source provides a secure endpoint to consume alerts from the Microsoft Graph Security API endpoint. It securely stores the required authentication, scheduling, and state tracking information. One threat event is reported for each affected device.
25+
The Sumo Logic source for [vendor] enables you to [collect/ingest/stream/etc.] [data type] from [vendor] into Sumo Logic. This integration helps you [business value/security/observability outcome], providing visibility into [specific activities, events, or metrics]. With this data in Sumo Logic, you can [detect/respond/optimize/etc.] [key use cases].
2626

2727
\Depending on the availability in the Fed, add the below note.\
2828

0 commit comments

Comments
 (0)