Omer: Workflows, 1

[omerjava]

my fork of the exercises repo

Study Plan

• Command Line Interface (CLI)
• Visual Studio Code (VSCode)
• Code Quality
• READMEs
• Git and GitHub
• Collaborating on GitHub
• GitHub Actions
• DevTools and the DOM

Learning Objectives

• 🥚 Git Remote/Local Connection: You can create a local git repository, commit changes, connect a remote repository and push changes to the remote.
• 🥚 Linting: what is it? why does it matter? can write CSS & Markdown that passes a linting check
• 🥚 Git Branching Workflow: You can manage your work locally using branches: pull remote changes -> create a new branch -> push the branch to the remote repository -> open a PR with passing Continuous Integration checks -> merge changes to main/master.
• 🥚 Command Line Interface (CLI): You can navigate a directory, manage folders/files, make small changes in a file using nano/vim, and much more (list coming soon).
• 🥚 NPM: You can install npm dependencies and use npm scripts (dev, lint and format)
• 🥚 Browser + DevTools: You can open a local HTML/CSS project in your browser and inspect the elements, emulate different devices, and inspect the source
• 🥚 File Extensions: You can identify all of the languages covered at HYF and give the correct file extension. (You don't need to know the languages, just recognize them!)
• 🥚 VSCode: You can complete these workflows in VScode, and can use keyboard shortcuts when possible:
  Opening a repository in a new window
  Opening the repository in VSCode terminal
  Adding a new file
  Adding a new folder
  Deleting a file
  Deleting a folder
  Previewing a Markdown File
  Opening an HTML file with the LiveServer extension
  Viewing the repository's git history with Git Graph extension
• 🐣 Touch Typing: You can write a README without looking at your keyboard to find any letters, numbers or special characters. (slowly is ok!)
• 🐣 User Stories: Given pictures of a website, you can describe the page with user stories: As a type of user I can do something so that something good happens.
• 🐣 Planning and Collaborating: You can comfortably complete these steps of the Planning and Collaborating process described in the Student Guidebook:
  Repository Setup
  Project Definition
  Communication Plan
  Backlog
  Wireframe
• 🐣 Development Strategies: You can work as a group to follow the steps in a development strategy and reconstruct a web page when the code is provided.
• 🐣 Atomic Commits & Feature Branches: You can organize your development process using small single-purpose commits on feature branches. You will learn to develop each of these features on a separate branch and to merge it to main/master on GitHub when the feature is complete.
• 🐣 GitHub: You can create new repositories, turn on GitHub Pages, connect the repository to your local computer, push/pull different branches, and pass Continuous Integration checks for code linting and validation.
• 🐥 GitHub Collaboration: You can collaborate in a single repository and contribute a markdown file. This includes: creating a new branch, creating and editing a file on that branch, sending a pull request, addressing any requested changes, and reviewing+merging a classmate's pull request. (this can all be done from the GitHub UI)
• 🐥 Code Review: You can use a code review checklist in a Pull Request to check a classmates code before merging.