Bootcamp

Scope

This bootcamp is dedicated to junior frontend developers, so they can learn the basics of the core technologies of this domain:

1. HTML
2. CSS
3. JavaScript
4. React
5. Git
6. Typescript

Guidelines

Directories

Every participant of the bootcamp should create their own directory inside /src. Like this, all the exercises of each participants are stored in a particular directory and ensure that there are no git conflicts due to other participants.

Issues

• You can check the issues tab in GitHub to see all the issues of the project. You can then filter out the issues per participant to see what is pending.
• You can and also must check the Projects tab in GitHub, there is the board where you can keep track of all the issues and their corresponding state, including the due date of the issues in process. Keep those dates in mind so you are always up to date.

Labels

Each issue has a label that indicates the type of issue it is. This information lets you to know what is expected from you:

1. Assignment: tasks with this label expects that you commit your solution and create a Pull Request. Assign your mentor as a reviewer so he/she can check it and provide feedback or approve it.
2. Exercise: these tasks are for you to practice and improve your skills. These don't demand that you code the solution in this project or create a PR.
3. Lecture: these tasks are lectures where you will learn new concepts. Each lecture has a quiz assigned, so you must complete it to evaluate that you have understood the concepts related.
4. Project: these are special tasks that will test your knowledge in a big domain. It requires that you commit your code and create a PR. More details will be given to you when this type of task is assigned.

Commits

In this project all commits are evaluated before they are created. The commit messages should be aligned with the Conventional Commit specification.

Code format

The code is formatted automatically during the commit process using Prettier. It is recommended that you have the VS Code extension of this formatter and that you allow it to auto format the code every time you save so you can see how the code is progressing.

Branches

Follow this structure when creating new branches in the project.

1. Start the branch name with the initial characters of your firstname and lastname. For example, 'John Doe' would use 'jd'.
2. Continue the branch name with the number of the issue you're working on. For example, '27'.
3. Complete the name with a brief title of the issue.

A complete example would look like this: 'jd/27/markup-a-readme'.

Pull Request

The main branch is protected, so the only way to have your code in there is through a Pull Request. When you complete the issue, create a Pull Request and assign your mentor as the reviewer. Also move the card in the board to the 'Review' state so your mentor can easily track that it is time to review your code.

Contributions

This project is an ongoing effort to train the new developers that join our company. If you find any problem, you have two options:

1. If you don't know how to solve it: create an issue, describe the problem and label it as a 'bug'.
2. If you can solve it: create a PR, describe the problem you're solving, label the PR as a bug and assign your mentor as reviewer.