Angular version 4.0.0 - invisible-makeover - is now available. This is a major release following the announced adoption of Semantic Versioning, and is backwards compatible with 2.x.x for most applications.
Next.js is a very slim yet powerful framework. Place React components in a pages directory and running next, and you'll get automatic code splitting, routing, hot code reloading and universal (server-side and client-side) rendering.
Since our industry is awesome, we don’t only have one recommended solution. Experts have jumped in and provided us with suggestions like BEM, OOCSS, SMACSS, Atomic Design and many others. Now, instead of suffering from “I don’t know what to do”, the question becomes: “there’s so many ways. Which should I try?” Should I use everything, only one approach or create a custom architecture from the possible picks out there?.
Mandy Michael has been creating some incredible text effects with just the power of CSS. She uses every trick in the book: gradients, transforms, pseudo elements, shadows, and clipping paths to name a few. They are all real web text too. Custom fonts typically, but no images, canvas, or SVG or anything like that.
It all started last week. 3 different React learners encountered 3 different obstacles trying to use setState() in their projects. Eric mentors new React users a lot, and consults with teams making transitions from other architectures to React.
Too often, we’ve seen others neglect accessibility because of some common misconceptions that make things difficult. In this post, we’ll debunk these myths, so you can easily create universally accessible content.