4. Section Ghost

For Kemi #7

• Clone this repo or pull it if you already cloned it
• Create the ghost branch git branch ghost
• Switch to that branch git checkout ghost
• Move your issue in the column in progress (in the Project board)
• Create the section ghost in index.html file
• Create the CSS relative to the ghost section in style.css
• Always add and commit your changes in your local repository
• Push to your branch on Github,
  the first time git push --set-upstream origin ghost
  or git push origin ghost (if the branch is already present in GitHub)
• Move your issue in the column to review
• Create a PR
• The PR is reviewed
• The branch is merged into master branch
• The PR is closed
• Move your issue in the done column

3. Section Monster

For Divya #5

• Clone this repo or pull it if you already cloned it
• Create the monster branch git branch monster
• Switch to that branch git checkout monster
• Move your issue in the column in progress (in the Project board)
• Create the section monster in index.html file
• Create the CSS relative to the monster section in style.css
• Always add and commit your changes in your local repository
• Push to your branch on Github,
  the first time git push --set-upstream origin monster
  or git push origin monster (if the branch is already present in GitHub)
• Push to your branch on GitHub
• Move your issue in the column to review
• Create a PR
• The PR is reviewed
• The branch is merged into master branch
• The PR is closed
• Move your issue in the done column

4. Section Alpinist

For Bermarte #8

• Clone this repo or pull it if you already cloned it
• Create the alpinist branch git branch alpinist
• Switch to that branch git checkout alpinist
• Move your issue in the column in progress (in the Project board)
• Create the section alpinist in index.html file
• Create the CSS relative to the alpinist section in style.css
• Always add and commit your changes in your local repository
• Push to your branch on Github,
  the first time git push --set-upstream origin alpinist
  or git push origin alpinist (if the branch is already present in GitHub)
• Move your issue in the column to review
• Create a PR
• The PR is reviewed
• The branch is merged into master branch
• The PR is closed
• Move your issue in the done column

1. Wireframe

Create a wireframe for our README file
For Bermarte #3

• Clone this repo or pull it if you already cloned it
• Create a wireframe branch
• Switch to that branch git checkout wireframe
• Move your issue in the column in progress (in the Project board)
• Create a Wireframe
• Always add and commit your changes in your local repository
• Push to your branch on Github,
  the first time git push --set-upstream origin wireframe
  or git push origin wireframe (if the branch is already present in GitHub)
• Move your issue in the column to review
• Create a PR
• The PR is reviewed
• The branch is merged into master branch
• The PR is closed
• Move your issue in the done column

9. ARIA

For Bermarte

• Search what ARIA is about
• Find some info
• Choose members who will implement this feature
• Validate using https://achecker.ca/checker/index.php
• Convert i to span
• Add label to the text input (like coach Tiago said)

For member X Y

Create the aria branch git branch aria
Switch to that branch git checkout aria
Always add and commit your changes in your local repository
Push to your branch on Github
Move your issue in the column to review
Create a PR
The PR is reviewed
The branch is merged into master branch
The PR is closed
Move your issue in the done column

tutorials, info

https://developers.google.com/web/fundamentals/accessibility/semantics-aria/

2. Section Home

For Burak #4

• Clone this repo or pull it if you already cloned it
• Create the home branch git branch home
• Switch to that branch git checkout home
• Move your issue in the column in progress (in the Project board)
• Create the section home in index.html file
• Create the CSS relative to the home section in style.css
• Always add and commit your changes in your local repository
• Push to your branch on Github,
  the first time git push --set-upstream origin home
  or git push origin home (if the branch is already present in GitHub)
• Move your issue in the column to review
• Create a PR
• The PR is reviewed
• The branch is merged into master branch
• The PR is closed
• Move your issue in the done column

7. Modding, Fixes

created by Bermarte and Burak

• Create a branch fix
• Validate
• Fix HTML
• Fix CSS
• Write Javascript
• Fix sections
• PR
• merge
• Create a branch homeSecond
• Fix HTML
• Fix CSS
• Write Javascript
• PR
• merge
• Create a branch thirdHome
• Fix HTML
• Fix CSS
• Write Javascript
• PR
• merge

4. Section Bathtub

For Patrick #6

• Clone this repo or pull it if you already cloned it
• Create the bathtub branch git branch bathtub
• Switch to that branch git checkout bathtub
• Move your issue in the column in progress (in the Project board)
• Create the section bathtub in index.html file
• Create the CSS relative to the bathtub section in style.css
• Always add and commit your changes in your local repository
• Push to your branch on Github,
  the first time git push --set-upstream origin bathtub
  or git push origin bathtub (if the branch is already present in GitHub)
• Move your issue in the column to review
• Create a PR
• The PR is reviewed
• The branch is merged into master branch
• The PR is closed
• Move your issue in the done column

0. Repo

For Bermarte
As a site visitor, I want to know about this repo
We start our repository on GitHub

Repo

• developed on the master branch
• Fork the HYF template to add the validator
• Invite members
• Give your project a name
• Create README.md file
• Create development-strategy file
• Create this Project Board
• Create imgs directory
• Copy the images from Duck Duck Go website
• Add a screenshot to README.md
• Write the user stories in the development strategy
• Write the issues and assign a member for each
• Add a screenshot to README.md