> For the complete documentation index, see [llms.txt](https://medievalbook.gitbook.io/digitizing-medieval-archives/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://medievalbook.gitbook.io/digitizing-medieval-archives/week-13/github-project-boards.md).

# Github Project Boards

[Our Github project page ](https://github.com/MedievalBook/HIST4006/projects/1)is largely empty at this point. The goal is that it becomes a way for everyone to work together on a final project. Check it out before doing anything else. Yup. Not very exciting. 

1. Making sure you are signed into Github, check to see whether you can edit the project board. 
2. If yes, great! Post on the Slack #github channel that you can edit the project board. 
3. If no, post that you can't on the Slack #github channel. I'll try to make sure everyone can edit. 
4. Read [this introduction](https://github.community/t5/Support-Protips/Using-project-boards-for-task-management/ba-p/8437) to the Github Project board.
5. Play with a bit. 
6. Decide whether to use this or stick with Slack to project manage tasks. 


---

# 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://medievalbook.gitbook.io/digitizing-medieval-archives/week-13/github-project-boards.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.