> For the complete documentation index, see [llms.txt](https://handbook.openguild.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.openguild.wtf/general-information/guidelines/developers-guideline.md).

# Developers Guideline

So you're here to contribute to OpenGuild’s ecosystem as a developer —**amazing!** Whether you're submitting code, writing an article, or joining a GitHub discussion, your contribution helps shape the open, community-driven future we believe in.

Let’s walk you through how to get involved and make your first impact.

#### 🔓 Who Owns the Work You Submit?

Great question! OpenGuild is a **community-owned initiative**—everything you contribute is part of a shared resource for builders in the Polkadot ecosystem.\
Before you contribute, **please read** our asset and IP usage notes:\
👉 [Contributor Ownership & Licensing](https://github.com/orgs/openguild-labs/discussions/9)

### Workflow for public contribution

* [x] Fork a repository - <https://github.com/orgs/openguild-labs/repositories>
* [x] Create a branch for your commits
* [x] Submit your changes to the branch
* [x] Create a PR between a sub-branch with the `main` or `master` branch in the parent repository
* [x] Wait for review from the core contributors

### How to Make a Contribution?

#### Articles & Blogs

Please find the template for this type of contribution below:

```
## Author
<!--- Provide information about the author in this section following the below structure -->
Example of the author metadata (only required for new authors):

---
name: Tin Chung
avatar: /static/images/tin-chung.jpeg
occupation: DevRel - Polkadot SEA
email: cqtin0903@gmail.com
twitter: https://twitter.com/chungquantin
linkedin: https://www.linkedin.com/in/tin-chung-36297a167/
github: https://github.com/chungquantin
---

## Description
<!--- Describe your changes in detail -->

## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->

## Screenshots (if appropriate):

```

OpenGuild.xyz website operates as an open blog, welcoming contributions from the public. Currently, we don't have a dedicated workflow or a sleek WYSIWYG editor on **openguild.wtf**. However, this doesn't hinder you from sharing your content—you can achieve this through a Github Pull Request (PR).

Refer to this [Markdown file writing tutorial](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) for guidance. Following these conventions ensures the continued quality of blog posts on our platform.

#### Open-source projects

Please find the contribution guidelines for the project that you are interested in because each project is maintained by different core contributors. They might have a different approach for project management at the moment.


---

# 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://handbook.openguild.wtf/general-information/guidelines/developers-guideline.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.