<commit_before>Hello! Thank you for choosing to help contribute to the SendGrid documentation site! There are many ways you can contribute and help is always welcome. When writing documentation, we ask you to consider the following style guidelines.

* [Style](#style)
    * [Numbers](#numbers)
    * [About additional resources](#about-additional-resources)
    * [Cross references](#cross-references)
    * [Head matter](#head-matter)
* [Terminology](#terminology)
* [Punctuation](#punctuation)
* [Capitalization](#capitalization)
* [Warning and info blocks](#warning-and-info-blocks)
* [Screenshots](#screenshots)


<a name="style"></a>
## Style

We strive to make our documentation concise, clear, organized, and scannable.

* Use conversational language and industry-standard terms when possible.
* Contractions are OK and preferred.
* Use bulleted lists and numbered steps where applicable.

When documenting a UI action, make it **bold**. Avoid using the word "button" in the step and simply refer to the name on the UI element.
    For example, "Enter your username and password, and then click **login**."

Where possible, write pages in a "jobs to be done" format. Jobs to be done style includes:

* Table of contents at the beginning
* "Additional Resources" section at the end
* Include sections to achieve the goal, with steps for each task (numbered steps, clear directions, and correct UI workflow)
	For an example, see [Sending a campaign]({{root_url}}/ui/sending-email/how-to-send-email-with-marketing-campaigns/)

**Avoid passive voice.** A good way to check if your sentence is in passive or not is to add "by zombies" to the end of it. If zombies end up doing the action, it's passive.

Example: Any templates, campaigns, contacts, or API keys created by the teammate will not be deleted....by zombies(!)

<a name="numbers"></a>
### Numbers

Use numerals instead of spelling them out. However, if a number leads off the sentence, spell it out.
YES: “SendGrid offers 10 templates in Marketing Campaigns.”
YES: “Ten templates are included in Marketing Campaigns.”

<a name="cross references"></a>
### Cross references

When referring to other pages in the documentation, make sure your link text is descriptive.

YES: For more information, see [Event Webhook] documentation.
NO: For more information, click [here].

<a name="head matter"></a>
### Head matter

The new head matter looks like this with the new Knowledge Center:
```
---
layout: page
weight: 0
group: 
title: 
seo:
  title: 
  description: 
  keywords: 
navigation:
  show: true
---
```

### Groups

The sections in **Bold** are the categories. The "group" field in the head matter pertains to the different headers article residing under a specific category. The group designation is after the colon of the "group" field.

src="https://github.com/sendgrid/docs/blob/develop/static/img/docs-architecture-group.png" width="676" height="386">
 
#### UI

**Sending Email**
- Building Email: building-email
- Delivery & Optimization: delivery-optimization
- Building Email with Marketing Campaigns: marketing-campaigns
- Building Transactional Email: transactional-email<commit_msg>Fixed broken image in styleguide.md<commit_after>Hello! Thank you for choosing to help contribute to the SendGrid documentation site! There are many ways you can contribute and help is always welcome. When writing documentation, we ask you to consider the following style guidelines.

* [Style](#style)
    * [Numbers](#numbers)
    * [About additional resources](#about-additional-resources)
    * [Cross references](#cross-references)
    * [Head matter](#head-matter)
* [Terminology](#terminology)
* [Punctuation](#punctuation)
* [Capitalization](#capitalization)
* [Warning and info blocks](#warning-and-info-blocks)
* [Screenshots](#screenshots)


<a name="style"></a>
## Style

We strive to make our documentation concise, clear, organized, and scannable.

* Use conversational language and industry-standard terms when possible.
* Contractions are OK and preferred.
* Use bulleted lists and numbered steps where applicable.

When documenting a UI action, make it **bold**. Avoid using the word "button" in the step and simply refer to the name on the UI element.
    For example, "Enter your username and password, and then click **login**."

Where possible, write pages in a "jobs to be done" format. Jobs to be done style includes:

* Table of contents at the beginning
* "Additional Resources" section at the end
* Include sections to achieve the goal, with steps for each task (numbered steps, clear directions, and correct UI workflow)
	For an example, see [Sending a campaign]({{root_url}}/ui/sending-email/how-to-send-email-with-marketing-campaigns/)

**Avoid passive voice.** A good way to check if your sentence is in passive or not is to add "by zombies" to the end of it. If zombies end up doing the action, it's passive.

Example: Any templates, campaigns, contacts, or API keys created by the teammate will not be deleted....by zombies(!)

<a name="numbers"></a>
### Numbers

Use numerals instead of spelling them out. However, if a number leads off the sentence, spell it out.
YES: “SendGrid offers 10 templates in Marketing Campaigns.”
YES: “Ten templates are included in Marketing Campaigns.”

<a name="cross references"></a>
### Cross references

When referring to other pages in the documentation, make sure your link text is descriptive.

YES: For more information, see [Event Webhook] documentation.
NO: For more information, click [here].

<a name="head matter"></a>
### Head matter

The new head matter looks like this with the new Knowledge Center:
```
---
layout: page
weight: 0
group: 
title: 
seo:
  title: 
  description: 
  keywords: 
navigation:
  show: true
---
```

### Groups

The sections in **Bold** are the categories. The "group" field in the head matter pertains to the different headers article residing under a specific category. The group designation is after the colon of the "group" field.

![Document architecture schematic.](https://github.com/sendgrid/docs/blob/develop/static/img/docs-architecture-group.png)
 
#### UI

**Sending Email**
- Building Email: building-email
- Delivery & Optimization: delivery-optimization
- Building Email with Marketing Campaigns: marketing-campaigns
- Building Transactional Email: transactional-email
{'fraction_non_alphanumeric': 0.09721128092011974, 'fraction_numerical': 0.0018906570033086498, 'mean_word_length': 4.662801070472792, 'pattern_counts': {'":': 0, '<': 19, '<?xml version=': 0, '>': 20, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1299797', 'n_tokens_mistral': 1768, 'n_tokens_neox': 1644, 'n_words': 789}