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

A Comprehensive Documentation for BitcoinJs-Lib. #2048

Closed
Muniru0 opened this issue Feb 27, 2024 · 2 comments
Closed

A Comprehensive Documentation for BitcoinJs-Lib. #2048

Muniru0 opened this issue Feb 27, 2024 · 2 comments

Comments

@Muniru0
Copy link

Muniru0 commented Feb 27, 2024

Bitcoinjs-lib though a fanstastic piece of work from it's active and passionate contributors currently lack documentation. This make's it extremely difficult for new users (including my very self) to get started and for some existing users to fully utilize it's features. As such with this documentation I intend to provide a conprehensive , clear and user-friendly guidelines to the library. Covering aspects including Installation, Configuration , Usage examples , API reference and Troubleshooting common errors.

Work Scope:

  1. Installation Process: Steps involved in the installation and use of the library in different environments.
  2. Get Started Tutorial : A guide that will help users to perform simple tasks with the library in minutes.
  3. Examples : Sequence of examples to illustrate the library's common use cases and showcasing its capabilities and effective usage.
  4. Short Descriptions: Short descriptions of the various functions and their uses within the library.
  5. Troubleshooting: Offer solutions to common errors associated with the library.

All the documentation will be written in Markdown and organized with a docs directory in the repository.

@junderw
Copy link
Member

junderw commented Feb 27, 2024

We have 3 in the README.

Closing in favor of #1986

Feel free to help review and/or build upon that PR.

I generally agree with the ideas behind your sections, but it must be done in a way that minimizes duplication of work. If someone modifies code, they shouldn't have to go searching for 7 different places in the docs that reference that code to modify. It should all be in a comment next to the area they modified. This is why something like Rust's rustdoc is so great, and it seems like #1986 utilizes some tooling to reduce the need for manually syncing a bunch of docs with the code.

@junderw junderw closed this as completed Feb 27, 2024
@Muniru0
Copy link
Author

Muniru0 commented Feb 28, 2024

Okay. Sure.

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

No branches or pull requests

2 participants