Skip to content

Latest commit

 

History

History
114 lines (66 loc) · 7.04 KB

technical-onboarding-instructions.md

File metadata and controls

114 lines (66 loc) · 7.04 KB

🚀 Technical Onboarding Instructions

📋 Section 0: Prerequisites

To get started, complete the following items if you haven’t already:

By completing this Technical Onboarding Process, you will:

  • 🌟 Become trained on the use of GitHub including GitHub Codespaces and GitHub Copilot
  • 📈 Complete one of the requirements for Student Ambassador program advancement
  • 🌐 Create your very own personalized Portfolio website
  • 🏆 Get a certificate that will recognize your new technical abilities!

For any questions or issues, reference the Technical Onboarding GitHub Discussions and engage with other Ambassadors.

Note: Technical Onboarding was updated on April 18, 2023. See this Discussions post for more details.

🌐 Section 1: Create your own JavaScript Portfolio Site with GitHub Codespaces and Copilot

Why do this section?

Microsoft Cloud Advocates have created a template GitHub repository for this Technical Onboarding experience. This template includes your own version of some starter code and a fully set up development environment in GitHub Codespaces.

In this exercise, you will:

  1. Set up your GitHub Codespace
  2. Create your Portfolio site
  3. Customize your site with GitHub Copilot
  4. Deploy your site to the cloud with Azure Static Web Apps

A static web app (SWA) is a site built with JavaScript, HTML, CSS, and other tools. SWAs are becoming increasingly common. Using Azure Static Web Apps will allow you to quickly post your Portfolio site to the world. Learn more about Static Web Apps in this Microsoft Learn module.

Find the template repository and instructions to create your own Portfolio site here.

💡 Section 2: Complete Your Next Step in GitHub Training with Reviewing Pull Requests

Why do this section?

By completing this Microsoft Learn Module, you will learn the foundation of collaboration on GitHub – one of the most popular platforms for collaborative development.

  1. Navigate to the "Manage repository changes by using pull requests on GitHub" Learn module.
  2. Complete all 5 units, including the exercise on GitHub in unit 3 and the Knowledge Check in unit 4.
  3. Navigate back to the Learn module page to confirm you have completed all steps of the module.

Module Completion

  1. Confirm that the pull request you have been interacting with has been merged on GitHub.

Pull Request Merged

✅ Section 3: Submit your onboarding details, feedback, and get your certificate of completion

Congratulations! You've made it to the end! The last step is to fill out the Onboarding Completion Form (using your @studentambassadors account) to provide a few details about you, your Profile site, the link to your final pull requests from the GitHub Learn module, and your experience with this process.

You will be advanced to the Beta milestone (once you have also hosted an event or actively participated in a social impact league project) after a Program Team member verifies that:

  1. Your Student Ambassador Profile is updated with your GitHub Account.
  2. Your Portfolio site is complete and deployed with Azure Static Web Apps.
  3. Your GitHub Learn module is complete.

Thank you for completing this exercise!

🎥 Optional: Creating an Azure Static Web App from an existing GitHub repository

Video demonstration

If you would like to create an Azure Static Web App from an existing GitHub repository on your GitHub account, you can follow these steps:

  1. Navigate to Azure and log in.
  2. Search for Static Web Apps and choose Static Web Apps.

Search Static Web Apps

  1. Click 'Create'.

Create Static Web App

  1. Choose your Azure subscription, create a new resource group, and give it a name.

Create Resource Group

  1. Name your app, choose Free for the plan type, and select a location close to you.

Plan Type

  1. Under deployment details, choose GitHub and 'Sign in with GitHub'.
  2. Choose your organization (your account) and your repository, leave Build presets blank, and click 'Review + create'.

Review + Create

  1. Choose React as your Build Preset.

Change Build Preset

  1. Change the output location from the default build to dist.

Change Build Location

  1. Click 'Go to Resource' once it has finished deploying, and you should have a link to visit your website.

Go to Resource Deployed Site

  1. Check your repository to see that your action has been created. Once it has finished running, refresh the link you visited and your site should be deployed.

Repository Action