Multicurrency Wallet Transfer Final Submission#16
Multicurrency Wallet Transfer Final Submission#16EOEboh wants to merge 2 commits intoWriteTech-Hub:mainfrom
Conversation
|
Hi @EOEboh, Everything looks good, thank you! 🙌🏾 |
There was a problem hiding this comment.
Hi @EOEboh. Thank you so much for working on this.
Your tutorial has a great structure, flows well, and is very clear and beginner-friendly. The only thing missing is a short section on how to handle common errors your readers might encounter. Once you add that, your PR should be ready to merge!
OfficialJhimmy
left a comment
There was a problem hiding this comment.
Hi @EOEboh , excellent work on this tutorial! I really enjoyed going through it. The structure is clean, the formatting is polished, and you’ve done a great job balancing Postman and cURL so different types of developers can follow along. Your use of screenshots, code samples, and asides makes it very beginner-friendly. It’s no surprise I scored this high. It’s one of the most complete entries I’ve reviewed.
That said, I do have a few suggestions that can make an already strong tutorial even better:
-
Structure and Flow
• The step-by-step breakdown is well done, but a couple of sections could use slightly smoother transitions. For example, after creating a wallet, you could briefly explain how the wallet ID connects to the transfer step. This makes the flow feel more natural and less like jumping from one action to the next.
• The “Recommended Next Steps” section is a nice touch. You might consider adding a short sentence before the links that ties back to the tutorial, like: “Now that you can make transfers, here’s where you can go deeper…” -
Clarity and Explanation
• Some terms, like “multi-currency wallet,” are used right away without much explanation. Adding one or two sentences at the start of the guide about what this type of wallet is and why it’s useful would give beginners more context.
• In the cURL examples, you could briefly explain each flag (-X, -H, -d) so beginners don’t just copy-paste but actually understand what’s happening. -
Writing Best Practices
• A few sentences are on the longer side and could be broken up for easier reading. For instance, the line “Open the ‘MultiCurrency Wallet’ folder in the left sidebar and navigate to the…” could be split into two shorter instructions to make scanning easier.
• Watch for small grammar tweaks, like capitalizing consistently (for example: “Create A Test Wallet” → “Create a Test Wallet”). Little details like this make the guide look even more polished. -
User Experience
• The troubleshooting section is really helpful. To make it even more practical, you could add one or two short example scenarios (e.g., “If you see a 401 Unauthorized error after following this guide, double-check that your Postman environment is correctly set to use your API key”). That way, readers can immediately connect the error messages to real-world debugging.
Overall, this is an excellent tutorial, clear, detailed, and very close to production-level documentation. With just a bit more context for beginners and some fine-tuning around flow and readability, it could easily serve as an official developer guide. Fantastic job! 🚀
This is my final submission of my work.
Multi-currency wallet transfereditions/01-chimoney/submissionsfolderPlease let me know if you need me to make any corrections as regards the submission.
@phyleria @adebayoileri