Documentation Gaps - Interested in Contributing

[0xherve]

Hello Everyone,
I was following the guide to create a Token with Metadata, and I appreciated how it required fewer lines of code and abstracted many functions in normal SPL token creation projects.

However, I noticed that most functions are not documented, and it is hard to find any guides on how to use them. For example, in Creating a transaction that creates a token, we are recommended to use the getCreateTokenInstructions() to abstract the instruction building. I searched for guides on how to use the instruction builder and couldn't find any information in the documentation or online. I used it by reading the code myself and following the arguments that the function expects.

I intended to fork this repository and add a guide to the instruction builder because I couldn't find it anywhere. According to the contribution guidelines, you need to have the issue approved first before making a PR. When I looked at the issue opening page, it appeared to be dedicated to technical issues.

There may be a reason for the way the guides are written. My questions are:

• Should I open an issue to propose documentation contributions, or is there a different process for docs?
• Is there a reason for the current guide format that I should be aware of?