As Angular is maturing, it gets harder and harder for newcomers to make sense of the abundance of materials you find online. The vast majority of Angular 1.x tutorials use outdated Angular practices–things that modern Angular 1.x projects should not be using.
It's often useful to include compiled front-end code in npm modules (eg: CSS transpiled from SCSS). However, it's suboptimal to commit compiled code to your repository because you end up with bloated diffs in your commit history and a higher chance of merge conflicts. You'll also end up with a much larger overall filesize for your repo, which will slow down pushes and pulls.
Rather than waiting until the whole team is stressed out and slammed with deadlines, you can proactively establish conventions and make sure the team is on the same page.
The main idea behind the flex layout is to give the container the ability to alter its items' width/height (and order) to best fill the available space (mostly to accommodate to all kind of display devices and screen sizes). A flex container expands items to fill available free space, or shrinks them to prevent overflow.
Heydon Pickering explains how to write less code by using CSS Inheritance. If you take a closer look, It’s remarkably good at letting you do a lot with a little.
JavaScript or frameworks built with it are not our enemy. They are neither the enemy of accessibility, nor of web standards in general. And neither are the ones who thought up those frameworks to make other developers’ lives easier. They want to do good things for the web just like accessibility advocates do, they just need to work together more.
We hope you enjoyed reading this week's issue of #FrontendCookies. If you like our newsletter, refer it to a friend or colleague.