Front-end

Micro-frontend architectures decompose a front-end app into individual, semi-independent "microapps" working loosely together. This can help make large projects more manageable, e.g. when transitioning from legacy codebases.

Are Vue.js, React, and Angular actually delivering a good developer and user experience, or are they used simply because they're the current de facto standard? Discover some exciting approaches to web development.

It's no secret that the WordPress codebase is a mess. Many developers use its legacy code as an excuse for writing sloppy code themselves, even if its newer additions follow best practices. If this is you, it's time to level up your skills!

Types and testable code are two of the most effective ways of avoiding bugs. In this tutorial, discover TypeScript best practices while you create a Discord bot from scratch.

With a static site generator back end in place from Part 1, now it's time to implement a Gatsby.js-based front end, host it on Netlify, and get AWS to activate the whole pipeline.

While components have been available in Angular since the beginning, they’re still easy to mess up with common mistakes like people not using them at all, creating components instead of attribute directives, and more. In this article, Toptal Freelance JavaScript Developer Valters Valdersteins differentiates the correct and incorrect ways to use Angular components and illustrates them with examples.

Eliminate complex code configurations using a monorepo structure. This guide will help you get started.

Without proper state management, your Angular app will become a UX nightmare. But even with that solved, persisting state across sessions and devices can be tricky. This tutorial shows how to leapfrog that challenge using Firebase.

As simple as your RESTful API may be, even internal users will want a JavaScript package that will do all the heavy lifting for them. Why build each CRUD request by hand, or worse, deal with related resources using custom code for every scenario? With ActiveResource.js, you don't have to.