Hello, thank you for reading our contributing guide. You can find useful information here on how to submit a Discord API library and any other topic that relates to it.
- Document as many libraries as possible
- Make it easy for readers to find what language and library they want to use
- Must be open-source with a known Git URL (GitHub, GitLab, BitBucket, etc).
- Must be written in a known language. Esolangs are not allowed.
- Must have a working prototype. It does not need to be "production" ready, but we need to know if this project is legitimate or not.
When formatting a language or a library, please make sure that they are sorted alphabetically. This makes it easier for people to find what they're looking for.
### [language](language_official_website "language")
If you can't find the language's official website, try linking to a Wikipedia article instead. If you can't find that either, then you may exclude the hyperlink.
* [display_name](lib_repo_url "lib_repo_name")
display_name
- The library's preferred name, or justlib_repo_name
if there is nonelib_repo_url
- The URL to the library's repolib_repo_name
- Strictly the name of the repo that hosts the library's code
Libraries that are discontinued are marked with strikethrough. Some libraries are marked as discontinued for historical purposes. If you believe that a library is discontinued, feel free to open a PR.