UPDATE: Automate development tasks by using GitHub Actions

[a-a-ron]

The purpose of this PR is to see how we can increase the completion rate and improve the user experience. Below is the August data for this module:

Module	Completion Rate	# completed / # started
Automate development tasks by using GitHub Actions	28.45%	468/1645

For reference: See the parent issue for context

Module file structure

Items to review for this module

We need to conduct a performance review on each of these modules to see how we can increase the completion rates, improve the user experience, and maintain the level of quality that we set for our learners.

Items for consideration

• Thoroughly review the module content for flow, narrative, and length
  • Review use of images, tables, and other visual elements
  • Does the content read like a doc or like a conversation guide?
  • Does the estimated time to complete each unit remain accurate?
• Review the introduction unit
  • Does it capture your attention?
  • Does it contain repetitive content from the course title page?
  • Do the learning objectives/scope align with the content?
  • Does the target audience match the content?
  • Do we accurately describe the module and learning objectives? (Is it possible that learners start the course thinking it's one thing to find out it's another?)
• Review the module exercise
  • Does it work?
  • Does it enforce a learning objective?
  • How is it placed in the module? Should we move it around?
  • Do we need other exercises?
• Review the questions at the end of the module
  • Do the questions test on content taught in the module?
  • Do the questions follow best practices for item writing?

Estimated Work Effort

Task	Hours
Detailed module review	18 hours
Action items as identified from review	TBD

[camihmerhar]

Action Items For Each Module

• Thoroughly review the module content for flow, narrative, and length
  • Review use of images, tables, and other visual elements
    - I think there are a good amount of images and they all help in building context of what the learner should be directing their focus to.
  • Does the content read like a doc or like a conversation guide?
    - For the most part I believe it reads like a conversation guide. Pretty consistent use of 2nd person which I feel like personalizes the content. Paragraphs are short and concise, which feels colloquial.
• Review the introduction unit
  • Does it capture your attention?
    - I think the title captures both that GitHub Actions will be the center of the module and pulls in the learner with the automation piece of the title and descriptions.
  • Do the learning objectives/scope align with the content?
    - Yes! Although the launch page learning objectives are missing one.
  • Does the target audience match the content?
    - Aside from the first 2 subunits in the first unit, I think everything else seems in place.
  • Do we accurately describe the module and learning objectives? (Is it possible that learners start the course thinking it's one thing to find out it's another?)
    - I think the title captures both that GitHub Actions will be the center of the module and pulls in the learner with the automation piece of the title and descriptions.
• Review the module exercise
  • Does it work?
    - Yes!
  • Does it enforce a learning objective?
    - 100%
  • How is it placed in the module? Should we move it around?
    - I think its perfect where it is.
  • Do we need other exercises?
    - I don’t believe so
• Review the questions at the end of the module
  • Do the questions test on content taught in the module?
    - Yes, I believe so
  • Do the questions follow best practices for item writing?
    - I believe so