Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 7ef69b0

Browse files
authored
Merge pull request HackYourFuture#391 from kelleyvanevert/style-guide
Fixing style guide intro text
2 parents 6d0c6f1 + e8418f8 commit 7ef69b0

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

README.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,11 @@ On top of that you'll also learn how to think differently about _how_ you write
1313

1414
## Before you start
1515

16+
In the following weeks we will be using a "style guide" to help you write _"clean code"_. Because code is not only meant to be run by computers, but also to be read by humans (your colleagues, and the future version of you), it's best to make your code good. If your code is readable and nicely formatted, you're doing your colleages (and future you) a great service. The idea of a "style guide" comes from visual design, where companies often have a "visual style". For example, watch the following video to get an idea of this:
17+
1618
### Setup Style Guide
1719

18-
In the following weeks we will be using a front-end `style guide` to help you write _"clean code"_. What is a style guide? Simply put, it's a set of coding standards put into one collection.
20+
Similar to how designers have style guides for their design work, programmers often have "programming style guides". This is set of rules to follow when writing/formatting your code. The styleguide we'll be using is the one from Airbnb:
1921

2022
- [Front-end Style Guides](https://fronteers.nl/congres/2015/sessions/front-end-style-guides-anna-debenham)
2123

@@ -25,6 +27,8 @@ The style guide we'll be using is the one from Airbnb:
2527

2628
While you do not need to read this guide in detail, it is recommended that you look at sections 1-8, 12-13, 15-21 and 23.
2729

30+
We also have tools that can automatically check whether your code is correctly formatted according to a style guide. These tools are called "linters". We will be using the JavaScript linter called "ESLint". The following packages are already added to this repository's `package.json`:
31+
2832
The required packages you need to install before you write code according to the style guide are the following:
2933

3034
```json

0 commit comments

Comments
 (0)