-
Notifications
You must be signed in to change notification settings - Fork 13
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
Detailed documentation #10
Comments
Can I work on this issue? I would like to add additional documentation |
Hi @AbhijithGanesh, |
I'll add additional docs , since only the project s original contributors can write docs, I'll keep it in mind and do what I can, thank you for clarifying. I am really looking forward to contribute and I felt the documentation would be a good place to start. |
I am looking forward to your contribution. As I said, if you have any questions, feel free to contact me or create a discussion. |
One more thing: I am working on release
It supposes to be finished yesterday (I am fixing the test coverage right now). So, there will be some changes in the codebase in the next few hours. This issue should not be affected, but anyway I think you should know. |
I will not be writing docs for another 12 hours(I work on IST) so yeah. I will start once the release is done if that suits the project the best |
#30 is merged, no bigger changes are planned for the next few days, so there should not be any potential conflicts |
Documentation is essential part of every project (in my opinion, it's not enough to keep full example in README file - which is starting to be quite long).
My idea is to create GitHub pages using mkdocs and mkdocs-material (like in duckql-python repository) with:
The text was updated successfully, but these errors were encountered: