✍️ @Saumil's Blog about open-source-mentorship HOT 7 OPEN

I think it's great that you're writing on something directly from your experience on the project. You may want to consider streamlining the focus of your blog. By that I mean, focus on one problem that you can teach the user about, but don't make it specific to Amplify contributors. No need to give a comprehensive introduction for Amplify or get into detail about setting up Codespaces. Definitely feel free to use the context of Amplify.

For example, the blog can center around the broader instruction of how to use the LOB API to customize a form for a letter or campaign and use your word limit to dive into that topic using examples from your experience working on Amplify. Hopefully that makes sense.

from open-source-mentorship.

Blog Outline

Audience: Anyone interested in learning about onboarding flow, API ecosystem and PostgreSQL.

Goal: Demo for people to follow and learn. Will include code snippets.

Title: Update letter using LOB API and PostgreSQL.
Issue #183, #371

Introduction:

• Introduction for Amplify platform
• What is LOB API?
  • Include brief introduction.
• What is PostgreSQL?
  • How is it connected with LOB API.
• How to onboard new issues to Amplify platform?
  • Give brief intro about amplify platform
  • Discuss how to use LOB API to customize a form for a letter
• How is LOB API connected to the entire workflow?
• What other tools you might need?

Body:

• Setup environment using Codespaces
• Lookup the data in tables in PostgreSQL
• Request data using LOB API
  • Consider using Postman to make the request
• Add merge variable to createLetter object in LOB API
• Updating API ecosystem and database (PostgreSQL)
• Encryption
• Tests

Conclusion:

• Summary

Next Steps:

Resources

• Amplify platform
• LOB API
• PostgreSQL

from open-source-mentorship.

Thanks Naj for sharing your feedback. I will incorporate your suggestions going forward. Also, adding the link to the google doc for my blog which is still a work in progress: https://docs.google.com/document/d/1Nw_dzesESQD6BLqvHk58JPfcdVhNAutZTa6MqU_EQzU/edit#heading=h.qcw1ux3m87yc. I will add the draft ready label as soon as I make good progress on this.

from open-source-mentorship.

@SAUMILDHANKAR you should have access now! Lmk if it's not working. Also be sure to fill out the doc with a rough draft. Focus on getting the intro and the body done, doesn't need to be perfect!

from open-source-mentorship.

@unnamedrd Thanks for sharing the access. I have added more information to my rough draft with steps that I am planning to complete. I will update it as I learn more. Apologies for the delay.

from open-source-mentorship.

@SAUMILDHANKAR Thank you! Remember to add the "draft ready" tag!

from open-source-mentorship.

@unnamedrd Hi Naj, sorry I missed the deadline. I just finished adding information to my blog so it meets some more requirements. I would like to add the "draft ready" tag now, but the setting to add label appears to be disabled for my issue currently. During pair programming session, I was removed and added back to the org (for testing purposes by Param), so not sure if that might impact the setting here. Look forward to hearing from you and thank you.

from open-source-mentorship.