Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Public Documentation #7

Open
0xLeif opened this issue Oct 10, 2023 · 5 comments
Open

Add Public Documentation #7

0xLeif opened this issue Oct 10, 2023 · 5 comments
Assignees
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@0xLeif
Copy link
Member

0xLeif commented Oct 10, 2023

We need to add comprehensive documentation for all public APIs throughout the project. This documentation should include clear and detailed explanations of the APIs, their input parameters, expected output, and any additional information that would assist developers in utilizing the APIs effectively.

@0xLeif 0xLeif added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Oct 10, 2023
@bellatrick
Copy link
Contributor

Hi. @0xLeif I would like to work on this issue. Please let me know if this task is still open and if yes, could you please point me to how to get started. Thanks!

@0xLeif
Copy link
Member Author

0xLeif commented Jan 8, 2024

Hey @bellatrick! Thank you for your interest in this project! For the documentation, we really only need to document anything that is public. There is a folder under source called public that should contain all of the objects that need documentation.

I think it would be best to start with one file and get a Pull Request up for that. Then you could do multiple files next or still do them one by one.

Let me know if you have any questions!

@bellatrick
Copy link
Contributor

Hey @bellatrick! Thank you for your interest in this project! For the documentation, we really only need to document anything that is public. There is a folder under source called public that should contain all of the objects that need documentation.

I think it would be best to start with one file and get a Pull Request up for that. Then you could do multiple files next or still do them one by one.

Let me know if you have any questions!

Sounds good. Do you want the documentation to be written in the form of inline comments in the code, or should a separate markdown file be created for each file?

@0xLeif
Copy link
Member Author

0xLeif commented Jan 8, 2024

@bellatrick preferably it would be best to have inline documentation at the minimum as it will use DocC to compile and upload the documentation to GitHub pages. After we have inline code documentation we could make separate files or a wiki for more information or documentation. Examples are welcome too for the inline documentation or readme.

@bellatrick
Copy link
Contributor

@bellatrick preferably it would be best to have inline documentation at the minimum as it will use DocC to compile and upload the documentation to GitHub pages. After we have inline code documentation we could make separate files or a wiki for more information or documentation. Examples are welcome too for the inline documentation or readme.

Alright got it. Will get started with the inline documentation. I'll let you know if I have questions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants