> For the complete documentation index, see [llms.txt](https://docs.demos.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.demos.global/hiring-demos/social-liaison-content-manager.md).

# 📝Social Liaison Content Manager

## Management of Social Content Calendar

### <mark style="color:yellow;">Roles & Responsibilities</mark>&#x20;

* Coordinate approvals & Reviews of content.
* Schedule and confirm dates.
* Prestage content in Demos Content Calendar for review

1. Schedule Tweets and Blog posts from the content calendar
2. Request creation of graphics/media requests through ClickUp
3. Post Tweet links to internal social media channels internally after posting
4. Assemble/create short-form content ideas for blogs and posts

<mark style="color:yellow;">SKILLS:</mark>

1. Good Communication and coordination skills.
2. Basic documentation creation.
3. Grammarly Application.
4. Using and posting to social channels, Twitter, Discord & Telegram.
5. Utilizing Google Docs / Sheets.

Nice to have&#x20;

* Using Slack Application
* Using Clickup Application


---

# 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.demos.global/hiring-demos/social-liaison-content-manager.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.