Frontend Workshop from HTML/CSS/JS to TypeScript/React/Redux
Перейти к файлу
Inna Nikolenko 09e2f5cca1 updated readme for step 01-05 (#111) 2019-03-11 09:11:48 -07:00
.vscode adding a recommended extension of prettier 2019-02-28 09:56:04 -08:00
assets fixing up step 2.7 demo 2019-03-03 20:14:51 -08:00
bonus-jest Jest step updates 2019-03-05 03:30:40 -08:00
bonus-servicecalls/demo fixing relative links 2019-03-04 19:01:59 -08:00
markdownReadme/src fixing relative links 2019-03-04 19:01:59 -08:00
playground playground using codesandbox 2019-03-03 20:30:36 -08:00
server [Server] Send HTTP response after processing request. 2019-02-25 12:12:11 -08:00
step1-01 Fix initialization of day 1/step 1 exercise. (#108) 2019-03-11 09:10:29 -07:00
step1-02 Day 1: title formatting coherence, other edits 2019-03-05 02:20:22 -08:00
step1-03 Associate label with input. Include name in input. (#92) 2019-03-11 08:54:20 -07:00
step1-04 Update README.md (#86) 2019-03-05 12:38:55 -08:00
step1-05 Folders hierarchy fix (#109) 2019-03-09 18:06:23 -08:00
step1-06 Step numbers in todo app headers 2019-03-05 02:58:04 -08:00
step1-07 Step numbers in todo app headers 2019-03-05 02:58:04 -08:00
step2-01 Add step2-01 final folder with solutions 2019-03-05 14:17:56 -08:00
step2-02 Step numbers in todo app headers 2019-03-05 02:58:04 -08:00
step2-03 Vertically center elements in TodoFooters 2019-03-05 13:36:07 -08:00
step2-04 Vertically center elements in TodoFooters 2019-03-05 13:36:07 -08:00
step2-05 Mostly day 2 step 6 updates (#85) 2019-03-07 15:45:36 -08:00
step2-06 Mostly day 2 step 6 updates (#85) 2019-03-07 15:45:36 -08:00
.gitignore checking in docs for github.io page 2019-02-19 23:41:11 -08:00
LICENSE Fixing license 2019-02-27 08:40:29 -08:00
LICENSE-CODE Fixing license 2019-02-27 08:40:29 -08:00
README.md Add guidelines fixes #97 (#99) 2019-03-11 09:05:17 -07:00
azure-pipelines.pr.yml getting rid of some typo 2019-02-25 21:54:48 -08:00
azure-pipelines.yml revert 2019-02-25 21:51:33 -08:00
index.html Add step2-01 final folder with solutions 2019-03-05 14:17:56 -08:00
jest.config.js adding enzyme test 2019-02-24 14:02:44 -08:00
jest.setup.js adding enzyme test 2019-02-24 14:02:44 -08:00
package-lock.json get rid of audit warnings 2019-03-04 09:41:52 -08:00
package.json Update package.json (#89) 2019-03-05 11:22:18 -08:00
prettier.config.js adding some redux steps 2019-02-16 17:00:47 -08:00
tsconfig.json fixing the tsconfig to exclude docs/ dir 2019-02-20 11:13:16 -08:00
webpack.config.js Add special case to webpack config for step1-04 docs 2019-03-05 04:01:22 -08:00

README.md

Frontend Bootcamp / Days in the Web

🚨🚨 This project is a work in progress! Issues and pull requests are encouraged. 🚨🚨

Welcome

In this two-day workshop you'll learn the basics of frontend development while building a working web app.

The first day provides an introduction to the fundamentals of the web: HTML, CSS and JavaScript. This is targeted at new and experienced developers alike. On the second day we'll dive into more advanced topics like TypeScript, state management, and testing. While the examples should be accessible to anyone, you'll get the most out of it if you have some prior experience with programming and web technologies.

Getting set up

1. Required software

Before starting, make sure your computer has up-to-date versions of the following installed:

2. Installing and opening the project

  • Open VS Code and then press ctrl + ` (backtick, in top left corner of keyboard) to open the built-in terminal
  • Use the cd (change directory) command to find an appropriate place for your code
  • Type git clone https://github.com/Microsoft/frontend-bootcamp.git into the terminal to pull down a copy of the workshop code
  • Type cd frontend-bootcamp to change your current directory to the bootcamp folder
  • Type npm install to install all of the project dependencies
  • Type code -r . to open the bootcamp code in VS Code

If on a Mac, be sure you've followed these steps first to make the code command available.

3. Run the "inner loop" build

At this point, your VS Code window should look something like this:

To start the dev "inner loop," run:

npm start

This will load the site shown below.

4. Lesson Structure

  1. Demos will either be via CodePen (Steps 1,2 and 3) or done in the step folder. Follow the step README to walkthrough the demo.

  2. Much like demos, exercises are done via CodePen or in the project step folders. These exercises will give you an opportunity to try what was demonstracted in the first step.

What to expect

For each lesson, the presenter will walk through some demo code to teach core concepts about the topic. Don't worry about writing code at this point. Just follow along via the readmes linked below.

Most lessons also have an exercise portion. Exercise instructions are usually found in the readme for each step's "exercise" folder.

Day one

Day one covers the basics of HTML, CSS and JavaScript, as well as an introduction to React and Typescript.

  1. Introduction to HTML
  2. Introduction to CSS
  3. Introduction JavaScript
  4. Introduction to React
  5. Building a static page
  6. State-driven UI
  7. Types and UI-driven state

Day two

  1. TypeScript basics
  2. UI Fabric component library
  3. Theming and styling
  4. React Context
  5. Redux: Store
  6. Redux: React binding

Bonus content

Additional resources

Follow the authors!

If you are interested in JavaScript, TypeScript, React, Redux, or Design Systems, follow us on Twitter:

Other projects from the UI Fabric team at Microsoft

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License, see the LICENSE file, and grant you a license to any code in the repository under the MIT License, see the LICENSE-CODE file.

Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.

Privacy information can be found at https://privacy.microsoft.com/en-us/

Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.