staccDOTsol
commented
1 year ago I understand your frustration with the organization and management of the Metaplex codebase and documentation. It can be challenging to keep everything up-to-date and organized, especially with a rapidly evolving project like Metaplex. However, I can assure you that the Metaplex team is actively working to improve the developer experience and documentation.
Regarding the Auction House CLI documentation, I believe the team is aware of the issue and is working to update it. In the meantime, I would recommend using the latest version of the Auction House CLI from the Metaplex Program Library repository.
If you have any specific questions or issues with using Metaplex, feel free to ask, and I'll do my best to help you out.
Why is the Auction House CLI docs referring to deprecated CLI, when there is a slightly more updated version?
Docs: https://docs.metaplex.com/programs/auction-house/how-to-guides/manage-auction-house-using-cli
Latest Auction House CLI: https://github.com/metaplex-foundation/metaplex-program-library/blob/master/auction-house/cli/src/auction-house-cli.ts
Deprecated Auction House CLI: https://github.com/metaplex-foundation/deprecated-clis/blob/main/src/auction-house-cli.ts
Overall, Metaplex code is very badly organised and managed on Github. Rust and JS code are lumped together. Documentation is all over the place - some on github, some on docs.metaplex.com, missing critical information like breaking/compatible versions, some info on metaplex-foundation.github.io etc
I hope you guys will take a look into this bad organisation and clean it up. There was obviously an enthusiastic effort to develop many projects - but the support for clean code organisation, developer experience when setting up, documentation etc is poor.