> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/my-profile/showcase-your-maintainer-badges-in-lfx-now/what-do-i-have-to-do-as-a-project-administrator.md).
# What do I have to do as a Project Administrator?
### 1. **Ensure that your maintainer list is up to date in community management.**
1. In Community Management, mark your project’s maintainers as a maintainer by selecting the 3 dots to the right and selecting **Add Maintainer** Tag.
Maintainer's badges
2\. The maintainer tag should now be shown in the Community Management dashboard.
Maintainer on CM
### 2. Ensure you have issued your maintainers a Credly maintainer badge
{% hint style="info" %}
Reach out to **Craig Ross** at,`ccr@linuxfoundation.org` and we can assist projects with designing their own Credly Badges.
{% endhint %}
The following template mock-ups are available for project maintainers:
Maintainer templates
### 3. Congratulations!! You are all set
Once your maintainers are identified in Community Management and you have issued your maintainers a badge via Credly.
---
# 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.linuxfoundation.org/lfx/my-profile/showcase-your-maintainer-badges-in-lfx-now/what-do-i-have-to-do-as-a-project-administrator.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.
