# How to publish a newsletter in your community

{% embed url="<https://www.youtube.com/watch?index=50&list=PLWB9ROSX-JSjbSyx9Hutrzi9Wk6B0WtRS&v=4sBHZRhB7wI>" %}

1. Go to communty dashboard
2. Go to **Newsletters** tab
3. Click **Create Newsletter**
4. Fill the following fields
   1. Title
   2. Bried description (helps with SEO)
   3. Add email subject (for newsletter to be delivered to your members, don't worry, it won't be sent automatically)
   4. Choose the editor type (rich text editor or drag n drop editor)
   5. Create content of the editor
   6. Click **Save & Publish** if you are ready to publish, or you can save a draft also
5. It will take you back to the list of newsletters
6. Here you can choose to publish and schedule an email to all your members

{% hint style="warning" %}
Before hitting that Publish button, you are advised to use the Send Testing Emails to your team to check the newsletter.
{% endhint %}

{% hint style="info" %}
You will be able to see the stats of the number of opens and clicks to all your members. The total count of sent and delivered might differ if people have unsubscribed to your newsletters earlier or overall from Commudle's emails
{% endhint %}

{% hint style="info" %}
Email subjects need to be smartly created so that the newsletter email doesn't land into spam and also gets higher open rates. Beware of using clickbaits as it increases unsubscribers.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.commudle.com/community-newsletters/how-to-publish-a-newsletter-in-your-community.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.