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

Official Docs Contribution #10

Open
heywhy opened this issue Jan 9, 2022 · 6 comments
Open

Official Docs Contribution #10

heywhy opened this issue Jan 9, 2022 · 6 comments
Projects

Comments

@heywhy
Copy link
Owner

heywhy commented Jan 9, 2022

I will be happy to have anyone contribute to the official docs for the project. Having comprehensive docs at hex.pm is desired, so modules need to be updated.

@TwistingTwists
Copy link

Hey.
This is a great project!
I have used - Meilisearch previously - a similar project in Rust.

Bringing a similar project to Elixir, brings me delight.

I am willing to contribute to the docs. Can you point me where to start?

@heywhy
Copy link
Owner Author

heywhy commented Jan 9, 2022

@TwistingTwists I'm glad to have you contribute to the docs or any other part of the project. To get started, I will suggest you start by updating the documentation (including examples where applicable) for each module based on it behavior or logic contained in it. Do not hesitate to reach out (via email) in case you are unsure of what a module does or how it contributes to the project. Note that you will need to familiarize yourself with the internal workings of the library so as to help you write more informative documentation.

I hope my suggestion isn't vague, do let me know if you have a better approach that will get us going with the documentation.

Thank you for wanting to contribute to the project, I really appreciate it.

@heywhy heywhy added this to To do in Elasticlunr Jan 9, 2022
@drannex42
Copy link

drannex42 commented Jan 9, 2022

+1 on Docs, but also the code should be commented! I read/write in Elixir but some of it was a bit hard to follow (not too hard, but comments are always great!).

Using the @doc macro would aid in inline understanding (and future proofing) the code, and help with adding some quick and simple documentation.

Thanks for your work on this @heywhy will def be using this soon!

@heywhy
Copy link
Owner Author

heywhy commented Jan 9, 2022

@drannex42 thank you for the feedback. your suggestion is what we’re working on already, module docs will be coming in before any other external docs.

Actually, the goal is to have an informational documentation on hexdocs.

@drannex42
Copy link

drannex42 commented Jan 9, 2022

Great to hear! Happy that it's already underway. Again, really great project you have here (I did not see that you were the one who posted the issue, thought it was someone else - my apologies!).

@heywhy
Copy link
Owner Author

heywhy commented Jan 9, 2022

No worries. I posted the issue myself to solicit for contributors to help.😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants