✍️ @Alex-is-Gonzalez Blog

[Alex-is-Gonzalez]

Outline Below Ready For Review

Title: How to Welcome first-time contributors to your repo and why it is important to do so

• What is a Welcome Message?
• Why use Welcome Messages?
• How to create Welcome Message?
• What is Github App?
• Configure yml
• Testing
• Summary and call to action

To Do: when you complete the requirements, add "outline ready" label on your issue

• [ X] Identify your topic from one of the PRs approved (Getting started with Actions #457)
• [X ] Outlining bullet points of blog roadmap
• [ X]s your blog a List, Survey, or demo? (Demo)
• [ X] Which Visuals or Diagram or Code snippets will you add (yml code snippets )
• [ X] References to resources (ref to GitHub actions, maybe additional resources to learn yml?)

Timeline:

• 📋 Week 4: Create an outline by 3/2
• 📰 Week 7: Rough draft due by 3/16
  • Mentor reviews by 3/30
• Week 9: Final version due 4/7

To Do: when you complete the requirements, add "outline ready" label on your issue

• [ X] Identify your topic from one of the PRs approved (Getting started with Actions #457)
• [X ] Outlining bullet points of blog roadmap
• [ ]X Is your blog a List, Survey, or demo? (Demo)
• [ X] Which Visuals or Diagram or Code snippets will you add (yml code snippets )
• [ X] References to resources (ref to GitHub actions, maybe additional resources to learn yml?)

📰 Blog Rough draft: Format into a google doc

Questions to answer across draft

• Why is this helpful for a reader?
• What problem does this help them solve?
• What kind of experience should the reader have or that you will provide so they’re up to speed
• What larger problem is this solving?
• Were there other ways of solving this problem - what made you choose the one that you did?
• What were the positive tradeoffs? (Did it save time? Save hours? Was more secure?)
• What is the best way to present the content (i.e. code snippets, graphics) ?
• What additional resources can they provide the reader if they want more information?
• Is there a call to action?

To do: when you complete the requirements, add "draft ready" label on your issue

• [ ] intro paragraph
• [ ] context of Amplify
• [ ] paragraph on problem
• [ ] paragrph compare your solution
• [ ] paragraph impact your solution
• [ ] Less than 600 words
• [ ] Drop link to your google doc (with permissions for edits) in review issue

[unnamedrd]

@Alex-is-Gonzalez did you create a welcome message for Amplify repo? The outline is super clear and concise, but I wasn't sure if this was indicative of something that you worked on.

[Alex-is-Gonzalez]

I did,I worked on it last week and created the PR. I'm working on getting it approved at the moment and got really good feed back on the PR!

[unnamedrd]

Perfect, continue!

[Alex-is-Gonzalez]

Here is the link to my Google Doc!

https://docs.google.com/document/d/1H-QZfzQt1IoccBy5OhT_iGx6IKyxvb1Z6t0t1Fhn_tE/edit?usp=sharing

[unnamedrd]

@Alex-is-Gonzalez thanks for getting this done! You might have to change permissions on the doc so that anyone with the link can view. I'm not able to see it. :-)

[Alex-is-Gonzalez]

@unnamedrd My apologies, I am a little rusty with Google Docs. I updated the permission and here is the updated link! https://docs.google.com/document/d/1H-QZfzQt1IoccBy5OhT_iGx6IKyxvb1Z6t0t1Fhn_tE/edit?usp=sharing

[GreCodes]

Hola Alex,

I really enjoyed reading the blog. Very interesting info!

I have left "a couple" of comments in the Docs document.

These are only my suggestions. I work in Support, and we use names of GitHub products all the time :D

I will continue on Monday because my brain is not working now, and it's Easter in Denmark.

Take care! Grecia

[Alex-is-Gonzalez]

@GreCodes, I am very appreciative of the feedback you have provided for my rough draft! I am excited to rework this draft with your notes! Many Thanks, Alex!