> 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

Role: 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.demos.global/hiring-demos/social-liaison-content-manager.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
