Skip to content

Commit 2e53b2c

Browse files
committed
Delete comments
1 parent 29827a5 commit 2e53b2c

File tree

1 file changed

+1
-29
lines changed
  • src/connections/destinations/catalog/actions-drip

1 file changed

+1
-29
lines changed

src/connections/destinations/catalog/actions-drip/index.md

Lines changed: 1 addition & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,32 +1,4 @@
1-
# 💥 Segment Partner Actions Destination Documentation Template
2-
3-
> Hi Partners 👋🏼
4-
>
5-
> Welcome to Segment - glad to have you onboard! This doc serves as a guideline for your team to create best-in-class documentation alongside your amazing product.
6-
>
7-
> Here are the guidelines we want you to have in mind when writing out your documentation:
8-
>
9-
> - Be succinct and simple in your writing. Reduce text bloat where possible.
10-
> - Avoid 1st person language as it’s confusing for customers if they don’t know who wrote the docs (Segment or the Partner).
11-
> - Where pre-reading is required, hyperlink to other more generic parts of Segment’s (or your) documentation.
12-
>
13-
> - Screenshots/Images are generally discouraged unless absolutely necessary
14-
>
15-
> The below template intends to provide a standardized structure. To submit your documentation, complete the following steps:
16-
>
17-
> 1. Fork and clone the `segment-docs` repo locally
18-
> 2. Create a new branch (e.g., partner-name/destination)
19-
> 3. Create an `index.md` file in the following path `src/connections/destinations/catalog/{destination-slug}/index.md
20-
> 4. Copy the template below into your `index.md` file, and edit it to be in line with how your integration operates
21-
> 5. Add, commit, and push your code, then submit a pull request to the `segment-docs` repo
22-
>
23-
> If a section does not apply to your integration, feel free to remove. Please don’t create separate sections unless absolutely necessary. In most cases, creating a H3 (###) sub-heading under an existing section is the best option!
24-
>
25-
> If you have any questions in the meantime, please reach out to our team at [email protected].
26-
27-
## Template begins here...
28-
29-
---
1+
--
302
title: Drip (Actions) Destination
313
---
324

0 commit comments

Comments
 (0)