> For the complete documentation index, see [llms.txt](https://sftpmag.gitbook.io/sftp-publishing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sftpmag.gitbook.io/sftp-publishing/web-social/web-editor-s-role.md).

# Web editor(s) role

This is a job description for the role of web editor, which may be split up between a number of people. 

The tasks this person/group is responsible for are:

**For each issue:** 

* Work with Managing Editor to get final versions of articles and coordinate on when they should be published
* Create a new page for each issue
* Create post drafts in WordPress for each article, properly format the text to adhere to consistent rules, fill in metadata where appropriate (i.e. page excerpt, author, category, tags, etc), add footnotes into the document, and link to translations if relevant
* Add and place any relevant art into the article and add captions, making sure it is properly formatted
* Publish the article when the publish date comes (to be determined with managing editor) 
* Adjust the SEO settings (keywords, previews, etc) and coordinate with social media team to share once posted

**Overall:**

* Place any articles outside the issue online as they come
* Make any necessary small aesthetic changes to the website (e.g., header color, reorganizing images on front page)\ <br>


---

# 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://sftpmag.gitbook.io/sftp-publishing/web-social/web-editor-s-role.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.