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.

Group members:
@Darin-Hamouda
@Nefn-Lakhouj
@krakla
@omerjava
@mniyomukiza

• repo
• many small, well-named commits
• a nice README
• one well-named file per person
• one pull requests for each group member
  • linting checks pass
  • code review checklist is complete
  • the reviewer merged the code

add entry to ./snippets describing a useful bit of code

Please leave your questions over this module under here for tonight's check-in review call. The assigned coach will go through your questions and answer them on the review call . Follow the instructions under,

1. I Need Help With:

2. what I have done to fix it:

3. What went well?

4. What went less well?

Leave a comment with these two things:

1. A summary of your week using only emojis
2. Something you'd like to share, anything goes! (within respect)

emoji cheat sheet

Learning Objectives

• Collaborating: You can effectively work in a group:
• 🥚 You can work with your group mates to agree on a communication plan.
• 🥚 As a group you can define project constraints by discussing your strength's, weaknesses and context.
• 🥚 During development you can ask your group for help when you need it using the agreed channels of communication.-
• 🥚 During development you communicate any changes in your personal situation that will impact the group.
• 🥚 When the project is finished your group can write a retrospective including concrete steps to make sure the next project goes smoother.Planning:
• You can work in a group to plan a multi-page website written with HTML & CSS:
• 🥚 You can understand a web page's users by creating user personas.
• 🥚 You can work together to write a backlog of user stories for your personas, organized by priority (must, should, could)
• 🥚 You can work together to create a simple wireframe with pencil+paper and a basic drawing app like Excalidraw
• 🐣 You can work together to write a development strategy for must-have user stories.
• 🐣 You can work together to convert a development strategy into issues on a project board organized with labels and milestones.Developing:
• Once the project board is set up you can work with your group to develop the website:
• 🥚 You can claim a task and manage your progress using the project board columns.
• 🥚 Your group can use issues to discuss and agree on project changes once development has begun.
• 🥚 You can use the help-wanted label to ask for help, and to find issues that need your help.
• 🥚 You can manage a separate branch with your work for each issue task.
• 🥚 You can create a PR that passes CI checks when your task is finished, then assign someone to review it.
• 🐣 You can review a group member's PR and conduct a code review using the project's checklist.

my fork of the exercises repo: workflows-week1-group-5
materials-workflows
exercises repo: workflows-week2-pc-group-5

Study Plan

Module02 workflows-Suggested Study

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

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.

Week 1

• I have pushed my progress to my fork of exercises repo

Check-In

I Need Help With:

• npm run spell-check conflict: code ELIFECYCLE
• pull request conflict

What went well?

• create a new issue
• create a pull request

What went less well?

• tracking/manage my issue
• tracking a issue from someone other's(if I have the same question/problem)

Lessons Learned

• git command
• npm command

Sunday Prep Work

• My retrospective for workflow-module/week-2

Check-In

I Need Help With:
I need more time to practice CSS and tp focus more.

What went well?
Understanding what is the required things to do and move through it smoothly. Getting more used to use VS codde and github with no problems also with npm.

What went less well?
Communication with group is difficult since there is no meetings because of conflicts in availability.
Also, I'm behind schedule as I was sick this week

Lessons Learned
Need more practice with CSS, better to plan everything before start thinking with codes.

Learning Objectives

Collaborating: You can effectively work in a group

• You can work with your group mates to agree on a communication plan.
• As a group you can define project constraints by discussing your strength's, weaknesses and context.
• During development you can ask your group for help when you need it using the agreed channels of communication.
• During development you communicate any changes in your personal situation that will impact the group.
• When the project is finished your group can write a retrospective including concrete steps to make sure the next project goes smoother.

Planning: You can work in a group to plan a multi-page website written with HTML & CSS:

• You can understand a web page's users by creating user personas.
• You can work together to write a backlog of user stories for your personas, organized by priority (must, should, could)
• You can work together to create a simple wireframe with pencil+paper and a basic drawing app like Excalidraw
• You can work together to write a development strategy for must-have user stories.
• You can work together to convert a development strategy into issues on a project board organized with labels and milestones.

Developing: Once the project board is set up you can work with your group to develop the website:

• You can claim a task and manage your progress using the project board columns.
• Your group can use issues to discuss and agree on project changes once development has begun.
• You can use the help-wanted label to ask for help, and to find issues that need your help.
• You can manage a separate branch with your work for each issue task.
• You can create a PR that passes CI checks when your task is finished, then assign someone to review it.
• You can review a group member's PR and conduct a code review using the project's checklist.

---- BEGIN CHECK-IN TEMPLATE ----

Week X

• I have pushed my progress to repo Fantastic4-html-css

Check-In

I Need Help With: Lint issue in html, I can't seem to find the problem, also when in VS Code it detects no problems (see attachements)

What went well? Considering we are only two contributing at the moment I think we are following the assignment ok

What went less well? Me and my lint issues 👎

Lessons Learned: Read the issue before you ask for help

Sunday Prep Work

---- END CHECK-IN TEMPLATE ----

-->

my fork of the exercises repo

Study Plan

Week 3

• I have pushed my progress to my fork of exercises repo

Check-In

I Need Help With:

for now i want more work on css & html if there is more things to learn about it

What went well?

working as a real group everyone have a different time

What went less well?

make more zoom meeting as a team i just connect and talk with Eduardo he is the only one responding for me

Lessons Learned

i learn more about html and css and that was perfect for me i watch a loruki video and i found it vey helpful
i know that i have to work more and more but for now its good for me
i work on navigation bar i learned a lot but i have a problem with linting while i push but eduardo help me and fix it

my fork of the exercises repo

you will create ONE check-in issue per module

Suggested Study:

Command Line Interface (CLI)

[] relative vs. absolute paths
[] The Coding Train
[] Jesse Showalter
[] CLI games:
[] bashcrawl - clone & play
[] Terminus - online
[] iTerm - online
[] A huge cheat sheet

Visual Studio Code (VSCode):

[] academind VSC tutorial
[] shortcuts cheatsheet
[] The Coding Train
VSC Intro from VSC
[] tutorial step-through
[] get started
[] Tips for HTML/CSS/JS
Are you using Windows?
[] Windows Subsystem for Linux
[] WSL with VSCode
[] nvm command not found

Code Quality

[] formatting (all file types with prettier)
[] linting
[] CSS
[] markdown
[] validating HTML
[] spelling checks (will do once by automation, then by hand. automated spell checks are a little annoying)

READMEs

[] makeareadme.com
[] bulldogjob
[] meakaakka
[] awesome-README-templates

Git and GitHub

Git and GitHub for Poets
Learn to visualize what happens inside of Git with:
learngitbranching + a Video Guide
ohmygit - a git game
HYF/study
lab.github.com/githubtraining
first day on github
first week on github
prepare to use github
Getting Started with GitHub
Creating a GitHub Repository
Creating a local repo and push
and much more at hackyourfuture.github.io/study
lab.github.com:
First Day on GitHub
First Week on GitHub
The Net Ninja
git-it
Understand how to use Atomic Commits

Collaborating on GitHub

Adding collaborators to a repository
about code reviews
requesting a code review
Git Workflow for 2
Pull Requests
Git & GitHub for Poets
The Net Ninja: 11
linking PRs to Issues: reference 1, reference 2
closing Issues using keywords

GitHub Actions

For now you can think of Continuous Integration is a fancy way to say "automatically check your code before you merge". Your project repositories will all have CI scripts to help maintain a quality and consistent code base.
hint: remember to enable GitHub Actions in your repository!

DevTools and the DOM

How to inspect an element
inspecting-the-dom
Modify the DOM. (does the source change?)

Class Recordings

HYF modules are often updated, recordings from past classes may not match this gitbook
When sending a PR's with recording links please ...
Indicate which class you were teaching
Which week it was (if the module is more than 1 week)
a helpful title or description
How to inspect an element
inspecting-the-dom
Modify the DOM. (does the source change?)

Group members

• @ashenafykebede
• @denrique-alvarez
• @mohammedlouzon
• @Levaii
• @mauricemat

Learning objectives

• repo (with a complete README)
• live demo

planning

• communication plan
• constraints
• user personas
• backlog
• wireframe
• user Stories
• development strategy
• retrospective
• project board

my fork of the exercises repo

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!)
• Touch Typing: You can write a README without looking at your keyboard to find any letters, numbers or special characters. (slowly is ok!)
• 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
• 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 classmate's code before merging.

exercises repo: agile-group-3 week I
exercises repo week II and III

Study Plan (Suggested Study)

Curriculum
Study Book

• Agile Development
• Sprint Planning
• User Stories
• Website Planning
• Working Together
• Code Review
• HTML & CSS
• Agile is not Perfect
• Class Recordings

Learning Objectives

• Collaborating: You can effectively work in a group:
• 🥚 You can work with your group mates to agree on a communication plan.
• 🥚 As a group you can define project constraints by discussing your strength's, weaknesses and context.
• 🥚 During development you can ask your group for help when you need it using the agreed channels of communication.
• 🥚 During development you communicate any changes in your personal situation that will impact the group.
• 🥚 When the project is finished your group can write a retrospective including concrete steps to make sure the next project goes smoother.
• Planning: You can work in a group to plan a multi-page website written with HTML & CSS:
• 🥚 You can understand a web page's users by creating user personas.
• 🥚 You can work together to write a backlog of user stories for your personas, organized by priority (must, should, could)
• 🥚 You can work together to create a simple wireframe with pencil+paper and a basic drawing app like Excalidraw
• 🐣 You can work together to write a development strategy for must-have user stories.
• 🐣 You can work together to convert a development strategy into issues on a project board organized with labels and milestones.
• Developing: Once the project board is set up you can work with your group to develop the website:
• 🥚 You can claim a task and manage your progress using the project board columns.
• 🥚 Your group can use issues to discuss and agree on project changes once development has begun.
• 🥚 You can use the help-wanted label to ask for help, and to find issues that need your help.
• 🥚 You can manage a separate branch with your work for each issue task.
• 🥚 You can create a PR that passes CI checks when your task is finished, then assign someone to review it.
• 🐣 You can review a group member's PR and conduct a code review using the project's checklist.

my fork of the exercises repo

Study Plan

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.

my fork of the exercises repo

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 classmate's code before merging.

Week 1

• I have pushed my progress to my fork of exercises repo

Check-In

I Need Help With:

What went well?

• ssh key and syncing my account with VSCode.

What went less well?

Lessons Learned

• Branches creating.
• push and pull.

Sunday Prep Work

Study Plan

Week 1 Agile Development

• I have pushed my progress to (https://github.com/sannesofie/agile-group-3)

• Agile Development

• Sprint Planning

• User Stories

• Website Planning

• Working Together

• Code Review

• HTML & CSS

• Agile is not Perfect

• Class Recordings

Learning Objectives

• Collaborating: You can effectively work in a group:
• 🥚 You can work with your group mates to agree on a communication plan.
• 🥚 As a group you can define project constraints by discussing your strength's, weaknesses and context.
• 🥚 During development you can ask your group for help when you need it using the agreed channels of communication.
• 🥚 During development you communicate any changes in your personal situation that will impact the group.
• 🥚 When the project is finished your group can write a retrospective including concrete steps to make sure the next project goes smoother.
• Planning: You can work in a group to plan a multi-page website written with HTML & CSS:
• 🥚 You can understand a web page's users by creating user personas.
• 🥚 You can work together to write a backlog of user stories for your personas, organized by priority (must, should, could)
• 🥚 You can work together to create a simple wireframe with pencil+paper and a basic drawing app like Excalidraw
• 🐣 You can work together to write a development strategy for must-have user stories.
• 🐣 You can work together to convert a development strategy into issues on a project board organized with labels and milestones.
• Developing: Once the project board is set up you can work with your group to develop the website:
• 🥚 You can claim a task and manage your progress using the project board columns.
• 🥚 Your group can use issues to discuss and agree on project changes once development has begun.
• 🥚 You can use the help-wanted label to ask for help, and to find issues that need your help.
• 🥚 You can manage a separate branch with your work for each issue task.
• 🥚 You can create a PR that passes CI checks when your task is finished, then assign someone to review it.
• 🐣 You can review a group member's PR and conduct a code review using the project's checklist.

Group members

• @samedsay
• @tahminarasoli
• @AlinaTaoRao
• @Dawit-bit

A group repository to get to know each other and practice creating Issues and PRs

• repo
• many small, well-named commits
• a nice README
• one well-named file per person
• one pull requests for each group member
  • inting checks pass
  • code review checklist is complete
  • the reviewer merged the code

• repo (with a complete README)
• live demo
• /planning
  • communication plan
  • constraints
  • backlog
  • design
  • development strategy
  • retrospective
• project board

@AlinaTaoRao
@tahminarasoli
@samedsay

• repo (with a complete README)
• live demo
• /planning
  • communication plan
  • constraints
  • user personas (you need to write this!)
  • backlog
  • design
  • development strategy
  • retrospective
• project board

Leave a comment with these two things:

1. A summary of your week using only emojis
2. Something you'd like to share, anything goes! (within respect)

emoji cheat sheet

What went well?
getting started with Github, creating and cloning repos

What went less well?

• generating SSH key
• pushing and pulling requests
• Synchronise VSC with Github Desktop
• Install npm dependencies and use npm scripts

Lessons Learned

• Watch as many tutorials as I can
• Practice
• do not focus on one mistake and forget other work.

what you have done for Sunday Prep Work

my fork of the exercises repo: agile-group-3
materials agile-development

Study Plan (Suggested Study)

Curriculum
Study Book

• Agile Development
• Sprint Planning
• User Stories
• Website Planning
• Working Together
• Code Review
• HTML & CSS
• Agile is not Perfect
• Class Recordings

Learning Objectives

• Collaborating: You can effectively work in a group:
• 🥚 You can work with your group mates to agree on a communication plan.
• 🥚 As a group you can define project constraints by discussing your strength's, weaknesses and context.
• 🥚 During development you can ask your group for help when you need it using the agreed channels of communication.
• 🥚 During development you communicate any changes in your personal situation that will impact the group.
• 🥚 When the project is finished your group can write a retrospective including concrete steps to make sure the next project goes smoother.
• Planning: You can work in a group to plan a multi-page website written with HTML & CSS:
• 🥚 You can understand a web page's users by creating user personas.
• 🥚 You can work together to write a backlog of user stories for your personas, organized by priority (must, should, could)
• 🥚 You can work together to create a simple wireframe with pencil+paper and a basic drawing app like Excalidraw
• 🐣 You can work together to write a development strategy for must-have user stories.
• 🐣 You can work together to convert a development strategy into issues on a project board organized with labels and milestones.
• Developing: Once the project board is set up you can work with your group to develop the website:
• 🥚 You can claim a task and manage your progress using the project board columns.
• 🥚 Your group can use issues to discuss and agree on project changes once development has begun.
• 🥚 You can use the help-wanted label to ask for help, and to find issues that need your help.
• 🥚 You can manage a separate branch with your work for each issue task.
• 🥚 You can create a PR that passes CI checks when your task is finished, then assign someone to review it.
• 🐣 You can review a group member's PR and conduct a code review using the project's checklist.

Week 1

• I have pushed my progress to my fork of exercises repo: agile-group-3

Check-In

I Need Help With:

What went well?

What went less well?

Lessons Learned

Sunday Prep Work

Leave a comment with these two things:

1. A summary of your week using only emojis
2. Something you'd like to share, anything goes! (within respect)

emoji cheat sheet

Group 4 - Agile development Week 1

Group members

• Ashenafi
• Omer
• Zakaria
• Mervat
• Rupam
• Hans

• repo
• live demo
• /planning
  • communication plan
  • constraints
  • backlog
  • design
  • development strategy
  • retrospective
• project board

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.

The Code

The code you have a question about (it doesn't need to be your code!). This can
be shared a few ways:

• a snippet in the MD of your issue or
• a
  permalink
  or
• a gist

Best Understanding

Explain the situation:

• What does the code do
• What do you want it to do
• How do you think it works?
• What don't you understand about how it works?

Best Efforts

If this is your code and it has a bug, explain what you've tried so far:

• Include code
• Mention everything you tried, even if it seems silly to you
• What happened with each effort?
• What brought you closer?
• What brought you farther?

Helpful Links

Videos, articles, snippets, ... anything that helped you understand or make
progress on the problem.

Hopeful Links

Links that look like they should be helpful but you just can't put all the
pieces together.

Exercise repository (Week 1)

Learning Objectives (Week 1)

• 🥚 Git Remote/Local Connection: I can:
  • create a local git repository
  • commit changes
  • connect a remote repository
  • 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: I 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): I 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
  • use npm scripts (dev, lint and format)
• 🥚 Browser + DevTools: I can:
  • open a local HTML/CSS project in your browser
  • inspect the elements
  • emulate different devices
  • inspect the source
• 🥚 File Extensions: I 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: I 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: I can:
  • write a README without looking at my keyboard to find any letters, numbers or special characters. (slowly is ok!)

update npm-commands.md to include entry on .html validation

Group 2

Ahmed
Hans
Mervat
Zakaria
Aviv

Our Goal:

plan and create a working website in a group, following a Development Strategy.

• repo
• live demo
• /planning
  • communication plan
  • constraints
  • backlog
  • design
  • development strategy
  • retrospective
• project board

https://github.com/sannesofie/workflows

my fork of the exercises repo ???not sure what this means???

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.

Week 1

• I had some Terminal issues regarding setup
• I cloned lab-antwerp-1/home to my local computer and added a vocabulary which I pushed back to the repository and did a PR
• I tried doing the same with the student bio, awaiting to see if it will push and I can make a PR.

Check-In

I Need Help With:

• If my student-bio push did not go through I need help in figuring out why not
• Will work on setting up a PR in my group repository to add my checklist (might need help with that)

What went well?

-Most things I get stuck with I can find a solution, but it can be very time consuming because everything is so new, it helps to sometimes rewatch some of the tutorials.

What went less well?

• When something is not setup right you can lose hours trying to figure out what is wrong, like when you get an error message in Terminal

Lessons Learned

• Reach out for help

Sunday Prep Work

Get working on my retrospective for this module

• @AlinaTaoRao :
• @sannesofie :
• @tahminarasoli :
• @NajiSarah :

• repo (with a complete README)
  • live demo
  • /planning
  • communication plan
  • constraints
  • backlog
  • wireframe
  • development strategy
  • retrospective
• project board

thursday check-in

Learning Objectives

• 🥚 Git Remote/Local Connection: You can:
• create a local git repository
• commit changes
• connect a remote repository
• 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
• use npm scripts (dev, lint and format)
• 🥚 Browser + DevTools: You can:
• open a local HTML/CSS project in your browser
• inspect the elements
• emulate different devices
• 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
• 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
• pass Continuous Integration checks for code linting and validation.
• 🐥 GitHub Collaboration: You can:
• collaborate in a single repository and contribute a markdown file.
• create a new branch
• create and edit a file on that branch
• send a pull request
• address any requested changes
• review +merge 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.

1. Create this issue
2. Install softwares
3. Install VSCode extensions
4. Organize your computer
5. GitHub setup
6. Submit student bio PR
7. Fork and Clone the flashcards repository
8. Prep work for Workflows Chapter 1

• repo (with a complete README)
• live demo
• /planning
  • communication plan
  • constraints
  • user personas (you need to write this!)
  • backlog
  • design
  • development strategy
  • retrospective
• project board

Learning Objectives

• Collaborating: You can effectively work in a group:
• 🥚 You can work with your group mates to agree on a communication plan.
• 🥚 As a group you can define project constraints by discussing your strength's, weaknesses and context.
• 🥚 During development you can ask your group for help when you need it using the agreed channels of communication.-
• 🥚 During development you communicate any changes in your personal situation that will impact the group.
• 🥚 When the project is finished your group can write a retrospective including concrete steps to make sure the next project goes smoother.Planning:
• You can work in a group to plan a multi-page website written with HTML & CSS:
• 🥚 You can understand a web page's users by creating user personas.
• 🥚 You can work together to write a backlog of user stories for your personas, organized by priority (must, should, could)
• 🥚 You can work together to create a simple wireframe with pencil+paper and a basic drawing app like Excalidraw
• 🐣 You can work together to write a development strategy for must-have user stories.
• 🐣 You can work together to convert a development strategy into issues on a project board organized with labels and milestones.Developing:
• Once the project board is set up you can work with your group to develop the website:
• 🥚 You can claim a task and manage your progress using the project board columns.
• 🥚 Your group can use issues to discuss and agree on project changes once development has begun.
• 🥚 You can use the help-wanted label to ask for help, and to find issues that need your help.
• 🥚 You can manage a separate branch with your work for each issue task.
• 🥚 You can create a PR that passes CI checks when your task is finished, then assign someone to review it.
• 🐣 You can review a group member's PR and conduct a code review using the project's checklist.

• name: Khaled
• name: Maurice
• name: Mohammed
• name: Ashenafi
• name: Daniel

A nice repository to introduce the members of the group to each other.

• repo
• many small, well-named commits
• a nice README
• one well-named file per person
• one pull requests for each group member
  • linting checks pass
  • code review checklist is complete
  • the reviewer merged the code

Group 1 - Agile Week 1

Mohammed
Daniel
Darin
Maurice
Aviv

Our Goal:

plan and create a working website in a group, following an agile development Strategy.

• repo
• live demo
• /planning
  • communication plan
  • constraints
  • backlog
  • design
  • development strategy
  • retrospective
• project board

Learning Objectives

• Collaborating: You can effectively work in a group:
• 🥚 You can work with your group mates to agree on a communication plan.
• 🥚 As a group you can define project constraints by discussing your strength's, weaknesses and context.
• 🥚 During development you can ask your group for help when you need it using the agreed channels of communication.-
• 🥚 During development you communicate any changes in your personal situation that will impact the group.
• 🥚 When the project is finished your group can write a retrospective including concrete steps to make sure the next project goes smoother.Planning:
• You can work in a group to plan a multi-page website written with HTML & CSS:
• 🥚 You can understand a web page's users by creating user personas.
• 🥚 You can work together to write a backlog of user stories for your personas, organized by priority (must, should, could)
• 🥚 You can work together to create a simple wireframe with pencil+paper and a basic drawing app like Excalidraw
• 🐣 You can work together to write a development strategy for must-have user stories.
• 🐣 You can work together to convert a development strategy into issues on a project board organized with labels and milestones.Developing:
• Once the project board is set up you can work with your group to develop the website:
• 🥚 You can claim a task and manage your progress using the project board columns.
• 🥚 Your group can use issues to discuss and agree on project changes once development has begun.
• 🥚 You can use the help-wanted label to ask for help, and to find issues that need your help.
• 🥚 You can manage a separate branch with your work for each issue task.
• 🥚 You can create a PR that passes CI checks when your task is finished, then assign someone to review it.
• 🐣 You can review a group member's PR and conduct a code review using the project's checklist.

my fork of the exercises repo

Study Plan

Week 4

• I have pushed my progress to my fork of exercises repo

Check-In

I Need Help With:

• It's not about needing help with something in particular, it's more about moving forward and fully understanding how everything is organized, resources, examples ... it's getting better, but it is true that at first I was quite lost

What went well?

• Better understanding how everything is organized
• Feeling more secure and confident in all the actions that I am taking
• Everything starts working for me, and it's a pretty big factor, linux, npm, verification, lint, git

What went less well?

• Take a few days off for stomach pain, and maybe I'm behind with the group
• Communication in general with the group is not entirely good
• Better organization and time management

Lessons Learned

• I need to push myself with CSS, the video tutorial "Build a Responsive Website | HTML, CSS Grid, Flexbox & More" blew me away, and I realized everything I have to learn

Sunday Prep Work

1. Create this issue
2. Install softwares
3. Install VSCode extensions
4. Organize your computer
5. GitHub setup
6. Submit student bio PR
7. Fork and Clone the flashcards repository
8. Prep work for Workflows Chapter 1

Group 2 - Agile development Week 1

Group members

• Nefn-Lakhouj
• Alfaro B. Eduardo
• Khaled
• mniyomuk

• repo
• planning
• communication plan
• constraints
• backlog
• design
• development strategy
• retrospective
• project board

Study Plan

• Agile Development
• Sprint Planning
• User Stories
• Website Planning
• Working Together
• Code Review
• HTML & CSS
• Agile is not Perfect
• Class Recordings

Collaborating in a group

• You can work with your group mates to agree on a communication plan.
• As a group you can define project constraints by discussing your strength's, weaknesses and context.
• During development you can ask your group for help when you need it using the agreed channels of communication.
• During development you communicate any changes in your personal situation that will impact the group.
• When the project is finished your group can write a retrospective including concrete steps to make sure the next project goes smoother.

Planning

• You can work in a group to plan a multi-page website written with HTML & CSS:
• You can understand a web page's users by creating user personas.
• You can work together to write a backlog of user stories for your personas, organized by priority (must, should, could)
• You can work together to create a simple wireframe with pencil+paper and a basic drawing app like Excalidraw
• You can work together to write a development strategy for must-have user stories.
• You can work together to convert a development strategy into issues on a project board organized with labels and milestones.

Developing

• You can claim a task and manage your progress using the project board columns.
• Your group can use issues to discuss and agree on project changes once development has begun.
• You can use the help-wanted label to ask for help and to find issues that need your help.
• You can manage a separate branch with your work for each issue task.
• You can create a PR that passes CI checks when your task is finished, then assign someone to review it.
• You can review a group member's PR and conduct a code review using the project's checklist

my fork of the exercises repo

Study Plan

• Module01:Precourse-Suggested Study
  • Being a Developer
  • What is the Internet?
  • Git and GitHub
  • Slack
  • Class Recordings

HYF Study Book

• Learning

  • Learning From Code
  • How to Ask Questions
  • Study Strategies
  • Self Assessment

• Git & GitHub

  • Git
  • GitHub
  • Graphical User Interface Clients
  • GitKraken
  • Because Windows
  • workflows

• Command Line Interface

  • Command Line Interface

• Programming

  • What is programming?
  • Reading Source Code
  • Problem Solving

Learning Objectives

• 🥚 GitHub Issues: You can create a new issue in a GitHub repository using an issue template. They can correctly use labels, milestones, and assignment to make their issue findable.
• 🥚 File System Management: You can create and organize a new folder in their personal computer for the materials they will study at HYF.
• 🥚 Project Boards: You can use issues on a GitHub project board to track their projects (class repo) and self-study (project board on personal account).
• 🐣 Visual Studio Code: You can install and manage extensions, open a folder, create new files/folders inside of the folder ... basic usage.
• 🐣 GitHub Pull Requests: You can fork a repository and send a Pull Request using a template.

Week 1

• I have pushed my progress to my fork of exercises repo

Check-In

I Need Help With:

What went well?

What went less well?

Lessons Learned

Sunday Prep Work

• name: @sannesofie
• name: @Rphoof
• name: @MJGoharriz
• name: @edualfaro

We just create a fantastic group from ther scratch

• repo
• many small, well-named commits
• a nice README
• one well-named file per person
• one pull requests for each group member
  • linting checks pass
  • code review checklist is complete
  • the reviewer merged the code

Study Plan

• Agile Development
• Sprint Planning
• User Stories
• Website Planning
• Working Together
• Code Review
• HTML & CSS
• Agile is not Perfect
• Class Recordings

Collaborating in a group

• You can work with your group mates to agree on a communication plan.
• As a group you can define project constraints by discussing your strength's, weaknesses and context.
• During development you can ask your group for help when you need it using the agreed channels of communication.
• During development you communicate any changes in your personal situation that will impact the group.
• When the project is finished your group can write a retrospective including concrete steps to make sure the next project goes smoother.

Planning

• You can work in a group to plan a multi-page website written with HTML & CSS:
• You can understand a web page's users by creating user personas.
• You can work together to write a backlog of user stories for your personas, organized by priority (must, should, could)
• You can work together to create a simple wireframe with pencil+paper and a basic drawing app like Excalidraw
• You can work together to write a development strategy for must-have user stories.
• You can work together to convert a development strategy into issues on a project board organized with labels and milestones.

Developing

• You can claim a task and manage your progress using the project board columns.
• Your group can use issues to discuss and agree on project changes once development has begun.
• You can use the help-wanted label to ask for help and to find issues that need your help.
• You can manage a separate branch with your work for each issue task.
• You can create a PR that passes CI checks when your task is finished, then assign someone to review it.
• You can review a group member's PR and conduct a code review using the project's checklist

you will create ONE check-in issue per module

Suggested Study:

Command Line Interface (CLI)

• relative vs. absolute paths
• The Coding Train
• Jesse Showalter
• CLI games:
  • bashcrawl - clone & play
  • Terminus - online
  • iTerm - online
• A huge cheat sheet

Visual Studio Code (VSCode):

• academind VSC tutorial
• shortcuts cheatsheet
• The Coding Train
  VSC Intro from VSC
• tutorial step-through
• get started
• Tips for HTML/CSS/JS
  Are you using Windows?
• Windows Subsystem for Linux
• WSL with VSCode
• nvm command not found

Code Quality

• formatting (all file types with prettier)
• linting
  • CSS
  • markdown
• validating HTML
• spelling checks (will do once by automation, then by hand. automated spell checks are a little annoying)

READMEs

• makeareadme.com
• bulldogjob
• meakaakka
• awesome-README-templates

Git and GitHub

Git and GitHub for Poets
Learn to visualize what happens inside of Git with:
learngitbranching + a Video Guide
ohmygit - a git game
HYF/study
lab.github.com/githubtraining
first day on github
first week on github
prepare to use github
Getting Started with GitHub
Creating a GitHub Repository
Creating a local repo and push
and much more at hackyourfuture.github.io/study
lab.github.com:
First Day on GitHub
First Week on GitHub
The Net Ninja
git-it
Understand how to use Atomic Commits

Collaborating on GitHub

Adding collaborators to a repository
about code reviews
requesting a code review
Git Workflow for 2
Pull Requests
Git & GitHub for Poets
The Net Ninja: 11
linking PRs to Issues: reference 1, reference 2
closing Issues using keywords

GitHub Actions

For now you can think of Continuous Integration is a fancy way to say "automatically check your code before you merge". Your project repositories will all have CI scripts to help maintain a quality and consistent code base.
hint: remember to enable GitHub Actions in your repository!

DevTools and the DOM

How to inspect an element
inspecting-the-dom
Modify the DOM. (does the source change?)

Class Recordings

HYF modules are often updated, recordings from past classes may not match this gitbook
When sending a PR's with recording links please ...
Indicate which class you were teaching
Which week it was (if the module is more than 1 week)
a helpful title or description
How to inspect an element
inspecting-the-dom
Modify the DOM. (does the source change?)

members:

Zakaria
Mervat
Ahmed
Hans
Aviv

• repo
• many small, well-named commits
• a nice README
• one well-named file per person
• one pull requests for each group member
  • linting checks pass
  • code review checklist is complete
  • the reviewer merged the code