> For the complete documentation index, see [llms.txt](https://docs.deepwork.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepwork.studio/teams-departments/operations/roles/newsletter-writer.md).

# Newsletter Writer

## Goals

* Inform community about important events
* Publish a newsletter with actionable steps to get involved

## Workflow

* Write bullet points throughout the month around what has been happening in the organization, categorised by team.
* Record the bi-weekly heartbeat session.
* Extract the transcript, upload it to AskYourPDF.
* Use the transcript in GPT along with the notes to create a summary with each team as a header.
  * *Convert the discussion from the transcript above into a newsletter with the headers from the following notes:*
* Improve the output text by adhering to the following format:
  * *Use bullet points for each section with keywords in bold*
  * *Use shorter than 30 words per sentence*
  * *Replace adjectives with data*
  * *Eliminate weasel words*
  * *Pass the “so what” test*
  * *Avoid jargon & acronyms*
  * *Use subject-verb-object structure*
  * *Avoid clutter*
* Review the result manually, add links
* Create top section for the newsletter
* Add images
* Publish


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.deepwork.studio/teams-departments/operations/roles/newsletter-writer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.