> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/newsroom-planner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/newsroom-planner/2.0.0-7/text-assignments/edit-article-on-assignment.md).
# Edit article on assignment
When you want to work with an article in the view My assignment you start by choosing the date when your assignment is planned. As we described earlier there could be an article already created on the article, or there is no article created.
When there is an article created on the assignment you click on the article, you see that your article will get a blue border so you easily see which assignment you are working on (1). The article will be opened to the right of the screen (2). You work on your article and click on Save when you are done with your editing (3). You can also click on Close (4).
If the assignment does not have a created article already, or if you need to make one more article on the same assignment, you click on New article. The article will be created and shown to the right on the screen the same way as described above and you can start working on it.
---
# 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.navigaglobal.com/newsroom-planner/2.0.0-7/text-assignments/edit-article-on-assignment.md?ask=&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.
