> For the complete documentation index, see [llms.txt](https://www.pmguidebook.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pmguidebook.com/guidebook/contribute.md).

# Contribute

This guide is free and open source. It was been written as other methodologies and approaches proved successful. As such, it's in everyones best interest for this to be a living document that is improved and updated regularly.

**How to Contribute:**

### 1. Edit Content Directly

#### a. Experienced with GitHub

If you're familiar with Github, feel free to open a Pull Request (PR) in any way you see fit.\
⇒ [**View Repo**](https://github.com/markthepixel/pmguidebook)**.**

#### b. Edit in GitHub

If you see something you think should be changed, please click the "**Edit in GitHub**" on any of the PM Guidebook page.

Through the power of GitHub, anyone can make changes:

* Click on the "Edit on GitHub" link on the related page.
* You will need to log in with your GitHub account, or create one if you don’t have one.
* Click on the pencil icon **Edit this file** in the top right corner
* Make your changes. Note: the website is written in markdown.
* Click **Commit changes…**
* By default, you will be asked to **Create a new branch for this commit and start a pull request**.
* Type in a little note explaining what you have changed and why then click **Propose changes**.
* This will create a **Pull Request** which someone will review.
* Thanks very much!!!

### 2. Request Content

If you're not familiar with editing in Github or Markdown, you can still contribute by creating an "issue" (a ticket, idea, suggestion) in GitHub.

You can think of this as similar as writing a Jira or Linear ticket. You will need a free Github account.

[**Raise an Issue / Make a Suggestion**](https://github.com/markthepixel/pmguidebook/issues)**.**

### 3. Consider Donating

And, if you find this guide helpful, please [consider donating](https://donate.stripe.com/5kAbK3bqOeekgqkaEI) – This guide was a labor of love with the goal of being open source and an ever evolving, living document.

That being said, we poured hundreds of hours into this guide, therefore donations are appreciated.

### 4. Favorite on GitHub

If you'd like to show some <mark style="color:red;">love</mark>, please consider **starring the repo** on Github ⇒ [**View Repo**](https://github.com/markthepixel/pmguidebook)**.**

**Thank you** :relaxed:


---

# 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://www.pmguidebook.com/guidebook/contribute.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.
