A lot of people are getting excited about CSS Grid, and want to learn it. A lot of people are also super busy. So let me teach you some very basic things about Grid, and get you started with a 5-minute taste.

Unlike Bootstrap or any of the other layout frameworks we’ve been using for the last decade, CSS Grid does not get applied to the entire page with everything on it.

You define a grid on a specific element. All of the direct children of that element will be placed on that Grid. Nothing else on the page gets involved.

Start by thinking about what to make a Grid container, and how to structure your markup so you have the Grid items that you want.

The landscape for learning d3 is rich, vast and sometimes perilous. You may be intimidated by the long list of functions in d3’s API documentation or paralyzed by choice reviewing the dozens of tutorials on the home page. There are over 20,000+ d3 examples you could learn from, but you never know how approachable any given one will be.

This guide is meant to prepare you mentally as well as give you some fruitful directions to pursue. There is a lot to learn besides the d3.js API, both technical knowledge around web standards like HTML, SVG, CSS and JavaScript as well as communication concepts and data visualization principles. Chances are you know something about some of those things, so this guide will attempt to give you good starting points for the things you want to learn more about.

This repository is an educational resource for Angular v1 experts that are looking to learn React/Redux. A contrived sample application for managing basic patient information is provided using both technologies' best practices (look under samples/ to see both versions). This application (demonstrated below) will be referred to below as we explore the key philosophical differences between Angular v1 and React/Redux so that you can get coding!

Once the technologies for a project are chosen, the next step is to figure out how to scaffold and build the application using production-ready practices. Angular v1 applications are typically wired together using a mixture of

This part is very important, it’s your last protection before the data are sent to your server so be careful here.
Two ways to do the work:

Let’s modify a bit the template from the previous post:

We only add a field that will be displayed if we have an error in our userForm.

Back to our Component’s code.
Angular 2 is Observable-Friendly, we can subscribe and listen to many changes now!

To keep it simple, we are only going to use the input name.
We stock the name Controls into a new const named nameControl.
Then we subscribe to the value changes.
Every time the input changes, we make a very basic check, if the input is empty we set a new error that will be named