> For the complete documentation index, see [llms.txt](https://wiki.nuance.xyz/nuance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.nuance.xyz/nuance/publications/how-to-manage-articles-for-editors.md).

# How to Manage Articles (For Editors)

Editors manage a publication's articles by reviewing, editing and publishing them.

When an author submits an article to your publication, it appears in your publication's article list for you to review.

From the article list, an editor can:

* Open an article by clicking its title. This opens the article so you can read and review it, and make any edits before it goes live.
* Publish or unpublish an article with the Live toggle on its row. Turn the toggle on to publish the article; turn it off to take a live article back down.

Each row also shows the article's published and modified dates. Article stats and assigning categories to articles are coming soon.


---

# 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://wiki.nuance.xyz/nuance/publications/how-to-manage-articles-for-editors.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.
